On Tue, Mar 9, 2010 at 2:00 AM, Maarten Lankhorst <[email protected]> wrote: > I don't know about any automated way, but one could conceivably just > write a program that outputs a sound at a certain frequency and tries > to find that frequency back in the input.
No need for a frequency - a single pulse would do it, as outlined at http://manual.audacityteam.org/index.php?title=Latency_Test https://ccrma.stanford.edu/~matt/latencytest/ http://www.music.mcgill.ca/~ich/research/icmc01/latency-icmc2001.pdf > But it wouldn't be needed to > determine how much latency wine itself adds. You can deduce that by > simple math, since there is a upper bound on it. :) That's fine in theory, but as Reagan said, "trust, but verify". There are a lot of probably's, if's, and but's in what you wrote, and many layers, so it's quite reasonable to want a simple automated check to actually measure the final latency. - Dan
