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

 
 
Latest News
GSequencer v3.6.x release goals posted by jkraehemann, Fri 31 Jul 2020 10:17:04 AM UTC - 0 replies
GSequencer v3.4.x release goals posted by jkraehemann, Thu 11 Jun 2020 06:58:14 PM UTC - 0 replies
GSequencer v3.3.x replaced all recalls by ags-fx engine posted by jkraehemann, Wed 20 May 2020 07:25:15 AM UTC - 0 replies
Refactor GSequencer's recalls - the ags-fx engine posted by jkraehemann, Sun 03 May 2020 12:08:19 AM UTC - 0 replies
GSequencer v3.3.x release goals posted by jkraehemann, Fri 17 Apr 2020 12:36:11 PM UTC - 0 replies
[Submit News]
[97 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.5