Troubleshooting

If LTC Magic does not produce the result you expected, start with the basics.

Check that the correct files were selected, the LTC channel is present, and the frame rate is correct. Many timing problems come from a mismatched frame rate or selecting the wrong channel as the LTC source.

If LTC cannot be decoded, listen to or inspect the suspected LTC channel. The signal may be missing, too quiet, clipped, interrupted or recorded on a different channel.

If an FCPXML imports with offline media, check whether the media paths changed after the build. Keep the FCPXML and media folder together when moving between systems.

If AAF audio is consistently early or late against the Stereo mix WAV, review AAF alignment in Inputs. Automatic audio match can find one offset from shared audio; if it cannot confirm a reliable match, use a verified Manual offset. The summary is available during the scan and stays visible through Mapping, Validate and Report. See alignment troubleshooting.

If Burnt-in Timecode reads the wrong number, redraw the box around the digits and check Frame rate before scanning. See If the readout is wrong.

If grouped WAVs appear incorrectly, review filenames, metadata and folder structure. Inconsistent naming can make related files harder to identify automatically.

When contacting support, include the app version, operating system, frame rate, source file type, a screenshot or copy of the warning, and a small sample file if possible.