Re: AUGraph deadlocks
Re: AUGraph deadlocks
- Subject: Re: AUGraph deadlocks
- From: Paul Davis <email@hidden>
- Date: Mon, 05 Dec 2011 11:42:54 -0500
On Mon, Dec 5, 2011 at 11:02 AM, patrick machielse <email@hidden> wrote:
> The processingRecipe prescribes the AudioUnit settings to use f(t). The settings change continuously during processing (whether the user changes the recipe or not) and should be adjusted on each render loop.
>
> Performing these adjustments from the 'outiside' seems to be harder to achieve than performing them from the renderCallback function. Also, the implementation of my custom audio unit would require more care (treading wise).
its not harder. its also the intended design of just about every
callback-driven API of the last 15 years.
i think you've established that you're not actually trying to do
anything particularly unusual. i strongly encourage you to stop
thinking so hard and use the same approach that everybody else does,
and which has been described a couple of times in this thread. you're
not doing rocket science. this is standard audio graph/data processing
stuff. set the parameters from where the changes are driven (thread
wise); in the render callback *just render*. its really that simple.
_______________________________________________
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