Re: question about AudioUnit render buffer size
Re: question about AudioUnit render buffer size
- Subject: Re: question about AudioUnit render buffer size
- From: William Stewart <email@hidden>
- Date: Fri, 16 Apr 2010 13:06:29 -0700
On Apr 16, 2010, at 11:32 AM, Christopher Penrose wrote:
>
>
> On Apr 16, 2010, at 11:06 AM, William Stewart wrote:
>
>> Yes, that is reasonable. But to be prepared you need to actually look at the max frames. For instance, we have seen bugs where the I/O size changes when the screen goes dark (from say 1024 to 4096), and upstream code not being prepared to deal with this. The AU's max frames was set to 4096.
>
> Is there any guarantee or attempt for such i/o size changes to be an integral of kAudioSessionProperty_PreferredHardwareIOBufferDuration?
I'm not sure what you are asking...
If you are successful with this (you get the size you want) and you are currently active and you are non-mixable and you are not interrupted, then the IO size won't change.
If any of the preceding are false, then it *shouldn't* change, but I would not be prepared to make a guarantee without further thinking about this some - the main concern is what we might want to change in the future. I'm not sure if this is a known or unknown unknown :)
Bill
>
> Christopher
>
>
_______________________________________________
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