Ardour can generate timecode and thus act as timecode <dfn>master</dfn>,
providing timecode information to other applications. Ardour can also be
<dfn>slaved</dfn> to some external source in which case the playhead
Ardour can generate timecode and thus act as timecode <dfn>master</dfn>,
providing timecode information to other applications. Ardour can also be
<dfn>slaved</dfn> to some external source in which case the playhead
Combining the timecode slave and generator modes, Ardour can also
<dfn>translate</dfn> timecode. e.g create LTC timecode from incoming MTC.
</p>
Combining the timecode slave and generator modes, Ardour can also
<dfn>translate</dfn> timecode. e.g create LTC timecode from incoming MTC.
</p>
This is pretty straightforward: simply turn it on. The MTC and MIDI-Clock
generator do not have any options. The LTC generator has a configurable
output level. JACK-transport cannot be <em>generated</em>. Jack itself is
This is pretty straightforward: simply turn it on. The MTC and MIDI-Clock
generator do not have any options. The LTC generator has a configurable
output level. JACK-transport cannot be <em>generated</em>. Jack itself is
specifies 29.97df as 30000/1001 frames per second, not all hardware devices
follow that standard. The checkbox
<kbd class="option">Lock to 29.9700 fps instead of 30000/1001</kbd> allows
specifies 29.97df as 30000/1001 frames per second, not all hardware devices
follow that standard. The checkbox
<kbd class="option">Lock to 29.9700 fps instead of 30000/1001</kbd> allows
When enabled, the external timecode source is assumed to use 29.970000 fps
instead of 30000/1001. SMPTE 12M-1999 specifies 29.97df as 30000/1001. The
<abbr title="specification">spec</abbr> further mentions that drop-frame
timecode has an accumulated error of -86 ms over a 24-hour period.
Drop-frame timecode would compensate exactly for a NTSC color frame rate
of 30 * 0.9990 (ie 29.970000). That is <em>not</em> the actual rate. However,
When enabled, the external timecode source is assumed to use 29.970000 fps
instead of 30000/1001. SMPTE 12M-1999 specifies 29.97df as 30000/1001. The
<abbr title="specification">spec</abbr> further mentions that drop-frame
timecode has an accumulated error of -86 ms over a 24-hour period.
Drop-frame timecode would compensate exactly for a NTSC color frame rate
of 30 * 0.9990 (ie 29.970000). That is <em>not</em> the actual rate. However,
- some vendors use that rate — despite it being against the specs
- — because the variant of using exactly 29.97 fps yields zero timecode
- drift.
+ some vendors use that rate—despite it being against the
+ specs—because the variant of using exactly 29.97 fps yields zero
+ timecode drift.
<p>
The <dfn>LTC</dfn> slave decodes an incoming LTC signal on a JACK audio
port. It will auto-detect the frame rate and start locking to the signal
<p>
The <dfn>LTC</dfn> slave decodes an incoming LTC signal on a JACK audio
port. It will auto-detect the frame rate and start locking to the signal
<p>
Ardour's MTC slave parses <dfn>full timecode messages</dfn> as well as
MTC <dfn>quarter-frame messages</dfn> arriving on the
<p>
Ardour's MTC slave parses <dfn>full timecode messages</dfn> as well as
MTC <dfn>quarter-frame messages</dfn> arriving on the