View Issue Details

IDCategoryLast Update
0001631other2013-07-15 00:13
ReporteroofusAssigned Tox42 
Status closedResolutionfixed 
PlatformDual 666MHz PIIIOSMandrivaOS Version2007
Product Version 
Fixed in Version3.0 
Summary0001631: When locking to MTC, if the MTC generator and Ardour are not locked to the same ref, they drift apart.
DescriptionWhen locking to MTC, if the MTC generator and Ardour are not locked to the same ref, they drift apart. This in itself is not the problem, this could be argued to be expected. The problem as I see it is that Ardour does not give any indication that this is happening. Over a long period the difference between the incoming MTC and Ardours timeline could be significant.

There are possibly two solutions.

1. Ardour slews to track the incoming MTC.

2. Ardour indicates that the timeline and incoming MTC are out of sync. This could be indicated by some flashing indicator and/or a clock to show the difference between the two.
TagsNo tags attached.


related to 0001608 closed Lock indication when received MTC is good and being locked to. 
related to 0001775 feedback The config option "timecode-source-is-synced" from the ardour.rc file should be exposed to the user as a configurable option. 



2007-05-12 21:12

developer   ~0003955

What must be happening at the moment is that Ardour sees the first incoming frame of MTC, uses that as its starting point then moves forward at it's own time line reference, ignoring subsequent incoming MTC.


2013-07-15 00:13

administrator   ~0015108

should be fixed in 3.0 (after complete overhaul of MTC slave & generator)

Issue History

Date Modified Username Field Change
2007-04-25 12:05 oofus New Issue
2007-04-26 21:45 oofus Relationship added related to 0001608
2007-05-12 21:12 oofus Note Added: 0003955
2007-09-05 09:50 oofus Relationship added related to 0001775
2010-07-22 12:29 oofus cost => 0.00
2010-07-22 12:29 oofus Target Version => 3.X
2013-07-15 00:13 x42 Note Added: 0015108
2013-07-15 00:13 x42 Status new => resolved
2013-07-15 00:13 x42 Fixed in Version => 3.0
2013-07-15 00:13 x42 Resolution open => fixed
2013-07-15 00:13 x42 Assigned To => x42
2013-07-15 00:13 x42 Status resolved => closed