View Issue Details

IDProjectCategoryView StatusLast Update
0004312ardourbugspublic2020-04-19 20:15
Reporterlhm100 Assigned Topaul  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0-alpha10 
Target Version3.0-beta3 
Summary0004312: Latency compensation issue
DescriptionA track played and looped back into the interface and recorded on a separate track does not time-allign well. The offset Latency is equal to the typical values calculated for Jack, but is uncompensated.

Does not appear to be a way to compensate for that latency. Jack -I and -O parameters appear to have no effect. [They do have an effect, and in a least a few cases, function correctly and solve the issue in 2.8.11.]

This issue is independent of Jack 1.9.7 in synchronous or asynchronous mode (although the latency value does change as one would expect)

Problem exists even with only 2 jack connections: "Track to hardware out" & "Capture to track in". All other connections removed.


Additional InformationSee:
http://ardour.org/node/4551

Ubuntu Studio 11.04
Updated to 2.6.39.4 kernel
Jackmp 1.9.7 rt via QjackClt
Ardour 3.a10
TagsNo tags attached.

Activities

paul

2011-09-14 19:53

administrator   ~0011508

alignment is perfect here.

lhm100

2011-09-15 02:13

reporter   ~0011517

Anything I can provide from here to help resolve issue? It is definitely not OK here - 22ms lag. One other test is to see if you can use the latency inputs to affect the timing, since I could not affect the timing at all with those inputs on 3a10, but could on 2.8. Thanks

paul

2011-09-15 02:25

administrator   ~0011518

i don't run jack2. so its hard to say if this is an issue with jack2 or something with ardour3. I've done *extensive* testing here (days and days) with many different i/o configuration, and a3 seems to be exactly correct given the information available. this is with current jack1.

lhm100

2011-09-16 00:34

reporter   ~0011528

Well... I'll run jack1 and see how that goes and report back. Should have results in a couple days... Many thanks.

lhm100

2011-09-19 05:56

reporter   ~0011537

With a change to Jack1, alignment is much better. Less than 1ms differential "out of the box". With a little manual tweaking of the input latency (-I) latency can be adjusted perfectly. So, issue is between A3 and Jack2. As discussed in the forum, A2.8.11 gets it right somehow with Jack2. Anyway, with Jack1, 3a10 works like one would expect. Thanks Paul.

vervelover

2011-11-17 11:26

reporter   ~0012104

I'm currently using jack2 on my studio setup. Is this issue to be resolved even for jack2? I'm asking because in this case I'd have to switch my whole setup to jack1, which can be painful.. Are there any other known shortcomings with jack2?

paul

2011-11-17 14:34

administrator   ~0012105

a3 and a2 have the same code for this, and jack1 and jack2 support the same API. i am not aware of any bugs at this time with either combination.if jack2 does not behave in the same way, it should be reported to the jack mailing list.

paul

2012-02-02 04:17

administrator   ~0012745

notes and IRC have confirmed that this issue is fixed with jack2 as of 1.9.8.

system

2020-04-19 20:15

developer   ~0022740

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2011-09-06 03:07 lhm100 New Issue
2011-09-06 09:34 cth103 cost => 0.00
2011-09-06 09:34 cth103 Target Version => 3.0-beta1
2011-09-14 19:53 paul Note Added: 0011508
2011-09-15 02:13 lhm100 Note Added: 0011517
2011-09-15 02:25 paul Note Added: 0011518
2011-09-16 00:34 lhm100 Note Added: 0011528
2011-09-19 05:56 lhm100 Note Added: 0011537
2011-11-15 15:01 cth103 Target Version 3.0-beta1 => 3.0-beta2
2011-11-17 11:26 vervelover Note Added: 0012104
2011-11-17 14:34 paul Note Added: 0012105
2012-01-10 20:46 cth103 Target Version 3.0-beta2 => 3.0-beta3
2012-02-02 04:17 paul Note Added: 0012745
2012-02-02 04:17 paul Status new => resolved
2012-02-02 04:17 paul Resolution open => fixed
2012-02-02 04:17 paul Assigned To => paul
2020-04-19 20:15 system Note Added: 0022740
2020-04-19 20:15 system Status resolved => closed