newsAdvanced Gtk+ Sequencer - News: Better performance needs bigger ring-buffer

 
 
Latest News
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
Better support for Apple MacOS X High Sierra posted by jkraehemann, Tue 14 Nov 2017 11:55:02 PM UTC - 0 replies
GSequencer 1.2.x goals posted by jkraehemann, Wed 18 Oct 2017 08:27:54 PM UTC - 0 replies
[Submit News]
[45 news in archive]

Better performance needs bigger ring-buffer

Item posted by Joël Krähemann <jkraehemann> on Wed 04 Jan 2017 03:46:21 PM UTC.

Recent refactoring using intermediate pre and post sync is believed to give better overall performance of the engine. But it had its disadvantage to audio playback being distorted.

Better performance needs bigger ring-buffer because ALSA output is done asynchronous. Further timing is only possible with already happened informations. So its basically just an approximation to stay in real-time.

For now, GSequencer uses a ring-buffer of size of 2. This is going to incremented to 8. The gsequencer release 0.7.123 didn't actually fix the issue introduced in 07.122. Since it wasn't evident what was happening.

However much code was improved so far, especially protecting objects by mutices.

Bests,
Joël

Comments:

No messages in Better performance needs bigger ring-buffer

 

Back to the top


Powered by Savane 3.1-cleanup1