X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F19_synchronization%2F03_timecode-generators-and-slaves.html;h=babca1496c24841d039b30299a8db0bb47ba50a2;hb=1321d4a5f39bf9163b6776dddc24d8ce151fd4d3;hp=08f0bb255de9b01306e9e18377ed0d1f257d73da;hpb=876124925eb2b43064a58dcc118e685ac876514c;p=ardour-manual diff --git a/_manual/19_synchronization/03_timecode-generators-and-slaves.html b/_manual/19_synchronization/03_timecode-generators-and-slaves.html index 08f0bb2..babca14 100644 --- a/_manual/19_synchronization/03_timecode-generators-and-slaves.html +++ b/_manual/19_synchronization/03_timecode-generators-and-slaves.html @@ -9,16 +9,16 @@ title: Timecode Generators and Slaves There are three common timecode formats:

As well as a JACK specific timecode implementation:

@@ -43,7 +43,7 @@ Note that some timecode formats are limited to a subset of Ardour's available fp

-The video-pullup modes change the effective samplerate of Ardour to allows for changing a film soundtrack from one frame rate to another. The scope is beyond this manual, but wikipedia's entry on Telecine may get you started. +The video-pullup modes change the effective samplerate of Ardour to allows for changing a film soundtrack from one frame rate to another. The concept is beyond the scope of this manual, but wikipedia's entry on Telecine may get you started.

Ardour Timecode Generator Configuration

@@ -62,7 +62,7 @@ The timecode is sent to jack-ports ardour:MTC out, ardour:MID

-Note that - at the time of writing this - only the LTC generator supports latency compensation. This is due to the fact the ardour MIDI ports are not yet latency compensated. +Note that - at the time of writing this - only the LTC generator supports latency compensation. This is due to the fact the Ardour MIDI ports are not yet latency compensated.

@@ -72,7 +72,7 @@ In session > properties it is possible to define an offset betwe

Both LTC and MTC are limited to max of 30fps. Using frame-rates larger than that will disable the generator. In both cases also only 24, 25, 29.97df and 30fps are well defined by specifications (such as SMPTE-12M, EU and the MIDI standard). -

+

MTC Generator

@@ -85,7 +85,7 @@ There are no options. Ardour sends full MTC frames whenever the transport is rel

LTC Generator

-The volume of the LTC signal can be conigured in in the Preferences > Transport dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system. +The volume of the LTC signal can be configured in in the Preferences > Transport dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system.

@@ -94,28 +94,26 @@ The LTC generator has an additional option to keep sending timecode even when th

LTC is send regardless of Ardour's transport-speed. It is accurately generated even for very slow speeds (<5%) and only limited by the soundcard's sampling-rate and filter (see Gibbs phenomenon) for high speeds. +

Ardour Slave Configuration

-Switching the timecode-source can be done via the button just right of Ardour's main clock. By default it is set to Internal in which case ardour will ignore any external timecode. The button allows to toggle between Internal and the configured timecode source which is chosen in Edit > Preferences > Transport. +Switching the timecode-source can be done via the button just right of Ardour's main clock. By default it is set to Internal in which case Ardour will ignore any external timecode. The button allows to toggle between Internal and the configured timecode source which is chosen in Edit > Preferences > Transport.

-When ardour is chasing an external timecode source the following cases need to be distinguished: +When Ardour is chasing an external timecode source the following cases need to be distinguished:

    -
  1. the timecode source shares the clock
    2. -
  2. the timecode source is independent (no wordclock sync)
    3. +
  3. the timecode source shares the clock
    4. +
  4. the timecode source is independent (no wordclock sync)
- -

-and -

+

and

    -
  1. the timecode source uses the same FPS setting as ardour
    2. -
  2. the timecode source runs at different frames-per-second
    3. +
  3. the timecode source uses the same FPS setting as Ardour
    4. +
  4. the timecode source runs at different frames-per-second

@@ -127,7 +125,7 @@ In both cases the first option is preferred: clock sync + same FPS setting.

Frames-per-second

-If the frames-per-second don't match, ardour can either re-calculate (map) the frames or the configured FPS (session > properties) can be changed automatically while the slave is active. The behavior is configured with the checkbox in Edit > Preferences > Transport labeled Match session video frame rate to external timecode: When enabled the session video frame rate will be changed to match that of the selected external timecode source. When disabled the session video frame rate will not be changed to match that of the selected external timecode source. Instead the frame rate indication in the main clock will flash red and Ardour will convert between the external timecode standard and the session standard. +If the frames-per-second don't match, Ardour can either re-calculate (map) the frames or the configured FPS (session > properties) can be changed automatically while the slave is active. The behavior is configured with the checkbox in Edit > Preferences > Transport labeled Match session video frame rate to external timecode: When enabled the session video frame rate will be changed to match that of the selected external timecode source. When disabled the session video frame rate will not be changed to match that of the selected external timecode source. Instead the frame rate indication in the main clock will flash red and Ardour will convert between the external timecode standard and the session standard.

@@ -151,11 +149,11 @@ The checkbox External timecode is sync locked allows to select the

-In other words: if enabled, ardour will only use perform initial synchronization and keep playing at speed 1.0 instead of vari-speed adjusting to compensate for drift. +In other words: if enabled, Ardour will only use perform initial synchronization and keep playing at speed 1.0 instead of vari-speed adjusting to compensate for drift.

-Note that vari-speed is unavailable when recording in ardour and all tracking happens at speed 1.0. So if you want to record in sync with external timecode it must be sample-locked or it will drift over time. +Note that vari-speed is unavailable when recording in Ardour and all tracking happens at speed 1.0. So if you want to record in sync with external timecode it must be sample-locked or it will drift over time.

@@ -199,7 +197,7 @@ While Ardour is chasing LTC, the main transport clock will display the received

-A global offset between incoming timecode and ardour's transport can be configured in Session > Properties. +A global offset between incoming timecode and Ardour's transport can be configured in Session > Properties.

@@ -235,6 +233,6 @@ JACK-transport does not support vari-speed, nor offsets. Ardour does not chase t

-JACK-transport also includes temp-based-time information ie. Bar:Beats:Ticks and beats-per-minute. However, only one JACK application can provide this information at a given time. The checkbox JACK Time Master in the Session > Properties dialog allows to configure ardour to act as translator from timecode to BBT information. +JACK-transport also includes temp-based-time information ie. Bar:Beats:Ticks and beats-per-minute. However, only one JACK application can provide this information at a given time. The checkbox JACK Time Master in the Session > Properties dialog allows to configure Ardour to act as translator from timecode to BBT information.