The setup problem

Some PC-based show-control systems and setups do not have the same physical LTC input hardware available as larger or more expensive console configurations.

What is actually happening

If the system can follow MIDI Timecode but does not have a convenient LTC input path, the workflow needs reliable LTC-to-MTC conversion and clear routing.

How DuckTC fits

DuckTC receives LTC from an audio interface, shows the waveform and sync state, converts to MTC, and routes the result through DuckPort MIDI.

The setup problem

Timecode failures often look mysterious because signal, frame rate, channel selection, MIDI routing, and software settings all fail in similar ways.

Quick checklist

• Confirm the show frame rate.
• Confirm the sending device is actually outputting code.
• Check the audio channel carrying LTC.
• Check level before blaming the console or app.
• Confirm the receiving system wants LTC or MTC.

When to use DuckTC tools

DuckTC Web can generate quick test code. DuckPort MIDI can simplify routing. DuckTC can convert incoming LTC to MTC while showing signal health.

The setup problem

One system may output LTC as audio while another system only accepts MTC through a MIDI input. That gap is common in PC-based lighting, laser, and show-control setups.

What is actually happening

LTC is an audio stream. MTC is MIDI Timecode. They can represent the same timeline, but they travel through different parts of the rig.

How to test it quickly

Start by confirming the timecode frame rate, then confirm whether the receiving software expects audio LTC or MIDI Timecode. The routing path determines the right tool.

When the rig needs a converter

DuckTC is designed for cases where LTC audio needs to become console-ready or app-ready MTC, routed through DuckPort MIDI.

The setup problem

In a show-control rig, several systems may need to follow the same clock: playback, lighting, lasers, video, and automation. LTC is one common way to send that clock as an audio signal.

What is actually happening

LTC stands for Linear Timecode. In practical terms, it is an audio waveform that encodes hours, minutes, seconds, and frames. A receiving device listens to that waveform and locks its timeline to the incoming code.

How to test it quickly

Use a known frame rate, route the signal to the correct audio channel, confirm level, and watch whether the receiving system locks cleanly. DuckTC Web is intended to make that first test fast.

When the rig needs more than a generator

If the device only accepts MIDI Timecode, or if you need to diagnose the actual LTC waveform, DuckTC is the professional next step.