Help

Short answers for getting TimeCode Play connected and running with your console.

Connection

For the full console workflow, use an external audio interface and an Ethernet connection to your console.

  1. Connect the audio interface you plan to use. Allow audio-input access for LTC monitoring, Local Network access for network protocols, and Photos or Camera access when using video.
  2. Connect Ethernet, check that the device and console can reach each other, then choose the network interface in Settings. TimeCode Play uses the interfaces and IPv4 addresses exposed by iOS/iPadOS.
  3. In Generator, choose Audio and tap File, or choose Video and open the preview menu to select a clip from Photos or record one.
  4. Configure the required timecode outputs in Settings. Match the frame rate on the receiving equipment, check your destinations, and test the connection before pressing Start.

Monitoring incoming timecode

Monitor shows incoming MTC, LTC and Art-Net TimeCode with signal status, timecode values and frame rate.

In Settings, enable MTC monitor input and choose a MIDI source. For Art-Net TimeCode, expand its Monitor card and tap Listen. For LTC, choose the connected audio input in Settings. The cards show timecode, frame rate and signal status; no usable signal is indicated separately.

Generating timecode

Generator sends MTC, LTC or Art-Net TimeCode while playing your reference material.

While stopped, tap the large time display to set start timecode and frame rate. Enable MIDI Time Code, Art-Net TimeCode or LTC in Settings and select the required interfaces, destinations and channels. The Pre 2 s button toggles pre-roll; Start, Pause and Reset control the generator.

Cues and media

Record a rehearsal or load an audio track, then add and edit cues for musical accents, movements and transitions.

Use Audio > File to select an audio track, or the Video preview menu to choose or record video. Add cue creates a point at the current timecode. Tap a cue to move the generator and media to it. Hold the time to edit it, hold the name to rename it, and swipe left to delete. Media follows the generator timeline; changing the start point does not alter the original file.

Control messages

Cue triggers can also send MIDI, OSC and Art-Net/DMX messages.

Tap a cue’s lightning button to configure MIDI, OSC or Art-Net/DMX messages. Check the selected destination, network interface and protocol settings, then use the test button before rehearsal. For Art-Net/DMX, enter the receiver’s IPv4 address and configure it to subscribe to the same universe. Jumping manually to a cue does not fire cue triggers.

Incoming OSC

Configured OSC controls can play, pause and move to the previous or next cue. Manual setup is required.

Open Settings > OSC remote, enable generator control, and note the UDP port. Send commands to this device’s IP address and that port. /tcplay/play, /tcplay/pause, /tcplay/reset, /tcplay/cue/previous and /tcplay/cue/next take no arguments. /tcplay/cue/go takes one positive Int32: the 1-based row in the active cue list. The listener has no sender authentication; enable it only on a trusted network.

Questions and answers

Do I need an audio interface?

The full console workflow requires an external audio interface and Ethernet. Available ports and channels depend on the connected equipment and the interfaces exposed by iOS/iPadOS.

Which system version do I need?

iOS 17 / iPadOS 17 or later.

Does media playback follow incoming timecode?

The media playback workflow follows the generator’s timecode. Monitor is used to inspect an external source.

Still stuck? Contact support.