Re: AUGraph deadlocks
Re: AUGraph deadlocks
- Subject: Re: AUGraph deadlocks
- From: Ross Bencina <email@hidden>
- Date: Mon, 05 Dec 2011 11:44:39 +1100
On 5/12/2011 10:55 AM, Paul Davis wrote:
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);
For GUI I agree, and admittedly I don't use AUGraph, but my
understanding is that there is no problem calling SetParameter() or
MIDIEvent() on an AU from an audio thread/callback. In the
SetParameter() case, how else would one implement sample-synchronous
parameter automation? Similarly, if your master MIDI scheduler runs
synchronously with the audio thread it makes sense to feed MIDI events
to the plugin there too.
This has been working for me for a few years. I've never heard of a
crash related to doing it this way.
the second happens in the Render callback.
Ross.
_______________________________________________
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