Advanced Gtk+ Sequencer - News

Group

Main
- Main
- View members
- Search
Homepage
Download
Docs
Support
- ~~Submit new~~
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Mailing lists
Source code
Bugs
- Submit new
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Tasks
- ~~Submit new~~
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
News
- Browse
- Atom feed
- ~~Submit~~
- ~~Manage~~

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