Start with LTC (timecode) β
Applies to: the next version, not yet released (iPhone, iPad, Mac). Everything in this chapter is β.
Receive LTC (timecode) from a sound console or video playback device through your device's audio input, and start cues at the timecode you set. This is a Pro feature.
What you need
- A device that outputs LTC (playback device, sound console, etc.)
- A cable to your device's audio input (an audio interface, etc.)
- Pro
Audio is processed on the device only. It is not recorded or sent.
Turn on receiving
- In Settings, under "LTC input", turn on Receive
- The first time, you're asked for microphone access. Tap Allow
- Under Input, choose the device the LTC is connected to ("Default input" also works)
- Under Channel, choose the channel carrying the LTC (CH 1, CH 2...)
- Play the LTC and check the following
- Level: adjust Gain so the level sits in the green band (−24 to −6 dBFS)
- The timecode runs and "Receiving" appears. The frame rate (24 / 25 / 29.97DF / 30) is detected automatically
| Status | Meaning |
|---|---|
| Receiving | LTC is being read |
| No signal | No LTC is coming in. Check the cable, input, and channel |
- The app receives only while it's in front. Keep the screen up during the show
- Only one device can receive. If you turn on receiving on another device on the same account, it turns off on this one automatically
- Input, channel, and gain are set per device (they don't sync)
Start a cue with LTC
- In the editor, open the cue and choose LTC under Trigger
- Enter the Start timecode (hours:minutes:seconds:frames) and save
If AUTO is on in the run screen, the cue starts when the LTC passes its start timecode. While receiving, a clock mark and the frame rate appear at the top of the run screen.
Start rules
- Cues start only when AUTO is on
- Only LTC cues after the current cue are eligible. Rewinding the LTC doesn't affect the current cue or earlier cues
- A cue starts if LTC is read within 10 seconds after its start timecode
- If several cues match at once, the last one starts and the earlier ones are skipped
- Elapsed time is counted from the LTC (from the moment the start timecode was passed)
- This works only on the receiving device. Share clients follow the host's run
LTC OFFSET (delay correction)
If LTC arrives late, correct it in frames with LTC OFFSET: in the sheet list, tap the sheet's → "Sheet settings" (−30 to +30, default 0). A positive value syncs that many frames earlier.
Writing it in CSV
Put ltc in the trigger column and the start timecode in the start column as HH:MM:SS:FF.
Older versions and Android
On older versions of the app and on Android, LTC cues are treated as "Manual" cues and wait until you press NEXT. Android can't receive LTC.
Troubleshooting
| Problem | Solution |
|---|---|
| Stuck on "No signal" | Check the input device and channel. Raise the gain until the level reaches the green band |
| "Microphone access is off. Allow it in Settings." | In your device's Settings app, allow microphone access for SBL Cue Timer |
| Receiving turned off by itself | Receiving was turned on on another device on the same account. Pick one device to receive |
| The cue doesn't start | Check that AUTO is on, that the cue is after the current cue, and that LTC arrives within 10 seconds after the start timecode |
| It drifts a little late | Set LTC OFFSET to a positive value |