Re: does CoreAudio respect the server plugin driver properties?
Re: does CoreAudio respect the server plugin driver properties?
- Subject: Re: does CoreAudio respect the server plugin driver properties?
- From: Frederic De Jaeger <email@hidden>
- Date: Tue, 04 Nov 2014 15:29:57 +0100
IMHO, 441 samples for your circular buffer size looks way too small. I would pick a much larger value, if I were you. I would not be surprise if a so small value could confuse CoreAudio. All the audio interfaces I have show a Max IO Buffer Size greater than 4096. Usually, the IO Buffer size is set to 512 frames (but to be able to provide that size, your circular buffer must be at least twice as big).
Have you look at how your driver responds to:
kAudioDevicePropertyBufferFrameSize = 'fsiz',
kAudioDevicePropertyBufferFrameSizeRange = 'fsz#',
It does not harm latency to have a big circular buffer. CoreAudio always tries to write the closest possible to the "Tape head". But if there is more room on the tape, there is less risk for an overrun and CoreAudio feels happier.
Fred
_______________________________________________
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