# Route-On, # Route-Off


If you use Route-For, your switcher event will be for a specified length of time, and will be visual as an audio event in the currently-playing area of Command Center. However there are times when you may prefer the switcher event to be semi-permanent" and just happen in the background without appearing on your screen. To do that, use # Route On/Off.

There are many good uses for this feature. An example is in routing audio for use with our TimeTracker background recording software. Assuming you have reserved stereo channel #1 for your main output, you might like to wire stereo output channel #2 so that it feeds the line-in of your TuneTracker computer. Then, by using Route-On and Route-Off, you can decide which of a variety of audio feeds you would like to send to the TuneTracker computer, depending on the time of day, and day of the week.

The parameters used for this command are very simple...

•   Examples:
  
  # Route-On Input 2 to Output 1
  # Route-Off Input 2 to Output 1
  

In the first example above, switcher input channel two will be opened and sent to output channel one. It will stay that way "permanently" or until you use a # Route-Off later in your log, to turn it off, as shown in the second example.

You can place Route-On and Route-Off commands wherever you like in your program log. Bear in mind that any audio channel routing you activate using Route-On will remain active until you switch it back off using a Route-Off command.

NOTE:  Be careful to avoid the possibility of sending two audio inputs to the same ouput, which is certainly possible using Route-On. Always assure you have scheduled a Route-Off for the first route to the output, before using Route-On to create a different one.

NOTE:  When placing Route-On and Route-Off events in your master logs, it is wise to position them just after an event you are certain will play. Avoid putting them just before time-corrects, which could cause them to be skipped-over and missed.




Table of Contents