Re: Difference between AUGraphConnectNodeInput() and kAudioUnitProperty_MakeConnection property
Re: Difference between AUGraphConnectNodeInput() and kAudioUnitProperty_MakeConnection property
- Subject: Re: Difference between AUGraphConnectNodeInput() and kAudioUnitProperty_MakeConnection property
- From: Chris Adamson <email@hidden>
- Date: Wed, 31 Mar 2010 13:40:58 -0400
Thanks, Bill. Setting up a callback is basically what I did in a third approach, which has the same sound problem as cited before. Like aurioTouch, this sets up a render callback on bus 0, and in the callback, it calls AudioUnitRender() to send samples right to the ioData parameter.
<http://pastie.org/897403>
I realize you said in your reply that I'd need to set up a callback on bus 1 for input (the kAudioOutputUnitProperty_SetInputCallback property?), but I don't see why this would be necessary when aurioTouch can do play-through by only setting up the one callback.
--Chris
On Mar 30, 2010, at 6:35 PM, William Stewart wrote:
> that won't work.
>
> It works on the desktop (and this is basically what AULab does), but on the device you need to handle input directly by installing the callback on bus 1 for input, then calling AudioUnitRender on bus 1 to get it. The connection won't do that for you
>
_______________________________________________
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