Re: [LAU] Latency and jack parameters clarification

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Linux Audio Users <linux-audio-user@...>
Date: Sunday, June 30, 2013 - 7:19 am

--089e015369ee0614f204e059f029
Content-Type: text/plain; charset=UTF-8

On Sun, Jun 30, 2013 at 7:42 AM, James Stone wrote:

In trying to get support with this usb problem in kernel 3.8:

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

--089e015369ee0614f204e059f029
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 30, 2013 at 7:42 AM, James Stone <jamesmstone@gmail.com> wrote:
In trying to get support with this usb problem in kernel 3.8:
ht=
tps://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 usin=
g 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 he=
lp out here!Actually, re-reading his reply, I think he has work=
ed 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 th=
e usb driver.. Seems to me it must be a kernel-side problem because it work=
s 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 d=
river was really using=20
the equivalent of 5.5 frames/period and 8 periods/buffer. This means=20
the actual latency (as far as the kernel is concerned) was 5.5 / 44100 =3D
0.125 ms, as I mentioned earlier. The usbmon trace for 3.8 shows that=20
the audio driver was really using the equivalent of 11 frames/period and
8 periods/buffer, for a latency of 11 / 44100 =3D 0.25 ms."Ja=
mes

--089e015369ee0614f204e059f029--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Latency and jack parameters clarification, James Stone, (Sun Jun 30, 6:42 am)
Re: [LAU] Latency and jack parameters clarification, James Stone, (Sun Jun 30, 7:19 am)