in & out Callbacks
in & out Callbacks
- Subject: in & out Callbacks
- From: Lubor Prikryl <email@hidden>
- Date: Sat, 12 Feb 2005 18:53:14 +0100
Hi,
My app is processing a stack of effects. I did the following:
- in the input callback I copied data from
mBuffers[].mData to my buffers
- in the output callback I processed the data and copied them back to mBuffers[].mData
On certain systems generally with higher CPU load (but NOT overload) my application clicks and pops from time to time.
To fix it, I changed to this:
- in the input callback I do nothing
- all the work was done in the output callback
My questions:
- What is better? (I think the second, but it cannot be used generally)
- For the first approach, is it guaranteed that callbacks are called exactly i-o-i-o-i-o-i-o-i-o-i-o... for one device? (I perform checking, it actually seems to be regular)
- The second approach can't be used with USB class driver or with two externally synced devices unless I would establish circular buffers and increase latency. I expect some non-regular alternating here, correct?
- If I would replace the AudioDeviceAddIOProc based HAL i/o by an AudioUnit i/o, I would get to the bad situation with the usb class compliant driver and externally synchronized devices, I would open two AUs to handle, but only one i/o AU is allowed per one Graph.
Thanks for a hint
Lubor
_______________________________________________
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