Mmc Control Of Record Functions; Routing Time Code To Other Devices; For Further Information - MOTU USB-MIDI User Manual

The first step is to slave your sequencer to MIDI
Time Code as described in the previous section
(and shown in Figure 4-3).
The next step is to establish MMC transport
control of the MOTU interface from your
sequencer. To do so, make sure your sequencer
knows the MMC Device ID of the MOTU
interface. The factory default ID of the MOTU
interface is 20. (If necessary, you can change it in
the console software.)

MMC CONTROL OF RECORD FUNCTIONS

Some sequencers provide MMC remote control of
record features, such as record-arming tracks,
setting automatic punch-in and punch-out points,
punching in on the fly, and so forth. The MOTU
interface's MMC capabilities, however, do not
come into play with record functions such as these.
It only handles MMC transport functions like
playing, stopping, and locating. For MMC record
functions, the MOTU interface serves only a means
S M P T E S Y N C A N D M M C W I T H A W I N D O W S S E Q U E N C E R
of passing on MMC record commands from your
sequencer and the MMC device. Just send them
directly to the appropriate Windows MIDI port.

ROUTING TIME CODE TO OTHER DEVICES

Once you have successfully established MMC
control of the MOTU interface from your
sequencer as described in this chapter, you can
route MIDI Time Code (MTC) from the MOTU
interface to other devices in your studio to control
them remotely from your sequencer, as shown in
Figure 4-4. For more information, see "Sync
routing" on page 63.

FOR FURTHER INFORMATION

For further details about using SMPTE sync and
MMC, see the appropriate chapter below:
chapter 6, "Using Micro Express Console"
I
(page 31)
chapter 7, "Using MIDI Express XT Console"
I
(page 51)
chapter 10, "Using MIDI Timepiece AV
I
Console" (page 83)
23