Re: [LAU] qjackctl and the hardware latency setting

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: "Maciej (Matchek) Bliziński" <maciej.blizinski@...>
Cc: <linux-audio-user@...>
Date: Wednesday, January 1, 2014 - 3:33 pm

On 01/01/2014 03:10 PM, Maciej (Matchek) Bliziński wrote:

nice writeup.

Once the 'problem' is understood and fixed, it'd be great to make a "how
to calibrate latency" walk-trough out of it. You already have nice
"before and after" screenshots.

> The workaround was to start jackd from command line and pass the -I and -O

If it's jackdbus that you're using, maybe qjackctl does not configure it
properly; or maybe you're just missing 'use dbus' in qjackctl's config?!
-- but those are only guesses. One could look in the source or bug Rui :)

A few things that may help to track things down:
'jack_control dp | grep latency'
prints the current configuration of jackdbus.

You can directly query the current port-latencies with 'jack_lsp -l'. It
lists the actual port-latencies as jack knows them, that includes
cycle-times, -I/-O configuration and latencies due to routing: eg.
effects with latencies, etc.

> It is possible (but not certain) that the problem was caused by qjackctl. I

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user

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

Messages in current thread:
[LAU] qjackctl and the hardware latency setting, Maciej (Matchek) Bliziński..., (Wed Jan 1, 2:10 pm)
Re: [LAU] qjackctl and the hardware latency setting, Robin Gareus, (Wed Jan 1, 3:33 pm)