Re: AUGraph deadlocks
Re: AUGraph deadlocks
- Subject: Re: AUGraph deadlocks
- From: Paul Davis <email@hidden>
- Date: Sun, 04 Dec 2011 18:55:47 -0500
On Sun, Dec 4, 2011 at 6:26 PM, patrick machielse <email@hidden> wrote:
> Thanks for your comments. The information is coming from the user, but not through any AudioUnit UI. My custom audio units don't have a UI, and I'm not using the default UI of any other bundled unit.
doesn't matter at all for the semantic discussion.
> At 'pre-render' time, the render thread first checks if there is a new processing 'recipe' available, and then updates all units in the graph according to the recipe for the current render time, using AUBase API.
you should apply the settings directly from your UI thread(s). they
will have no effect until the next Render call. if you need to make
them atomic, that will be a little more work, but probably not much.
> There is a clear division between the UI and the audio processing engine. At some point the render settings must be applied to the audio units. kAudioUnitRenderAction_PreRender seemed the best opportunity to me.
there are two things that have to happen, not one:
* the new settings must be supplied to the AU
* the AU must notice them and start to use them
the first happens from one or more UI threads (where UI encompasses
all possible forms of user interaction, include a GUI, MIDI, OSC, or
other control mechanisms); the second happens in the Render callback.
and you're done! :)
_______________________________________________
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