Re: AudioUnitScheduleParameters
Re: AudioUnitScheduleParameters
- Subject: Re: AudioUnitScheduleParameters
- From: William Stewart <email@hidden>
- Date: Mon, 11 Apr 2005 15:35:29 -0700
On 11/04/2005, at 2:43 PM, Ev wrote:
On Apr 11, 2005, at 4:20 PM, William Stewart wrote:
RenderNotify is one API call (so you pass in a refCon for that) -
that is the pre/post calls
RenderCallback is another API call (so you can pass in a different
refCon for that if you want) - that's the call to give input to
the AU
But you're saying that the pre-RenderNotify is the only place I can
schedule parameters. The RenderCallback is too late for that.
The render callback is too late - you are already in the AU's render
logic at that time. Decisions about what to do may already have been
made.
===
For each RenderNotify proc I set up for an audio unit in the graph,
the proc gets called for each audio unit i associated it with. For
2 audio units with a RenderNotify proc attached to them, the
procedure gets called 4 times - twice before the render, twice
after the render.
Yes
Additionally, the only way to tell for *which* audio unit the
procedure was called is to use the refCon. Is this correct?
I guess so, if you are sharing the same proc between the AUs.
Bill
Ev
Technical Knowledge Officer
Head Programmer/Designer
Audiofile Engineering
http://www.audiofile-engineering.com/
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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