Re: AU, what samplerate and buffersize?
Re: AU, what samplerate and buffersize?
- Subject: Re: AU, what samplerate and buffersize?
- From: William Stewart <email@hidden>
- Date: Tue, 3 Jan 2006 15:35:18 -0800
On 03/01/2006, at 1:15 PM, Urs Heckmann wrote:
Am 03.01.2006 um 21:25 schrieb William Stewart:
kAudioUnitProperty_MaxFramesPerSlice
- this tells you the *maximum* num of frames that an AU can be
asked to produce at a given time. It can't be changed without
reinitializing the AU. A host is able to call an AU for any number
of frames to render up to that number.
Uhm... is thread safety guaranteed then?
Yes - that is a responsibility of the host.
I mean, if I need to malloc enough memory to hold temporary results
i.e. to feed multiple output busses upon their separate render
calls (first call renders data for all busses, next calls fills
these busses, you remember that issue...), I'd probably trash an
old buffer and malloc a new buffer if that property changes. I
wouldn't wanna do that during a render call or if a render call
could interrupt the malloc...
Why isn't this bound to happen in unitialized state? It would sound
more logical to me if it was.
Ummm... that is what I said. Max frames can only be changed through
reinitializing the AU (ie. uninit, change max frames, init)
Bill
Cheers,
;) Urs
urs heckmann
email@hidden
www.u-he.com
--
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