Re: Safety Offset (Was: I/O Latency (Was: Layman with a mission))
Re: Safety Offset (Was: I/O Latency (Was: Layman with a mission))
- Subject: Re: Safety Offset (Was: I/O Latency (Was: Layman with a mission))
- From: Herbie Robinson <email@hidden>
- Date: Thu, 14 Oct 2004 16:35:47 -0400
At 12:11 PM -0700 10/14/04, Jeff Moore wrote:
Because it's not an exact science, driver writers need to examine
their requirements carefully and do some profiling and
experimentation to figure out the best number to report as the
safety offset for their hardware.
Actually, for decent hardware, the optimum value is probably going to
vary quite a lot depending on the CPU speed and the number of CPUs.
Also, note that applications must have more buffers to do any of the following:
1. Support multiple interfaces.
2. Support audio processing on multiple CPUs (networked or local).
This is because they won't be able to do all the processing in a
single callback.
--
-*****************************************
** http://www.curbside-recording.com/ **
******************************************
_______________________________________________
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