Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: I/O Latency (Was: Layman with a mission)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I/O Latency (Was: Layman with a mission)

Subject: Re: I/O Latency (Was: Layman with a mission)
From: Philippe Wicker <email@hidden>
Date: Thu, 14 Oct 2004 08:13:28 +0200

On Oct 13, 2004, at 7:17 PM, William Stewart wrote:

By "now" I mean this. On the input side, the "now" is the real, "what is the time now" minus the safety offset of the driver. So, if the safety offset is 24 samples, then "now" for input is the real now - 24 samples - so you get the 64 samples that were written in up to 24 samples ago. On output, "now" is the real now plus the safety offset of the driver.

What are the factors that determine the safety offset value? I can think of a protection against a possible jitter in the OS wake up time? Or to give the time for these 64 samples to be transmitted on the USB, Firewire cable, etc from the device to the computer? Any other factor?

Thanks,

Philippe


Bill


Philippe Wicker
email@hidden

_______________________________________________
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


Follow-Ups:

Re: Safety Offset (Was: I/O Latency (Was: Layman with a mission))
From: Jeff Moore <email@hidden>


References:  
  >Re: I/O Latency (Was: Layman with a mission) (From: William Stewart <email@hidden>)




Prev by Date:
AUParameterSet/Event Notification and 'generic' UIs

Next by Date:
Re: I/O Latency (Was: Layman with a mission)

Previous by thread:
Re: I/O Latency (Was: Layman with a mission)

Next by thread:
Re: Safety Offset (Was: I/O Latency (Was: Layman with a mission))

Index(es):

Date
Thread