User`s guide
INSTALLING THE TRAVELER HARDWARE
32
SYNCING TO SMPTE TIME CODE
The Traveler system can resolve directly to SMPTE
time code. It can also generate time code and word
clock, under its own clock or while slaving to time
code. Therefore, the Traveler can act both as an
audio interface and digital audio synchronizer, to
which you can slave other digital audio devices.
Yo u c a n u s e the Traveler to slave your audio
software to SMPTE as well, as long as your software
supports sample-accurate sync, which is the means
by which the software follows the Traveler. The
accuracy may not be sample-accurate, but in most
cases it will be very close.
Other digital audio device
slaved to the Traveler
Figure 4-15: Connections for synchronizing
the Traveler directly to SMPTE time code.
Choose SMPTE as the clock source in the
MOTU FireWire Audio Console. This
setting can also be made in the
FireWire SMPTE Console (shown
below).
Trav el er interface
SMPTE time code
source
audio cable bearing LTC
(Longitudinal Time Code)
FireWire cable
Launch the FireWire SMPTE Console and specify the SMPTE Source, which
is the input receiving the SMPTE time code. Also, confirm that the Clock
Source/Address is SMPTE/SMPTE. For details about the other settings, see
chapter 11, “FireWire SMPTE Console” (page 79).
video
cable
audio
cable
Analog
out
Word
Out
When lockup is achieved,
the LOCK light illuminates
and the TACH light blinks
once per second.
Windows computer running Cubase or
other sample-accurate ASIO software
In Cubase SX, go to the Sync Setup window and
choose the ASIO Audio Device option.
Any analog input
Use this setup if you have:
✓ A SMPTE time code source, such as a multitrack tape deck.
✓
A Traveler by itself, OR with another slaved device (such as a
digital mixer).
✓ Host software that supports sample-accurate sync.
This setup provides:
✗
No sample-accurate locating.
✓ Continuous sync to SMPTE time code.
✓ Sub-frame timing accuracy.
✓ Transport control from the SMPTE time code source.
!Traveler Manual/Win Page 32 Monday, November 29, 2004 3:50 PM