Re: [Jack-Devel] is this latency coming from ALSA, jack, or ardour?

On Fri, Apr 15, 2011 at 2:20 PM, Chris Caudle <[hidden]> wrote:
> On Fri, April 15, 2011 7:52 am, Paul Davis wrote:
>> To get a useful value, multiple frames/period by the periods/buffer
>> value. Subtract this from the number shown by jack_iodelay. Divide by
>> two.
>> Then give this value to the JACK backend with the -I and -O flags,
>> which specify "system input latency" and "system output latency".
>
> Not sure I'm following here.
> This is what I have at the moment:
> Using qjackctl to start jack, the setup dialog shows 1024 frames/period, 3
> periods/buffer.
>
> Multiplied those together to get 3072 frames/buffer.

> Ran jack_iodelay and it printed "1024.000 frames     23.220 ms"

you've got a digital loopback, it appears.

my instructions were wrong. sorry. subtract frames/period from
jack_iodelay's answer, then divide by 2 for the input/output numbers.
note that dividing by 2 is a heuristic: if you used different devices
for A/D and D/A, it would not necessarily be correct.

1302891755.22008_0.ltw:2,a <BANLkTim0nr2YrEWXooEnAY3uh4ZgLEoeuw at mail dot gmail dot com>