Re: AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
Re: AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
- Subject: Re: AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
- From: William Stewart <email@hidden>
- Date: Mon, 9 Oct 2006 12:32:42 -0700
The RenderNotify calls are done and expressed in *output* scope of an AU
The Input callbacks are expressed (and done) on the input scope/
element of an AU
So, you have to look at:
Render Notify - the format for the output scope (and element)
Input Callback - the format for the input scope and element
Bill
On 08/10/2006, at 3:59 AM, Craig Bakalian wrote:
Hi,
I have just discovered that there are two buffers with a
mDataByteSize of 2048 in a callback set up with
AudioUnitAddRenderNotify. However, when setting up a
AudioUnitRender and its callback the mDataByteSize is 128 with two
buffers. So, if I use AudioUnitAddRenderNotify to capture data and
store it in memory, and then pull on that data with an
AudioUnitRender, weird stuff happens, unreliable stuff.
What is up with this?
Craig Bakalian
www.ethinkingcap.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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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