Re: Add/Remove Render Notify more than once
Re: Add/Remove Render Notify more than once
- Subject: Re: Add/Remove Render Notify more than once
- From: William Stewart <email@hidden>
- Date: Mon, 22 Jan 2007 12:39:50 -0800
First the declarations:
AudioUnitAddRenderNotify( AudioUnit ci,
AURenderCallback inProc,
void * inProcUserData)
AudioUnitRemoveRenderNotify( AudioUnit ci,
AURenderCallback inProc,
void * inProcUserData)
The AU determines a notify by examining *both* the proc and the
user data as a key (that contains two values). Thus - you can use
the same static function with different user data as distinct
entries. Thus, when you remove a notification you have to provide
both the function ptr AND the user data for that notification entry
to remove.
On 28/12/2006, at 9:32 AM, Evan Olcott wrote:
This isn't in the documentation, so I thought I'd ask here:
* if I call AudioUnitAddRenderNotify and the callback was
previously added & already hooked in, is the adding skipped or is
it added for a second entry?
If the pair is already a member, it does nothing
* if I call AudioUnitRemoveRenderNotify and the callback doesn't
exist, do I just get an error as a result, no harm done, no
residual effect?
noErr is always returned - can't see how this would cause any harm
Bill
TIA
Ev
Technical Knowledge Officer
Head Programmer/Designer
Audiofile Engineering
--
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