Re: Buffer overrun management with TPCircularBuffer.. best way to do so?
Re: Buffer overrun management with TPCircularBuffer.. best way to do so?
- Subject: Re: Buffer overrun management with TPCircularBuffer.. best way to do so?
- From: Frederic De Jaeger <email@hidden>
- Date: Wed, 14 May 2014 12:28:09 +0200
Hi,
AUDeferredRenderer is the same kind of AudioUnit as AUConverter. You would feed data to it in the exact same way, with a callback (like renderModuleCallback in your gist).
AUDeferredRenderer's job is to call your callback in an auxiliary thread. From here, you are free to call libxmp directly without the need of using TCPCircularBuffer (In fact, there is some kind of a TCPCircularBuffer inside AUDeferredRenderer).
You probably need to have an intermediate buffer because the number of frames returned by xmp_get_frame_info might not be the same as what is requested to your callback. Or you may also have a look to kAudioUnitProperty_DeferredRendererPullSize, and set it to the number of frames returned by xmp_get_frame_info (provided it is a constant you can access when you configure the AUGraph)
If libxmp renders faster than the AUGraph, you should not have any issue (provided that you set kAudioUnitProperty_DeferredRendererExtraLatency to a value big enough. This property corresponds more or less to the size of the internal TCPCircularBuffer)
Hope that helps.
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