Apple

Thank you very much, you are correct. I took the name AUGraphSetNodeInputCallback() to be aligned with the name kAudioOutputUnitProperty_SetInputCallback, when in fact it is sort of the opposite. Unfortunate choice of names that could have been mitigated by the documentation if it were not so terse.

Unfortunately it seems I had two problems and that solved just one of them.

Steven J. Clark

VGo Communications

From: matt ingalls [mailto:email@hidden]
Sent: Wednesday, June 4, 2014 4:21 PM
To: Steven Clark
Cc: CoreAudio API
Subject: Re: VPIO unit in a graph

it’s been a while since i’ve done this, but i think you might have your render and input callbacks swapped:

AUGraphSetNodeInputCallback should be used for your own output (as the “input” for the VPIO's output)

and

kAudioOutputUnitProperty_SetInputCallback to get the VPIO’s (microphone) input

-matt

On Jun 4, 2014, at 12:46 PM, Steven Clark <email@hidden> wrote:

I’ve been trying without success to use Apple’s VPIO unit in an AUGraph.

I’ve set up a little test application. It always instantiates its audio units by creating an AUGraph. That much works. I can use either the AUGraph API calls or the AudioUnit calls after that.

[sjc:] remainder of message elided…

Steven J. Clark

VGo Communications

_______________________________________________
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

References:
	>VPIO unit in a graph (From: Steven Clark <email@hidden>)
	>Re: VPIO unit in a graph (From: matt ingalls <email@hidden>)