Re: [LAD] how to store deferred events in a real time audio app?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Paul Davis <paul@...>
Cc: <linux-audio-dev@...>
Date: Wednesday, December 21, 2011 - 11:17 am

[Paul Davis]

>On Tue, Dec 20, 2011 at 8:24 AM, Tim Goetze wrote:

Yes, and fortunately commonly occurring events from MIDI-sourced=20
tracks are relatively sparse. If these events are only enqueued in=20
bursts a handful of times per second the sorting overhead is quite=20
small, and reduced further if sorting only occurs when the consuming=20
thread detects write pointer movement on the FIFO. (Since there's a=20
certain contention for the track lock between recording, playback and=20
editing, hard realtime access to the track contents seems all but out=20
of the question anyway.)

>> =A0Multiple

There'll be at least the realtime MIDI input thread, and then there=20
are events generated from audio streams that have to be dispatched in=20
a lockfree code path. (Of course, none of this is much of a concern=20
if you do all your realtime work in a jack audio processing callback.)


Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] how to store deferred events in a real time audio ..., Tim Goetze, (Wed Dec 21, 11:17 am)