Re: AUGraph deadlocks
Re: AUGraph deadlocks
- Subject: Re: AUGraph deadlocks
- From: Brian Willoughby <email@hidden>
- Date: Mon, 05 Dec 2011 02:31:29 -0800
On Dec 4, 2011, at 16:44, Ross Bencina wrote:
In the SetParameter() case, how else would one implement sample-
synchronous parameter automation?
My understanding is that the AU Render() routine provided by Apple
breaks the buffer into pieces and calls the subclass Render() for
each piece, even if it's only one frame long. AudioUnitSetParameter
() includes inBufferOffsetInFrames, which controls the progression.
As far as your AudioUnit subclass is concerned, every Buffer is
calculated with parameters that do not change for the duration of the
Buffer, with the caveat that the Buffer can have any size between 1
frame and the maximum number of frames.
For the most part, sample-synchronous parameter automation would seem
to be an AU Host issue, with most of the AU engine code hidden deep
inside the C++ objects that Apple provides for AU developers.
Granted, I've never tested this in depth, but it all seemed to make
sense last time the topic crossed this list.
Brian Willoughby
Sound Consulting
P.S. You may be right, though, that some calls are necessary in
certain situations and also safe. I'm merely pointing out that
they're not necessary for sample-synchronous parameter automation as
far as I understand its inner workings.
_______________________________________________
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