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: Paul Davis <email@hidden>
- Date: Mon, 23 May 2011 10:33:36 -0400
On Mon, May 23, 2011 at 10:21 AM, Brennon Bortz
<email@hidden> wrote:
> 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)?
if you are interacting with an audio interface via the HAL (i.e. OS X,
using CoreAudio), the render callback is going to execute in a thread
created on your behalf by the CoreAudio libraries. any techniques you
use there must be non-blocking and roughly linear-RT (i.e. to process
N samples takes A*N + B cycles, where A and B are roughly constant).
if you running AU's in an offline mode (i.e. totally decoupled from
any periodic processing callback), then you will be able to run them
in whatever thread you want, and you can do whatever you want to share
the data since you're not running with any realtime constraints. you
could even malloc more space and use some complex and slow messaging
system if you wanted to.
i assumed you were facing the former challenge.
_______________________________________________
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