Linear timecode

Linear (or Longitudinal) Timecode (LTC) is an encoding of SMPTE timecode data in an audio signal, as defined in SMPTE 12M specification. The audio signal is commonly recorded on a VTR track or other storage media. The bits are encoded using the biphase mark code (also known as FM): a 0 bit has a single transition at the start of the bit period. A 1 bit has two transitions, at the beginning and middle of the period. This encoding is self-clocking. Each frame is terminated by a 'sync word' which has a special predefined sync relationship with any video or film content.

A special bit in the linear timecode frame, the biphase mark correction bit, ensures that there are an even number of AC transitions in each timecode frame.

The sound of linear timecode is a jarring and distinctive noise and has been used as a sound-effects shorthand to imply telemetry or computers.

As of 2019-01-21, this recommendation was withdrawn by ITU-R <ref name=BR.780-2>Recommendation ITU-R BR.780-2: Time and control code standards, for production applications in order to facilitate the international exchange of television programmes on magnetic tapes. ITU. 2005-04-08 [1992, 2002, 2005].</ref>

Generation and Distribution

In broadcast video situations, the LTC generator should be tied into house black burst, as should all devices using timecode, to ensure correct color framing and correct synchronization of all digital clocks. When synchronizing multiple clock-dependent digital devices together with video, such as digital audio recorders, the devices must be connected to a common word clock signal that is derived from the house black burst signal. This can be accomplished by using a generator that generates both black burst and video-resolved word clock, or by synchronizing the master digital device to video, and synchronizing all subsequent devices to the word clock output of the master digital device (and to LTC).

Made up of 80 bits per frame, where there may be 24, 25 or 30 frames per second, LTC timecode varies from 960 Hz (binary zeros at 24 frames/s) to 2400 Hz (binary ones at 30 frames/s), and thus is comfortably in the audio frequency range. LTC can exist as either a balanced or unbalanced signal, and can be treated as an audio signal in regards to distribution. Like audio, LTC can be distributed by standard audio wiring, connectors, distribution amplifiers, and patchbays, and can be ground-isolated with audio transformers. It can also be distributed via 75 ohm video cable and video distribution amplifiers, although the voltage attenuation caused by using a 75 ohm system may cause the signal to drop to a level that can not be read by some equipment.

Care has to be taken with analog audio to avoid audible 'breakthrough' (aka "crosstalk") from the LTC track to the audio tracks.

LTC care:

• Avoid percussive sounds close to LTC
• Never process an LTC with noise reduction, eq or compressor
• Allow pre roll and post roll
• To create negative time code add one hour to time (avoid midnight effect)
• Always put slowest device as a master

Longitudinal SMPTE timecode should be played back at a middle-level when recorded on an audio track, as both low and high levels will introduce distortion.

Longitudinal timecode data format

Linear timecode waveform as displayed in Audacity with 80 bit data frame highlighted

The basic format is an 80-bit code that gives the time of day to the second, and the frame number within the second. Values are stored in binary-coded decimal, least significant bit first. There are thirty-two bits of user data, usually used for a reel number and date.

SMPTE linear timecode<ref name="BR.780-2" group=""></ref>

Bit	Weight	Meaning		Bit	Weight	Meaning		Bit	Weight	Meaning		Bit	Weight	Meaning		Bit	Value	Meaning
00	1	Frame number units (0–9)		16	1	Seconds units (0–9)		32	1	Minutes units (0–9)		48	1	Hours units (0–9)		64	0	Sync word, fixed bit pattern 0011 1111 1111 1101
01	2			17	2			33	2			49	2			65	0
02	4			18	4			34	4			50	4			66	1
03	8			19	8			35	8			51	8			67	1
04	User bits field 1			20	User bits field 3			36	User bits field 5			52	User bits field 7			68	1
05				21				37				53				69	1
06				22				38				54				70	1
07				23				39				55				71	1
08	10	Frame number tens (0-2)		24	10	Seconds tens (0–5)		40	10	Minutes tens (0–5)		56	10	Hours tens (0-2)		72	1
09	20			25	20			41	20			57	20			73	1
10	D	Drop frame flag.		26	40			42	40			58	BGF1	Clock flag		74	1
11	C	"Color frame" flag		27	(flag, see below)			43	(flag, see below)			59	(flag, see below)			75	1
12	User bits field 2			28	User bits field 4			44	User bits field 6			60	User bits field 8			76	1
13				29				45				61				77	1
14				30				46				62				78	0
15				31				47				63				79	1

• Bit 10 is set to 1 if drop frame numbering is in use; frame numbers 0 and 1 are skipped during the first second of every minute, except multiples of 10 minutes. This converts 30 frame/second time code to the 29.97 frame/second NTSC standard.
• Bit 11, the color framing bit, is set to 1 if the time code is synchronized to a color video signal. The frame number modulo 2 (for NTSC and SECAM) or modulo 4 (for PAL) should be preserved across cuts in order to avoid phase jumps in the chrominance subcarrier.
• Bits 27, 43, and 59 differ between 25 frame/s time code, and other frame rates (30, 29.97, or 24).<ref name="BR.780-2" group=""></ref><ref>Indian Standard IS: 12429 (Part 1) Time and Control Code for Video Tape Recorders: Part 1 Longitudinal Time Code (LTC) (PDF). Bureau of Indian Standards. 2002 [1988]. pp. 1–3. This is an example of the 25 frame/s bit assignments, which are different from the more commonly seen 30/29.97/24 bit assignments.</ref> The bits are:
  • "Polarity correction bit" (bit 59 at 25 frame/s, bit 27 at other rates): this bit is chosen to provide an even number of 0 bits in the whole frame, including the sync code. (Since the frame is an even number of bits long, this implies an even number of 1 bits, and is thus an even parity bit. Since the sync code includes an odd number of 1 bits, it is an odd parity bit over the data.) This keeps the phase of each frame consistent, so it always starts with a rising edge at the beginning of bit 0. This allows seamless splicing of different time codes, and lets it be more easily read with an oscilloscope.
  • "Binary group flag" bits BGF0 and BGF2 (bits 27 and 43 at 25 frame/s, bits 43 and 59 at other rates): these indicate the format of the user bits. Both 0 indicates no (or unspecified) format. Only BGF0 set indicates four 8-bit characters (transmitted little-endian). The combinations with BGF2 set are reserved.<ref name="BR.780-2" group=""></ref>
• Bit 58, unused in earlier versions of the specification, is now defined as "binary group flag 1" and indicates that the time code is synchronized to an external clock.<ref name="BR.780-2" group=""></ref> if zero, the time origin is arbitrary.
• The sync pattern in bits 64 through 79 includes 12 consecutive 1 bits, which cannot appear anywhere else in the time code. Assuming all user bits are set to 1, the longest run of 1 bits that can appear elsewhere in the time code is 10, bits 9 to 18 inclusive.
• The sync pattern is preceded by 00 and followed by 01. This is used to determine whether an audio tape is running forward or backward.<ref>"SMPTR Made Simple" (PDF). TimeLine Vista, Inc. 1996. p. 11. The time code reader uses the direction sense bits to determine whether the tape is running forward or backward.</ref><ref>Rees, Phil (15 November 2013). "Synchronisation and SMPTE timecode (time code)". Retrieved 2016-12-25.</ref>

See also

• AES-EBU embedded timecode
• Burnt-in timecode
• Control track longitudinal timecode
• MIDI timecode
• Manchester code, Differential Manchester encoding
• Rewritable consumer timecode
• Vertical interval timecode

External links

• LGPL library to en/decode LTC in software