Re: best way to divert callbacks to main thread from audio thread
Re: best way to divert callbacks to main thread from audio thread
- Subject: Re: best way to divert callbacks to main thread from audio thread
- From: Rich E <email@hidden>
- Date: Tue, 04 Oct 2011 06:20:35 +1100
(Oops, for got to hit the 'Reply to all')
Thanks for the suggestions.
In our case, it's going to take a prettttty ugly circular buffer, since there is no hard limit to the amount of data passed to the callbacks. floats, triggers, arrays, and they all take a copy since the audio app running underneath our wrapper is going to do something else with that storage space as soon as it can.
I agree this is the ideal solution, but we can't really have a fixed size circular buffer, so then we need memory allocations again..
On Tue, Oct 4, 2011 at 6:08 AM, Robert Bielik
<email@hidden> wrote:
For this kind of purpose I'm using a FIFO (wrapped circular buffer) to store object references (think placement new), then extracting info in
the GUI thread. No lock on audio side, and next to zero execution time.
Regards,
/Rob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden