newsAdvanced Gtk+ Sequencer - News: Potential dead-lock due to libags-audio callbacks to UI

Latest News
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
Conservative multi-threaded setup posted by jkraehemann, Wed 17 Jan 2018 04:22:14 AM UTC - 0 replies
Goals of GSequencer 1.4.x posted by jkraehemann, Fri 05 Jan 2018 01:43:07 AM UTC - 0 replies
[Submit News]
[55 news in archive]

Potential dead-lock due to libags-audio callbacks to UI

Item posted by Joël Krähemann <jkraehemann> on Fri 17 Nov 2017 08:47:59 AM UTC.

A bigger refactoring is foreseen. Since the Advanced Gtk+ Sequencer user interfaces does relay on callbacks of the underlying library libags-audio.

It is believed to be the source of a dead-lock affecting Apple Mac OS X port at least.

After refactoring communication only will be unidirectional.

Some common callbacks need to replaced would be:

  • AgsAudio::set-pads()
  • AgsAudio::set-audio-channels()

And probably others are there. For sure is that callbacks from AgsTask::launch() need to be replaced, too. This might be a difficult problem. Because there is no real monitoring strategy.

1.1.x-mac changed first

Thought the changes are considered to be critical, the changes are going to be developed on the porting branch first. At most it is the only know architecture affected by the issue.

As soon the code is ready and usable it is going to be merged.



No messages in Potential dead-lock due to libags-audio callbacks to UI


Back to the top

Powered by Savane 3.1-cleanup1