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

 
 
Latest News
The enormous payload of async UI posted by jkraehemann, Sun 17 Dec 2017 09:57:51 PM UTC - 0 replies
Message delivery to GUI posted by jkraehemann, Sat 09 Dec 2017 04:31:47 PM UTC - 0 replies
Refactoring the notation editor posted by jkraehemann, Thu 07 Dec 2017 10:29:21 PM UTC - 0 replies
Potential dead-lock due to libags-audio callbacks to UI posted by jkraehemann, Fri 17 Nov 2017 08:47:59 AM UTC - 0 replies

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