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

PrevNext  Index
DateFri, 15 Apr 2011 19:57:18 +0200
From Stéphane Letz <[hidden] at grame dot fr>
To[hidden] at chriscaudle dot org
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToChris Caudle Re: [Jack-Devel] is this latency coming from ALSA, jack, or ardour?
Follow-UpPaul Davis Re: [Jack-Devel] is this latency coming from ALSA, jack, or ardour?
Le 15 avr. 2011 à 19:50, Chris Caudle a écrit :

> 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
> 


jackd -d alsa -h

Stéphane 
PrevNext  Index

1302890268.18824_0.ltw:2,a <27D9F1FB-70F8-4D86-BD11-C8DD981AE86E at grame dot fr>