X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F19_synchronization%2F04_overview-of-timecode-related-settings.html;h=623cbf07f71c4d5b002e9d54cd921a4d11046775;hb=27ff2f09a183a7cd1d105bdd73a91d0e29e0b766;hp=c9e486a0ef955e9d180aaa394ccfda463abddff1;hpb=7a02ccdce1f9599b9ea5b1a08f53f913474eec25;p=ardour-manual-diverged

diff --git a/_manual/19_synchronization/04_overview-of-timecode-related-settings.html b/_manual/19_synchronization/04_overview-of-timecode-related-settings.html
index c9e486a..623cbf0 100644
--- a/_manual/19_synchronization/04_overview-of-timecode-related-settings.html
+++ b/_manual/19_synchronization/04_overview-of-timecode-related-settings.html
@@ -34,8 +34,12 @@ Timecode related settings are accessed from the menu:
 <ul>
 <li><strong>External timecode source</strong> – select timecode source: JACK, LTC, MTC, MClk</li>
 <li><strong>Match session video frame rate to external timecode</strong> – This option controls the value of the video frame rate <em>while chasing</em> an external timecode source. <strong>When enabled</strong> the session video frame rate will be changed to match that of the selected external timecode source. <strong>When disabled</strong> 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.</li>
-<li><strong>External timecode is sync locked</strong> – <strong>When enabled</strong> indicates that the selected external timecode source shares sync (Black &amp;amp; Burst, Wordclock, etc) with the audio interface.</li>
+<li><strong>External timecode is sync locked</strong> – <strong>When enabled</strong> indicates that the selected external timecode source shares sync (Black &amp; Burst, Wordclock, etc) with the audio interface.</li>
 <li><strong>Lock to 29.9700 fps instead of 30000/1001</strong> – <strong>When enabled</strong> the external timecode source is assumed to use 29.97 fps instead of 30000/1001. SMPTE 12M-1999 specifies 29.97df as 30000/1001. The <acronym title="specification">spec</acronym> further mentions that drop-frame timecode has an accumulated error of -86ms 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 not the actual rate. However, some vendors use that rate - despite it being against the specs - because the variant of using exactly 29.97 fps has zero timecode drift.</li>
+<li><strong>LTC incoming port</strong> – offers a session agnostic way to retain the LTC port connection.</li>
+<li><strong>Enable LTC generator</strong> – does just what it says.</li>
+<li><strong>Send LTC while stopped</strong> – <b>When enabled</b> Ardour will continue to send LTC information even when the transport (playhead) is not moving. This mode is intended to drive analog tape machines which unspool the tape if no LTC timecode is received.</li>
+<li><strong>LTC generator level</strong> – Specify the Peak Volume of the generated LTC signal in dbFS. A good value is  0dBu ^= -18dbFS in an EBU calibrated system</li>
 </ul>