3D Mixer Bug or User Error?
3D Mixer Bug or User Error?
- Subject: 3D Mixer Bug or User Error?
- From: Chandrasekhar Ramakrishnan <email@hidden>
- Date: Thu, 21 Dec 2006 07:40:01 -0800
I stumbled across an inconsistency in the behavior of the 3D Mixer
compared to the Matrix Mixer.
I'm creating an AudioBufferList via AUOutputBL::Allocate, passing in
my max frames per slice as the argument. When I render the Matrix
Mixer, it updates the mDataByteSize in the buffers of the buffer list
to match what would be expected given the inNumberFrames I asked for.
The 3D Mixer, however, does not do this -- it leaves the mDataByteSize
at maxFramesPerSlice * sizeof(float) (for a mono buffer). This
behavior is causing my AudioConverter to complain. It returns an
'insz' error, apparently because of the decrepency between the number
of frames I ask it to convert and the size of the buffer.
The workaround is easy to implement -- I check if my AU is a 3D Mixer
and, if so, I tweak the mDataByteSizes -- but I'd like to know what
the correct behavior of an AU is in general: is it safe to expect them
to return correct mDataByteSizes, or should I always do the correction
myself?
Thanks and Happy Holidays!
- sekhar
--
C. Ramakrishnan email@hidden
Illposed Software http://www.illposed.com
_______________________________________________
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