Reference Guide

1167
SMPTE/MIDI time code synchronization
Synchronizing your gear
Troubleshooting SMPTE/MTC sync
The most common problems with SMPTE/MTC Sync, and ways to correct or avoid them, are shown
in the following table.
No MTC sync within 1 minute of midnight roll-over
SONAR will not sync to MTC within one minute of roll-over (1 minute before midnight; 23:59:00:00 -
23:59:59:xx). To address this, use a SMPTE offset that doesn't require you to trigger the midnight
roll-over.
Problem What to do
The tape is striped incorrectly Check the tape stripe using your time code generator and, if
necessary, restripe the tape.
The MIDI interface isn’t producing MIDI
Time Code
Use utility programs that come with your MIDI interface to make
sure that the time code stripe is being received (sometimes you
must enable a Time Code Sync option). Check the MIDI
interface settings to make sure that MIDI Time Code is being
generated.
The frame rate is set incorrectly The frame rate on the stripe must match the frame rate you set in
SONAR.
The offset is set incorrectly The offset you enter in SONAR must match the start time of
recorded material on the tape.
SONAR is not configured correctly Verify and/or repeat the steps in “To configure SONAR to sync to
SMPTE/MTC” on page 1164.
Audio playback drifts out of sync with the
tape
Enable the Full Chase Lock option, which keeps audio from
freewheeling.
SONAR continues playing for up to one full
second after the time code stops
Some time code readers tolerate dropouts of up to one second,
without affecting playback. When you stop the tape deck, it takes
a full second for the reader to realize that this isn’t merely a
dropout and to signal the end of the time code to SONAR. This
does not indicate any problem with time code sync.
Table 210.