30 Jun
2013
30 Jun
'13
7:19 a.m.
On Sun, Jun 30, 2013 at 7:42 AM, James Stone <jamesmstone(a)gmail.com> wrote:
In trying to get support with this usb problem in kernel 3.8:
https://bugs.launchpad.net/bugs/1191603
I have been asked to provide info on what the period size in jack is and
how the round trip latency is calculated.
The dev can't see how with a 1ms latency (which is what jack is using with
a period size of 256 samples) the round trip latency is around 10ms.
I have quoted bits of the jack manual page but he doesn't find this
helpful and I have now reached the limits of my understanding of the matter
and can't find any more detailed descriptions on the web.
It would be great if someone with a more in-depth understanding could help
out here!
Actually, re-reading his reply, I think he has worked most of it out, and
the main problem was me not providing enough info.. But now it seems to
have got down to how jack actually communicates with the usb driver.. Seems
to me it must be a kernel-side problem because it works on 3.5 - but
apparently the code for 3.5 was not doing it the "right way"..
He writes:
"The usbmon trace for 3.5 shows that the audio driver was really using the
equivalent of 5.5 frames/period and 8 periods/buffer. This means the actual
latency (as far as the kernel is concerned) was 5.5 / 44100 = 0.125 ms, as
I mentioned earlier. The usbmon trace for 3.8 shows that the audio driver
was really using the equivalent of 11 frames/period and 8 periods/buffer,
for a latency of 11 / 44100 = 0.25 ms."
James