RE: AUHAL Full duplex issues
RE: AUHAL Full duplex issues
- Subject: RE: AUHAL Full duplex issues
- From: "Aridis-Lang, Simon" <email@hidden>
- Date: Mon, 9 Aug 2010 10:11:28 +1000
- Thread-topic: AUHAL Full duplex issues
I think I’ve solved problem 1 at least… I
didn’t think to use the input bus on AudioUnitRender rather than just passing
in the bus defined in the callback.
From: Aridis-Lang,
Simon
Sent: Friday, 6 August 2010 1:24
PM
To: email@hidden
Subject: AUHAL Full duplex issues
Hi,
I'm having some trouble configuring an AUHAL
device for full duplex operation. I have simplex built-in devices working
well on a MBP, however some of my USB interfaces are presenting errors when
calling AudioUnitRender.
My callbacks are configured as a
kAudioUnitProperty_SetRenderCallback for scope 0 for simplex output and full
duplex, and a kAudioOutputUnitProperty_SetInputCallback for scope 1 for simplex
input devices.
Is this correct or do I need to register a callback
for the input side as well and use bus numbers to determine which direction the
unit is processing? I've found the TN for input configuration on an
AUHAL, but can't find anything that talks about full duplex cases.
When I call AudioUnitRender I'm getting results
varying from -50 (MOTU UltraLite Mk3) to a recursive call to the callback and a
stack overflow!! (M-Audio Fast Track Ultra).
Also, one of my devices (an ESI U46) is not
honouring calls to kAudioUnitProperty_MaximumFramesPerSlice, instead calling
back with more frames than specified. Are there more steps to ensuring I
get a callback with a fixed (or maximum) number of frames? Or do I need
to realloc the AudioBuffer to fit the number of frames?
Regards,
Simon.
|
_______________________________________________
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