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

 
 
Latest News
GSequencer v2.1.53 for debian buster posted by jkraehemann, Fri 08 Mar 2019 11:01:12 PM UTC - 0 replies
Get emotional as debian buster is going to be released posted by jkraehemann, Thu 07 Mar 2019 12:46:59 AM UTC - 0 replies
State of GSequencer in debian buster posted by jkraehemann, Sun 03 Mar 2019 07:08:32 PM UTC - 0 replies
handling LV2 iriref posted by jkraehemann, Wed 13 Feb 2019 10:20:49 AM UTC - 0 replies
fixed ref-count posted by jkraehemann, Sat 09 Feb 2019 02:46:41 PM UTC - 0 replies
[Submit News]
[79 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.


Cheers,
Joël

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

 

Back to the top


Powered by Savane 3.4