Timecode

Timecode is how CuePoints and everything else in the building agree on what time it is. One machine says what time it is; the others follow. This page covers where CuePoints gets its timecode, how it sends it out, and how it follows someone else's.

Striped Or Generated

There are two ways a track can have timecode.

Striped: the timecode is already recorded onto the media, as a sound on an audio channel. This is LTC. When you import a file you're asked whether it's striped; if it is, CuePoints reads the timecode off the media itself.

Generated: the media has no timecode, so CuePoints makes it. It counts from the track's offset, at the track's framerate. This is what most people use.

If a track is striped but you'd rather CuePoints made its own, turn on Enable LTC Generator in the track settings. Enable LTC Generator for All Tracks does the same across the whole project.

Change a track's offset, framerate or pre-roll and the generated timecode is rebuilt immediately.

Getting Timecode Out

Three ways, and they can run at once.

As audio (LTC). LTC goes out of an audio socket, so you route it like any other sound. On the Audio Output pane, set the channel you want it on to LTC. This is why people run a multi-channel interface: a four-channel box gets you a stereo mix for in-ears or speakers and two separate LTC feeds. And because routing is per-channel, two people can set the same show up differently: the designer sends only track audio to their headphones, while the programmer sends LTC down channels 3 and 4 to the desk.

As MIDI (MTC). CuePoints sends MIDI timecode directly; no extra software. Set Protocol to MIDI Timecode under Settings and pick the MIDI output device.

Over the network (Art-Net). Set Protocol to Artnet Timecode, then choose the interface to send from, the destination address, and the stream number. The receiving machine has to be listening for the same stream.

Taking Timecode In

If something else is the clock, CuePoints follows it. Under Settings, set Source to LTC Audio Input, MIDI Timecode or Artnet Timecode, and pick the device or stream.

In and out can both be active at once, so CuePoints can follow one machine and pass the clock on to another.

Whatever you're following, your track's framerate has to match the sender's. If it doesn't, the numbers will be wrong even though everything looks connected. The default for new tracks is on the Tracks & Media pane.

Settings

CuePoints > Settings… > Timecode

Two halves, TIMECODE IN and TIMECODE OUT. Each has one source, and the rows underneath change to match whatever you pick.

Timecode In

Source picks what CuePoints listens to:

• Disabled: CuePoints runs on its own clock. The normal setting when nothing else is driving your show.

• LTC Audio Input: timecode arriving as a sound, down an audio cable. The most common way on a live show.

• MIDI Timecode: arriving over MIDI.

• Artnet Timecode: arriving over the network, the way lighting rigs send it.

LTC in

• Audio input device: the interface the cable is plugged into.

• Audio channel: which socket on that interface (Ch 1, Ch 2, and so on). Count the sockets on the back before you guess.

MIDI in

• MIDI input device: the MIDI port the timecode arrives on.

If the sending app is on the same computer, you'll see a note: you must create an IAC Bus in order to share MIDI internally. An IAC Bus is a virtual MIDI cable between apps on the same Mac. Create one in Applications > Utilities > Audio MIDI Setup, under Window > Show MIDI Studio, then double-click IAC Driver and tick Device is online. It then shows up in this list.

Art-Net in

• Art-Net stream: which stream to follow. Leave it empty to accept any stream; start there. Type a number 0–255 to follow only that one, when several things on the network are sending timecode and you must lock to one of them.

Timecode Out

Protocol picks how CuePoints sends its clock out:

• Disabled: CuePoints doesn't send timecode.

• MIDI Timecode: sent over MIDI.

• Artnet Timecode: sent over the network.

MIDI out

• MIDI output device: the MIDI port to send down. The IAC Bus note above applies if the receiving app is on this computer.

Art-Net out

• ArtNet TC Network Interface: which network card to send from. This is about your computer, not the far end. On Wi-Fi and a wired show network at once, pick the wired one.

• Destination IP: where it goes. Localhost (127.0.0.1) means another app on this same computer. Otherwise, the address of the machine that needs it.

• Stream: the stream number to send as. The receiving machine has to be listening for the same number.

Sending LTC

LTC out lives on the Audio Output pane, not here. LTC out is a sound, so it comes out of an audio socket like anything else. Find the channel you want it on and set that channel to LTC.

When It Isn't Working

Nothing is arriving. Check Source isn't Disabled; it's the first thing to go wrong and the easiest to miss. Then check the device and channel.

Numbers arrive but they're wrong. That's frame rate. The sender and CuePoints have to count at the same rate. See the default under Tracks & Media.

MIDI device isn't listed. If it's another app on the same computer, you need the IAC Bus. If it's real hardware, unplug and replug it, then reopen Settings.

Art-Net arrives but nothing moves. You're locked to the wrong stream number. Clear the Art-Net stream box to accept anything, and see if it starts.