Hi all, I must admit I am pushing it, but (test-wise) I configure my CoreAudio server plugin with a 10ms circular buffer (i.e. 441 sample frames at 44.1kHz, following is all at 44.1kHz), accordingly the plugins answers kAudioDevicePropertyZeroTimeStampPeriod request with 441. No matter how the plugin answers the kAudioDevicePropertySafetyOffset request DoIOOperation (kAudioServerPlugInIOOperationWriteMix) is called with upto 441 sample frames and a sample time of upto 610+safety offset sample frames in the future.
Why does CoreAudio think the plugin can receive 441 sample frames at once (when a non-zero kAudioDevicePropertySafetyOffset was provided?) and why does CoreAudio think the plugin can handle upto 610+safety offset+441 sample frames in the future? CoreAudio (via HALLab Default device alert) seems to call DoIOOperation at least 150 sample frames in the future. Which is an inherent “safety offset” of 3.4ms. What would be the minimal and what the optimal buffer size in sample frames (or msec) the CoreAudio server plugin should provide? Does this scale well with high channel counts? Cheers and thanks, Hagen
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
