newsAdvanced Gtk+ Sequencer - News: Implementing ags-play-pattern recall and ags_input_next_active()

 
 
Latest News
GSequencer 1.2.x goals posted by jkraehemann, Wed 18 Oct 2017 08:27:54 PM UTC - 0 replies
GSequencer gets triple-sync and additional dialogs posted by jkraehemann, Fri 13 Oct 2017 04:28:05 PM UTC - 0 replies
GSequencer first major release 1.0.0 posted by jkraehemann, Sun 01 Oct 2017 05:41:43 AM UTC - 0 replies
Reduced latency of JACK posted by jkraehemann, Fri 22 Sep 2017 12:37:27 PM UTC - 0 replies
Advanced Gtk+ Sequencer v1.0.0-beta posted by jkraehemann, Thu 31 Aug 2017 06:14:22 PM UTC - 0 replies
[Submit News]
[41 news in archive]

Implementing ags-play-pattern recall and ags_input_next_active()

Item posted by Joël Krähemann <jkraehemann> on Fri 24 Mar 2017 08:30:02 PM UTC.

I think there can be much overhead reduced by replacing ags-copy-pattern recall with ags-play-pattern recall. In view of ags-copy-pattern what does decided to play a channel within ags_channel_play(). It comes with a heavy payload. It would make no sense to have ags_input_next_active().

Contrary ags-play-pattern does decide to play a channel within ags_audio_play(). This gives the advantage of being able to use ags_input_next_active() in ags_channel_recursive_play().

Like that entire parts of your audio processing tree can skip very early. Reducing much overhead doing actually nothing.

This is the prototype to skip not active channels:

And shall be used by the recursive iteration function:

cheers,
Joël

Comments:

No messages in Implementing ags-play-pattern recall and ags_input_next_active()

 

Back to the top


Powered by Savane 3.1-cleanup1