User Tools

Site Tools


external:smpte_timecode

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
external:smpte_timecode [2019/12/26 11:54] – [Table] icke_siegenexternal:smpte_timecode [2020/03/17 03:12] (current) – external edit 127.0.0.1
Line 3: Line 3:
 Whenever more than one device - software, hardware, computer etc. - are used simultaneously to create one final thing - e.g. a movie with music, or a lightshow running in sync to music or to a video - then a way to synchronize all devices is required. SMPTE Timecode is something like the standard for such a task: the timecode master sends a continuous stream of data which permanently states the time the master has advanced into the show/track/clip. And all other devices - here: timecode slaves - are to react to the very time as programmed in each device. Whenever more than one device - software, hardware, computer etc. - are used simultaneously to create one final thing - e.g. a movie with music, or a lightshow running in sync to music or to a video - then a way to synchronize all devices is required. SMPTE Timecode is something like the standard for such a task: the timecode master sends a continuous stream of data which permanently states the time the master has advanced into the show/track/clip. And all other devices - here: timecode slaves - are to react to the very time as programmed in each device.
  
-^ More info on Linear Timecode  | https://en.wikipedia.org/wiki/Linear_timecode  +^ More info on Linear Timecode  | https://en.wikipedia.org/wiki/Linear_timecode      
-^ More info om SMPTE Timecode   | https://en.wikipedia.org/wiki/SMPTE_timecode   +^ More info on SMPTE Timecode   | https://en.wikipedia.org/wiki/SMPTE_timecode       
-^ Signal                        | digital audio signal, 80 bit per frame         +^ Signal                        | digital audio signal, 80 bit per frame             
-^ Framerate                     | 24, **25**, 29.97, 30 fps                      +^ Framerate                     | 24, **25**, 29.97, 30 fps                          
-^ Connector/Cables              | usually 3 pin XLR.                             |+^ Connector/Cables              | usually 3 pin XLR. Other connectors are possible. 
 +^ Value range                   | from 00:00:00.00 to 23:59:59:23 (frames as per framerate) |
  
 From https://en.wikipedia.org/wiki/Linear_timecode#Generation_and_Distribution: From https://en.wikipedia.org/wiki/Linear_timecode#Generation_and_Distribution:
Line 24: Line 25:
 >  * To create negative time code add one hour to time (avoid midnight effect) >  * To create negative time code add one hour to time (avoid midnight effect)
 >  * Always put slowest device as a master >  * Always put slowest device as a master
 +
 +===== Practical Handling =====
 +
 +Usually the timecode signal comes as extra audio signal. It is not uncommon to record it as extra track on a multitrack system. For rehearsing/preprogramming your lights you can even have the producers mix all audio together e.g. on the left audio track, and have timecode on audio right channel. If you remember how a fax machine or a computer modem sounds: this is how SMPTE timecode sounds as well.
 +
 +The signal needs to be sent to all devices which need to be synced. In a very basic environment feed the timecode from your video playback or digital audio workstation into your lighting console.
 +
 +For testing purposes you can even find audio files with timecode online or generate it, e.g. at http://elteesee.pehrhovey.net/.
 +
 +===== Titan Consoles and timecode =====
 +
 +Not every Titan console has the hardware to handle SMPTE timecode:
 +  * the Titan One and the T1 do **NOT** support timecode input
 +  * the T2 does support timecode, and can be used as timecode input for other consoles
 +  * the Titan Mobile, Quartz, Tiger Touch, Tiger Touch Pro, Pearl Expert and Pear Expert Pro do **not** support timecode input but 
 +    * if running Titan v12 or above: can be extended with a T2 in order to be used as timecode input
 +    * do understand MIDI timecode so that you can use an external converter box to convert LTC to MTC, see below ([[external:smpte_timecode#Converters]])
 +  * Tiger Touch 2 and Sapphire Touch both have a designated LTC (SMPTE) input
 +
 +===== Converters =====
 +
 +There are some converters on the market which can translate between SMPTE timecode and MIDI timecode. They have different feature sets - some can convert from everything to everything, some can generate timecode themselfes, some converte to/from USB MIDI as well etc. Just some examples:
 +
 +  * the [[https://rosendahl-studiotechnik.com/mif4.html|Rosendahl Mif-4]] is the gold standard for timecode converters in the AV industry
 +  * various [[https://motu.com/products/body.html?productslider=4|MOTU interfaces]], e.g. the [[https://motu.com/products/midi/micro_usb|MOTU micro express]] ((a few yeears ago there was a firmware issue in some MOTU interfaces, resulting in 1 second jumps in special situations, depending from frame rate and start time. Don't know if this has been resolved - we made MOTU aware of this.))
 +  * the [[https://kiss-box.nl/product-archive/tc2tr-ltc-mtcmidi-tranceiver/|Kissbox TC2TR]]
 +
 +This list will never be complete. I believe I used a Fostex or Roland interface many years ago but I don't know for sure - this market is in constant movement.
external/smpte_timecode.1577361240.txt.gz · Last modified: 2019/12/26 11:54 by icke_siegen

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki