- From: Stephen Band <stephband@cruncher.ch>
- Date: Sat, 30 Aug 2014 21:46:48 +0200
- To: Alex Russell <slightlyoff@google.com>
- Cc: public-audio@w3.org
Received on Saturday, 30 August 2014 19:47:16 UTC
It's nothing to do with the UI really. You're doing well if you get less than 40ms out of a standard sound card, but if you use a good external audio interface you could see as low as 5ms. Above 15-20ms is when the ear starts to hear two distinct sounds, although it can be uncomfortable to sing and monitor with a latency of >10ms. So I would say a good latency would be <10ms. But good luck getting there :) On 30 Aug 2014 21:21, "Alex Russell" <slightlyoff@google.com> wrote: > What's a "good" number for this? I'm assuming less than a UI frame (16ms) > is preferred? I'm seeing ~50ms on Chrome Dev/OS X/MBP and FF doesn't seem > to detect all of the signals in my view. > > > On Sat, Aug 30, 2014 at 11:24 AM, Stephen Band <stephband@cruncher.ch> > wrote: > >> In case someone should find it useful, here's a round-trip latency tester: >> >> https://sound.io/latency/ >> >> >> >
Received on Saturday, 30 August 2014 19:47:16 UTC