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

 
 
Latest News
It was never so easy ... posted by jkraehemann, Wed 16 May 2018 09:57:42 PM UTC - 0 replies
AgsSoundContainer and AgsSoundResource interfaces posted by jkraehemann, Mon 07 May 2018 03:48:09 PM UTC - 0 replies
Refactored key c source files posted by jkraehemann, Thu 19 Apr 2018 06:49:50 PM UTC - 0 replies
Extended semantics and some removals posted by jkraehemann, Sun 08 Apr 2018 05:10:13 PM UTC - 0 replies

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

No messages in Better performance needs bigger ring-buffer

 

Back to the top


Powered by Savane 3.3