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=b83935e91ad87f9eccedc0946ade6a82b5a39b02;hpb=ae870f36cfaeb42c0c889a862db4e13749694728;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 b83935e..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:
@@ -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). -
+
-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,6 +94,7 @@ 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. +
-and -
+and