Re: I/O Latency (Was: Layman with a mission)
Re: I/O Latency (Was: Layman with a mission)
- Subject: Re: I/O Latency (Was: Layman with a mission)
- From: Dennis Gunn <email@hidden>
- Date: Wed, 13 Oct 2004 16:56:02 +0900
On Oct 13, 2004, at 3:57 PM, Philippe Wicker wrote:
On Oct 13, 2004, at 2:55 AM, William Stewart wrote:
Great explanations. They give an accurate picture.
Is this good enough? Remember, sound takes 1msec to travel a foot, so the latency for you to hear my guitar playing if you are 20 feet away from my speaker is 20msecs, an orchestra has at least 50msecs of latency from side to side...etc..., enough for one day I think.
>From what I've read here and there and from my personal experience the latency "problem" is not relevant for people listening to the music but for the musician doing self-monitoring. After all, a couple of ms is within an acceptable delay range for most of us (if not all of us). However, some singers have been reporting "phase" problems between sound coming from their throat and sound coming from the output of the DAW. When the instrument produces sharp attack (e.g. a hard strike on a guitar string) then you've got a disturbing impression of uncorrelated sound and hand movement. I'm perfectly aware that going under the 64 samples buffer size is risky and therefore maybe that musicians should accept that self-monitoring using DAWs has some limitations and cannot completely replace the direct monitoring.
Precisely.
I replied to William's other points in longer post that is actually so long it is awaiting moderation but probably the biggest the thing that I am asking about here specifically is if it would be possible to simply have a mode where the clock of the application is locked directly to the clock of the IO and there is no need to have buffers to accommodate jitter or unmatching clock rates or whatever (yes I know I am a layman and "simply" is easy for me to say) . I assume that in as much is as it relates to this latency issue that is the single biggest difference between OS9 where there was no big buffer between the application and the IO hardware and OSX where there is a kind of huge one. For somebody using a DAW it just is not really a consideration, we do not want the OS to do the jitter compensation since jitter is an issue between clock that are not synced, nor do we want the real time SRC. What we want is for everything to be locked up in tight sync and run a low latency with no processing being done outside the DAW app whatsoever.
_______________________________________________
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