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

PrevNext  Index
DateFri, 15 Apr 2011 12:50:17 -0500
From Chris Caudle <[hidden] at chriscaudle dot org>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToPaul Davis Re: [Jack-Devel] is this latency coming from ALSA, jack, or ardour?
Follow-UpStéphane Letz Re: [Jack-Devel] is this latency coming from ALSA, jack, or ardour?
On Fri, April 15, 2011 7:52 am, Paul Davis wrote:
> Same as with any card:...
> then use ...jack_iodelay

Very cool.  I'll try to write down some notes as I play with it, because
it seems that there is no mention of that tool in the FAQ, and I did not
see an entry for the tool on trac.jackaudio.org.  Using google to search
jackaudio.org, the only mention I found of jdelay or jack_iodelay was in
the source tree.  This email is in fact the first that I have heard of the
tool.

> Then give this value to the JACK backend with the -I and -O flags,
> which specify "system input latency" and "system output latency".

Since jack_iodelay can measure in rather small increments,  I was a little
confused about whether that argument should be given to jack in
milliseconds or frames, and it turns out that "jackd --help" has no
mention of those flags, and the man page for jackd only has -I for audio
device ID or number of midi inputs, and -O is only number of midi outputs.
 This is with jackdmp SVN 4299.
Is that feature only in jack 1, or is it just not documented with jack2?

-- 
Chris Caudle
PrevNext  Index

1302889842.18085_0.ltw:2,a <396e738e27f0565d3f630ff46b20895d.squirrel at email dot powweb dot com>