2014-06-20 18:05 GMT+02:00 Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx>: > > > > On Fri, Jun 20, 2014 at 10:10 AM, Fons Adriaensen <fons@xxxxxxxxxxxxxx> > wrote: >> >> On Fri, Jun 20, 2014 at 09:23:58AM -0400, Paul Davis wrote: >> > On Fri, Jun 20, 2014 at 9:19 AM, Fons Adriaensen <fons@xxxxxxxxxxxxxx> >> > wrote: >> > >> > > On Fri, Jun 20, 2014 at 09:07:37AM -0400, Paul Davis wrote: >> > > >> > > > If you used jack_iodelay, it would do the math for you and show you >> > > > how >> > > > much extra latency is bing caused by the hardware (rather than the >> > > > period >> > > > size). >> > > >> > > jack_delay will do this as well, use the -E option. >> > > >> > >> > and make sure your distribution has packaged and included the new >> > version >> > of jack_delay :) >> >> Released 18 April 2011, that is more than three years ago :-) > > > It might even be in Debian Stable, then! :) > Hehe Anyway, thanks guys for enlightening me about improving the test results! Follow up question: from a theoretical perspective, is it likely a usb 2.0 interface would have similar transport latency as firewire? Usb 1 I suppose would be worse due to lower clockspeed. Regards, Robert _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
