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

 
 
Latest News
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
The 4 paste modes posted by jkraehemann, Wed 03 Jan 2018 12:26:29 AM UTC - 0 replies
Hi all posted by jkraehemann, Sun 31 Dec 2017 05:37:26 PM UTC - 0 replies
[Submit News]
[53 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