newsAdvanced Gtk+ Sequencer - News: The enormous payload of async UI

 
 
Latest News
Refactored key c source files posted by jkraehemann, Thu 19 Apr 2018 06:49:50 PM UTC - 0 replies
Extended semantics and some removals posted by jkraehemann, Sun 08 Apr 2018 05:10:13 PM UTC - 0 replies
The new dispatcher: ags_channel_recursive_run_stage() posted by jkraehemann, Sun 18 Mar 2018 05:37:45 PM UTC - 0 replies
GSequencer development insights posted by jkraehemann, Sun 04 Mar 2018 02:15:03 PM UTC - 0 replies
GSequencer v2.0.0 - forecast posted by jkraehemann, Tue 06 Feb 2018 03:04:57 PM UTC - 0 replies
[Submit News]
[57 news in archive]

The enormous payload of async UI

Item posted by Joël Krähemann <jkraehemann> on Sun 17 Dec 2017 09:57:51 PM UTC.

Last week I just spent with adding mutices to functions that were never intended to run in parallel. They require to run asynchronous exclusively. E.g. ags_channel_set_link() is such a function. You can't run it at arbitrary time it requires the audio engine not running any AgsRecall implementations. Due to the nested and shared AgsRecycling tree, providing reusable AgsAudioSignal, which would break any concurrent logic.

The nested tree link functions

The payload of the nested tree in code to be written is just enormous. Now it has been 3 days since I started to make some functions related to link AgsChannel thread-safe.

The function ags_channel_set_link() has some related functions:

  • ags_channel_set_recycling()
  • ags_channel_recycling_changed()
  • ags_channel_recursive_set_property()
  • ags_channel_recursive_reset_recall_ids()

Whereas the last is related to these functions:

  • ags_channel_recursive_play_init()
  • ags_channel_tillrecycling_cancel()

ags_channel_recursive_reset_recall_ids() is huge it contains 30 nested functions is over 2000 lines long, at the moment. It is responsible to hot link AgsChannel and set up a running engine. But at most, I think it is the very last function that needs to be thread-safe.

It took 2 more days to make all AgsTask::launch() class to be thread-safe.

Objects need to be locked

In libags-audio these 4 objects need to be protected by a mutex. Accessing properties of them required appropriate lock.

  • AgsSoundcard implementations
  • AgsAudio
  • AgsChannel
  • AgsRecycling

Thought there are more objects that require thread-safety, its mutex is given by libags like for these:

  • AgsSoundcardThread
  • AgsAudioLoop
  • AgsAudioThread
  • AgsChannelThread

Joël

No messages in The enormous payload of async UI

 

Back to the top


Powered by Savane 3.1-cleanup1