Re: in/out data count difference in audio server plugin
Re: in/out data count difference in audio server plugin
- Subject: Re: in/out data count difference in audio server plugin
- From: Jeff Moore <email@hidden>
- Date: Wed, 27 Mar 2013 12:44:57 -0700
The cadence and rhythm of the calls to the driver have more to do with the scheduling of the client IO threads than anything else. There will never be a one-to-one mapping between what is read from the input and what is written to the output as the handling of the two are done completely differently with an eye toward only ever touch each time edge once. For example, the output mixer employs a coloring algorithm to know when all the clients have provided output for a given segment of time. This will always result in different kinds of access for writing data than for reading data (which is much more straight forward).
--
Jeff Moore
Core Audio
Apple
On Mar 27, 2013, at 12:30 PM, Eric Gorouben <email@hidden> wrote:
> We noticed that the audio server sends slightly more data to the plugin that it gets (inIOBufferFrameSize is bigger on output than on input) and this difference gets never compensated.
> We saw this also in the samples provided.
> What explains this difference?
_______________________________________________
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