Re: buffer size magical reduction
Re: buffer size magical reduction
- Subject: Re: buffer size magical reduction
- From: David Plans <email@hidden>
- Date: Sun, 28 Nov 2010 16:40:28 -0500
On Nov 28, 2010, at 3:43 PM, Paul Davis wrote:
> you get something supported by the h/w and other layers of the
> CoreAudio API; you can find out its value as described by the quoted
> sentence you mentioned.
But the thing is, we consistently get _half_ of the buffersize we ask for...that is, no matter what we ask for, we get exactly that, I can't see why.
Surely, if it had to do something with hardware supported, there would be some immovable low/high limit that I'd hit when I set it very low or very high?
Which isn't the case, it just gets cut in half.
> btw, PureData doesn't "have" a blocksize per-se that matters in this
> sense.. Its quite happy to adapt to the blocksize imposed by outside
> factors, like the audio h/w, OS audio API etc. etc.
Well, by 'have' I meant that Miller Puckette wrote:
#define DEFDACBLKSIZE 64
into s_stuff.h and that traditionally, that's PD's blocksize
_______________________________________________
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