Re: HALOutputUnit (Pt 1)
Re: HALOutputUnit (Pt 1)
- Subject: Re: HALOutputUnit (Pt 1)
- From: Robert Grant <email@hidden>
- Date: Tue, 13 Jan 2004 09:12:11 -0500
Hi Bill,
I'm trying to understand exactly what happens in this situation - but
my brain's a bit slow this morning (every morning?!)
Do we really use SetInputCallback? I thought this was deprecated for V2
AUs?
Should it be SetRenderCallback?
And will the buffers presented in the callback be filled with the
captured audio? Or should we make a call back to the HALOutputUnit to
get buffers filled? I'm asking because it sounds like it's backwards
which I guess is how the HALOutputUnit generally does input :-)
Thanks,
Robert.
On Jan 9, 2004, at 7:05 PM, William Stewart wrote:
In the case of a device that doesn't have a in and out (for eg, USB)
the client can register a callback with the AUHAL unit
(kAudioOutputUnitProperty_SetInputCallback) - this then will call you
when the AUHAL unit has input data for you. Please note, due to some
bugs in CA-Panther this WASN'T working as shipped - however, with the
QT 6.5 update we fixed those (so this now works for Panther and Jaguar
systems)...
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.