View Issue Details

IDCategoryLast Update
0001775features2013-07-15 00:28
ReporteroofusAssigned To 
ReproducibilityN/A 
Status feedbackResolutionreopened 
PlatformDual 666MHz PIIIOSMandrivaOS Version2007
Product Version2.0 
Fixed in Version3.0 
Summary0001775: The config option "timecode-source-is-synced" from the ardour.rc file should be exposed to the user as a configurable option.
DescriptionThe config option "timecode-source-is-synced" from the ardour.rc file should be exposed to the user as a configurable option.

Vital to be able to set this when chasing MTC. Currently the default is 'yes', I would guess that this doesn't suit most peoples setups. In a setup where the timecode source isn't synced, MTC chase works but drifts, with no indication that this is happening.

As a new feature to extend this, I would like to see 3 clocks.....somewhere. One showing the transport position, one showing the incoming MTC and the third showing the difference between them. It then becomes trivial to see that chasing is happening and happening accurately. Maybe this could be added to the Big Clock.
TagsNo tags attached.

Relationships

related to 0001631 closedx42 When locking to MTC, if the MTC generator and Ardour are not locked to the same ref, they drift apart. 

Activities

oofus

2007-09-07 15:25

developer   ~0004347

Made a better note of how Pyramix handles chasing timecode. It has 4 chase modes; none, hard, soft and vari.

None - Obviouse I think
Hard - Chase the incoming TC but if that TC either 'goes away' or drifts out of time with the timeline, stop the transport.
Soft - Chase the incoming TC but if that TC either 'goes away' or drifts out of time with the timeline, stop chasing the incoming TC, but keep the transport rolling.
Vari - Chase the incoming TC, if it drifts out of time with the timeline vari speed to re-sync.

I quite like these options, apart from none, that's the equivalent of internal.

oofus

2007-10-25 15:43

developer   ~0004505

The config option "timecode-source-is-synced" from the ardour.rc, is now available as a user configurable option.

The further comments about keeping track of drifting Timecode still stand.

x42

2013-07-15 00:17

administrator   ~0015109

fixed with MTC+LTC overhaul in 3.0

x42

2013-07-15 00:28

administrator   ~0015110

sync mode is not yet configurable. Each slave currently has appropriate default behaviour (e.g. MTC: hard-sync; LTC: fly-wheel)

Issue History

Date Modified Username Field Change
2007-07-18 12:30 oofus New Issue
2007-09-05 09:50 oofus Relationship added related to 0001631
2007-09-07 15:25 oofus Note Added: 0004347
2007-10-25 15:43 oofus Note Added: 0004505
2010-07-22 09:45 oofus cost => 0.00
2010-07-22 09:45 oofus Target Version => 3.X
2010-12-31 13:46 oofus Status new => feedback
2013-07-15 00:17 x42 Note Added: 0015109
2013-07-15 00:17 x42 Status feedback => closed
2013-07-15 00:17 x42 Resolution open => fixed
2013-07-15 00:17 x42 Fixed in Version => 3.0
2013-07-15 00:28 x42 Note Added: 0015110
2013-07-15 00:28 x42 Status closed => feedback
2013-07-15 00:28 x42 Resolution fixed => reopened