opcode studio 4 Manual Do Utilizador

aware that these routings can be 
active at the same time as routings 
established in the RCM window and, 
unless your careful, could cause 
unwanted MIDI thruing and extra 
sounds.

Experienced users will find many 
instances when it's convenient to use mul-
tiple routing methods, but novices may be 
overwhelmed if they try to use more than 
one method at a time. The important 
thing to remember is that sequencers, 
OMS patches and the RCM window all 
affect MIDI routing. You can use these 
various methods together, but you should 
plan your MIDI routing scheme carefully 
to avoid confusion.

You may wish to define a Routing, Chan-
nelizing and Muting window without any 
routings at all. You can save this window 
as a Studio 4 state and recall it whenever 
you work with sequencers or OMS 
patches that control MIDI routing. See 
“Establishing a Do Nothing State” in 
Chapter 8.

The timecode routing area is shown in 
Figure 7.20. This grid is very similar to 
the MIDI routing grid—you click one of 
the squares to route timecode (as gener-
ated by the Studio 4) to a MIDI device. 
The timecode’s MIDI format (MTC, DTL, 
or DTLe) is chosen in the Stripe SMPTE 
window (see Chapter 10). Timecode rout-
ing sends only MTC, DTL, or DTLe. It 
does not send MIDI Clock or Song Posi-
tion Pointer.

You usually use timecode routing to send 
MTC (or a DTL format) from the Studio 4 
to an external non-computer sequencer 
(such as a stand-alone hardware 
sequencer or a sequencer contained in a 
MIDI “workstation”).