Re: Sharing data from within a render callback
Re: Sharing data from within a render callback
- Subject: Re: Sharing data from within a render callback
- From: Brennon Bortz <email@hidden>
- Date: Mon, 23 May 2011 15:21:54 +0100
Thanks for the speedy response, Paul.
Is there any reason that the writing thread can't be the main application thread (on which the render callback must run)?
Best,
Brennon
On 23 May 2011, at 15:14, Paul Davis wrote:
> On Mon, May 23, 2011 at 10:08 AM, Brennon Bortz
> <email@hidden> wrote:
>> Hello,
>>
>> I'm building an iOS/AudioUnit app doing some processing of incoming signals using a Remote I/O unit. I have all of my processing in place, but now I'd like to be able to access current sample values from elsewhere in my application. I'm wondering what the best practice is for making sample value data available from within my render callback to other interested objects.
>
> copy them into one or more lock-free ringbuffers (FIFO's). lock-free
> ringbuffers require a single writing thread and a single reading
> thread. if you have more than 1 reading thread, you'll either need to
> add a read-lock, or use multiple ringbuffers (1 per reader).
Brennon Bortz
Software Researcher
Dundalk Institute of Technology
email@hidden
Ph.D. Composer & Researcher - Sonic Arts Research Centre
Queen's University, Belfast
email@hidden / 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