In the case of 48kHz and 25fps, there are 1920 samples per video frame.
</p>
-<p>
-An interesting point to note is that LTC (Linear Time Code) is a Manchester Encoded, Frequency Modulated signal that carries both 'Clock' and 'Time'. It is possible to extract absolute position data and speed from it.
-</p>
-
<p>
The concept of clock and timecode is reflected in JACK and Ardour:
</p>
<p>
JACK provides clock-synchronization and is not concerned with time-code (this is not entirely true, more on jack-transport later).
Within software, jackd provides sample-accurate synchronization between all JACK applications.
-On the harware side JACK uses the clock of the audio-interface. Synchronization of multiple interfaces requires hardware support to sync the clocks.
+On the hardware side JACK uses the clock of the audio-interface. Synchronization of multiple interfaces requires hardware support to sync the clocks.
If two interfaces run at different clocks the only way to align the signals is via re-sampling (SRC - Sample Rate Conversion) - which decreases fidelity.
</p>
NB. to make things confusing, there are possibilities to synchronize clocks using timecode. e.g. using mechanism called <em>jam-sync</em> and a Phase-Locked-Loop.
</p>
+<p>
+An interesting point to note is that LTC (Linear Time Code) is a Manchester encoded, frequency modulated signal that carries both 'Clock' and 'Time'. It is possible to extract absolute position data and speed from it.
+</p>