Timecode Nodes

Timecode Converter

The Timecode Converter node takes a timecode and splits it into its components Hour, Minute, Second, Frame and Field. These values are provided as output properties. The current timecode in TotalSeconds is provided as well. It is also possible to add an Offset value to the incoming timecode. The resulting timecode is available via the output property TimecodeNew. If the incoming timecode is changing every frame, the TimecodeDirection property says if time is running forward or backward.

Timecode Event

The Timecode Event node provides the possibility to fire events on specific timecodes or cue points. These user-defined points in time can be added via the Custom Model dialog (click Edit Custom Model button in the Property Editor). Each of the user-defined timecodes gets a corresponding event which is fired if the specified timecode is reached. The Accuracy input property specifies how close the reference timecode (Timecode) must be to the user-defined points in time, to trigger the corresponding event. This is necessary if the reference timecode and the Ventuz configured timecode have different formats: e.g. 29.97 Drop Frame and 30.00. In this case the timecodes cannot be mapped exactly on each other.

Timecode OSC

The OSC Timecode node extracts the time-stamp of OSC messages and provides it in a Ventuz timecode format. The OSC specific input properties are described in the OSC Nodes section. The Timebase property specifies in which format the received OSC time-stamp is displayed:

Local Time	Timecode is based on the time of the local machine.
UTC	Timecode is based on the Coordinated Universal Time.
Zero	Timecode represents the zero-based number of seconds.

Timecode LTC

The LTC Timecode node receives Longitudinal Timecode which is encoded in audio data.
The property Ordinal specifies the device which should provide the audio data.

Timecode MIDI

The MIDI Timecode node receives timecode from a MIDI device.
The property DeviceID specifies the device which should provide the MIDI data.

Timecode Property and Formats

The above Timecode nodes have timecode input or properties of type VTimeCode. Binding input and output properties of this type is straightforward. But it's also possible to bind to or from other property types.
These are string, float, int, TimeSpan and DateTime. In case of the last two types following values are considered for a conversion: hours, minutes, seconds and milliseconds. float and int values are interpreted as seconds.
If binding to or from string values, conversion becomes a little bit more complicate. The result, if converting to string, depends on the setting in the Machine Configuration. If converting VTimeCode from string, a valid format is required to make the binding work. Valid strings representing a timecode must have one of the following formats:

• hh.mm.ss.xxxx
• hh.mm.ss
• mm.ss.xxxx
• mm.ss
• ss.xxxx
• ss
• .xxxx

Valid string values e.g. are:

• 01:02:03 (one hour, two minutes and tree seconds)
• 1:2:03 (one hour, two minutes and tree seconds)
• 03.400 (tree seconds and 400 milliseconds)
• 03.40 (tree seconds and 400 milliseconds)
• 03.4 (tree seconds and 400 milliseconds)

If entering values directly to the Property Editor you can also type in the timecode display format as configured in the Machine Configuration.

Copyright 2004-2014 Ventuz Technology Group