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

PrevNext  Index
DateSat, 16 Apr 2011 17:21:16 +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 à 20:29, Chris Caudle a écrit :

> On Fri, April 15, 2011 7:54 am, Paul Davis wrote:
>> Current versions of Ardour do not get the capture
>> alignment correct in all cases. I am not sure whether
>> yours is one of those cases.
> 
> I am running Ardour 3 build alpha 4.  Do you mean current as in alpha
> builds, or current as in 2.8.11?
> 
> I don't know if you saw the original description I wrote from several days
> ago, but I don't see how this case can get any simpler.
> Basically route a track to a physical output, connect that physical output
> back to a physical input, and route that input to another track.
> Trying to simulate a perfect percussionist who hears a click track in the
> headphones, and synchronizes playing exactly to the click track, then
> another percussionist listens to the first track, and lays down another
> track while keeping time perfectly to the first track heard in headphones.
> 
> I know that in reality you probably would not keep changing reference
> track, everyone would be listening to the click.  And just to be clear, I
> have no complaint now with A3 alpha 4 with jack 2 SVN and my PCI card
> (envy24 based).  That works well.

OK

> A3 alpha4 with jack 1.9.6 seemed broken,

The new API for latency management was introduced *after* jack 1.9.6, so this may explain that.

> and A3 alpha4 with jack2 SVN and
> a USB interface still seems off.

And here it may be an incorrect report of latency at ALSA level?

Stéphane 
PrevNext  Index

1302967294.32137_0.ltw:2,a <4956C0BB-29AA-40A3-8038-2D1F434F8E61 at grame dot fr>