TUNETRACKER SYSTEM IN ACTION - TuneTracker



   
TUNETRACKER COMMANDS
"JUMP LIST"


Find any command quickly.
Commonly-Used Commands

Comment
Hour
Live
Interrupt
Pause-For
Pause-Until
Time-Correct
TempAnnounce
TimeAnnounce



Special-Use Commands

FadeInto
GetFile
GetPlay
LiveAssist
Overlay
Chime
Relay-For
Run
DoBackups
ShowText
SS (Silence Sense)
TalkBed (see # VT feature)
TriggerPlay
UseButtonPadSet
UseMyShowSet
VT (Voicetrack)



Switcher-Related Commands

Note: The single "Switcher" command can be often used in place of Route-For, Listen, HotTrack, and Ignore, so see that one first!

Switcher
Ignore
Listen
HotTrack
Route-For
Route-On/Off
SendRelay
SendTone
TimedTone
ClearSwitcher


TuneTracker™ Commands

Simple automation commands, included in your format clocks, are used to tell the TuneTracker™ automation program what to do, and when to do it. All TuneTracker™ commands must begin with a single # (pound sign). TuneTracker™ commands are "case insensitive," though when they specify a path and a filename, you must use the same upper and lowercase letters as actually exist in the path and filename.

The quickest way to access information about any TuneTracker command is to click on the item in our "Jumplist" on the right. You will note that some commands are only available with certain versions of TuneTracker, and those exceptions are noted in each command's description.

Where offered, be sure to click "Read More" for more detailed information on commands, including lots of really helpful hints and examples. If you don't read them, you'll miss a lot of what these features can do for you!

For full, in-context examples of these commands "in action," be sure to view the format clock and master log template files and the sample program log, found in your TuneTracker System's "Templates" folder, or in the "Logs" folders found inside your "Station" folder.

Some of our timed automation commands let you get much more specific than the traditional hours, minutes, and seconds. Watch for features below that offer "milliseconds-level" accuracy, allowing you to add precision down to the thousandth-of-a-second by including one, two, or three decimal places, for use in hyper-critical timing situations.




# Hour (required)

# Hour is a marker that must be included at the top of each hour in your program day, including at the start of each of your
format clocks and at the start of every hour in your 24-hour master logs. The # Hour statement tells TuneTracker™ that all the entries following it should occur in the hour specified. The # Hour command is expressed in 24-hour "military" time format, where hour 13 is 1 p.m., hour 14 is 2 p.m., etc. The first hour of the day, from midnight to 1 a.m., is expressed as "# Hour 0".


    Examples:

    # Hour 0 (midnight hour)
    # Hour 8 (8 a.m.)
    # Hour 12 (noon)
    # Hour 15 (3 p.m.)






# Time-Correct (strongly recommended)

A Time-Correct is an industry standard radio automation function which is used to help keep your programming running on-schedule. At least once each half hour, a Time-Correct should be included in your
format clock. The Time-Correct command tells TuneTracker™ to skip any unneeded events at the time specified.


    Examples:

    # Time-Correct@:19:00
    # Time-Correct@:59:45

Read More about using this feature.






# Pause-For

The "# Pause-For" command tells TuneTracker™ to cease further operations for a specified period of time. This command can be used in tandem with other commands in a number of ways.


    Examples:

    # Pause-For 01:00:00 (pause for one hour)
    # Pause-For 00:01:00 (pause for one minute)
    # Pause-For 00:00:15 (pause for 15 seconds)
    # Pause-For 00:00:15.2 (pause for 15.2 seconds)
    # Pause-For 00:00:15.28 (pause for 15.28 seconds)
    # Pause-For 00:00:15.284 (pause for 15.284 seconds)
    # Pause-For 99:00:00 (infinite pause)

Read More about using this feature.






# Pause-Until

Unlike # Pause-For, which pauses for a prescribed period of time, # Pause-Until causes Command Center to pause until a specified time.

    Examples:

    # Pause-Until 09:30:15
    # Pause-Until Noon (both "Noon" and "Midnight" are terms that can be used)
    # Pause-Until 21:17.8 (you can add a decimal for tenth-of-a-second accuracy) # Pause-Until 21:17.87 (you can add two decimals for hundreths-of-a-second accuracy) # Pause-Until 21:17.872 (you can add a decimal for thousandths-of-a-second accuracy)

Note that the log should be BLANK between the Pause-Until event and the point in the log where the Command Center is supposed to resume.

An overnight pause should look like this:

    Example:

    /boot/Station/Announcements/Signoff.mp3
    # Pause-Until Midnight

    (next day's program log
    # Hour 0
    # Pause-Until 06:00:00
    # Hour 6
    /boot/Station/Announcements/Signon.mp3

Read More about using this feature.






# Interrupt

The "# interrupt" command is a powerful command which is extremely useful in joining (or breaking away from) programming at a specific time. A single "# interrupt" command fades the currently playing audio event for a specified length of time, then takes it off the air and starts the next event at an exact time.

IMPORTANT: Note in the examples below that there is a : (colon) just after the @ sign. Note also that the time shown after the colon is expressed in minutes and seconds. Do not express the hour here, just a colon, followed by minutes and seconds.



  •   Example:

    /boot/path/song.mp3
    # interrupt@:30:00 10
    /boot/path/news.wav

Read More about using this feature.






ALERT!

There are TWO different versions of the following command. One is for use in TuneTracker Basic™ (and the old TT Pro program). The other is for use in Command Center™. Be certain to use the correct syntax for the version of TuneTracker you have, or your automated live events will not behave properly!




# Live On and # Live Off (TuneTracker Basic ONLY)

The "# Live" command is an automated method of opening a live connection to whatever is audio source is plugged into your sound card. There are two possible parameters: "live on" and "live off."


  •   Examples:

    # Live on
    # Pause-For 00:05:00
    # Live off

The # Live automation event is NOT intended for frequent, day-in, day-out satellite automation. Use a Command Center
ChannelCaster-equipped system with switcher package for that sort of broadcast operation.


# Live-For (Command Center ONLY)

The "# Live-For" command is an automated method of opening a live connection to whatever is audio source is plugged into your sound card. In Command Center, you specify the period of time for the live event right in the same line, so no Pause-For line is necessary.


  •   Example 1:

    # Live-For 00:05:00



  •   Example 2:

    # Live-For 99:00:00
    # Interrupt@:18:00

In the second example, Live-For uses an "infinite pause" which will keep your live event active until it is taken off the air by an # Interrupt.

IMPORTANT NOTE:  The # Live-For and # Live On/Off automation events are NOT intended for frequent, day-in, day-out, satellite-based automation. For that kind of broadcasting, use Command Center and a ChannelCaster switcher package.

Read More about using this feature.






## Comment Lines

Any line which begins with ## (two pound signs) is considered a "comment line" in the TuneTracker System™. It is disregarded by TuneStacker™ and automatically passed on to the program log TuneStacker™ generates. That allows you to add notes of clarification and blank lines for spacing, to keep your log easier to read.



    Examples:

    ## (blank line)
    ## Noon News Segment
    ## Remove item below on January 1st
    ## /boot/path/sports/fishingreport.wav

Read More about using this feature.






# FadeInto

FadeInto does just what you'd think. It lets you start a live event or a digital audio cut at zero volume and fade it up. It's especially useful when you need to join live audio "in progress" and don't want the transition to sound chopped and abrupt. The number following your # fadeinto indicates how many seconds the fade-in should last. As little as one-second of fade-in can sound good. The example below shows a long, five-second fadein.



    Examples:

    # FadeInto 5
    # Live-For 00:15:00

Read More about using this feature.






# SS On / # SS Off

It is possible to automatically turn the silence sensor on and off via your program log. This is done extremely easily, and is handy for situations where you are joining a live audio event that can have unpredictable amounts of silence such as a concert, church service, lecture, etc, or when you plan to use the "# Pause-For" event to pause the automation silently for a period of time, such as overnight.

The silence sensor is "immune" to pause-for events, and thus you do not need to turn it off during a long, silent pause.



    Examples:

    # SS off
    # live on
    # Pause-For 01:00:00 (hour-long live concert)
    # live off
    # ss on

Read more about using this feature.






# Relay-For

TuneTracker's "# Relay-For" lets you receive and relay an MP3 audio stream coming from a Internet/intranet radio station located elsewhere, for any specified length of time. Relay-For can also be used to play an audio file located elsewhere such as on the Internet or from across a LAN.

    Examples:

    # Relay-For 00:10:00 http://123.456.789.101:123456
    # Relay-For 99:00:00 http://123.456.789.101:123456
We have other commands that also contain the word "relay" and refer to swticher relays, so please don't let the word "relay" in this command confuse you. The Relay-For command refers to the relaying of an Internet/intranet stream or the playing of an audio file from a remote server.

Relay-For events can also be assigned to
configurable buttons, for manual access. More on that on the "Read More" page.

Read more about using this feature.






# Run (Command Center™ Only)

# Run allows you to launch programs and scripts at specific times. Since TuneTracker™ is a 24 hour "time machine," you can take advantage of its time awareness to perform duties such as downloading news reports, generating program logs, retrieving files from another computer, uploading a playlist to the web, doing a reboot; essentially, any task that can be run as a script or a program can be launched by TuneTracker's # Run command.

Note that at the end of each line containing a # Run command, you must include an ampersand (&). Do not fail to include that or it could cause TuneTracker™ to stop at the line and go no further.

If you are unable to create such scripting yourself, our staff is available to write scripts to perform almost any function you can dream up.
Write to us to discuss your ideas!


    Examples:

    # Run /boot/home/config/bin/GetWeather.sh &
    # Run /boot/home/config/bin/shutdown -r &
    # Run /boot/home/config/bin/SendPlaylist.sh &
    # Run /boot/home/config/bin/DownloadNews.sh &

To assure they are not skipped-over, # Run commands are normally best placed right after a Time-Correct.

In addition to being automated, # Run commands can also be assigned to configurable buttons and given labels matching their purpose, such as "Do Backups," "Make Logs," etc.




# DoBackups (Command Center™ Only)

Add this line at a time in your program log when you would like Command Center to do a complete backup of your main hard drive to your TuneBacker drive. Be sure to position it in a place where it won't get skipped over by a Time-Correct. TuneTracker will launch DoBackups as a background task, and at the end of the process, will display a little alert window indicating your backups are completed.


    Example:

    # DoBackups




# GetFile (Command Center™ Only)

# GetPlay performs a single, useful function. It dynamically grabs one file from a specified folder and plays it, regardless of its filename. If more than one file exits, GetFile takes the one that would be at the start of the list, alphanumerically.

GetPlay is intended for situations where you are unable to know in advance the name of a file you need to play. It's useful if you are auto-downloading a podcast each day and want to broadcast it without having to edit the podcast's filename or mess with editing the program log. For best results, always delete the previous file before downloading the new one. This can be handled automatically, and can be accomplished with a simple script. If you need assistance with creating the script, contact us.

To assure GetPlay works as expected, be certain the path and foldername you use is identical to the path and foldername where the file is stored.

  •   Example:

    # GetFile /boot/Station/Programs/DailyPodcast/
GetFile should not be confused with PlayFolder, a TuneStacker command, which collects all the contents of a folder and adds it to the program log. PlayFolder must find the files at the time the program log is created. GetFile is dynamic, is performed by TuneTracker, and grabs a single file, moments before it will be played. For that reason, GetFile is forgiving if the required file isn't available until shortly before it's needed.





# GetPlay (Command Center™ Only)

# GetPlay is a huge time-saver and an excellent way to assure that a program whose content changes every day gets played consistently. It behaves similarly to the TuneStacker™ command called "Play," except, instead of finding the files at the time you generate your program log in TuneStacker, # GetPlay tells TuneTracker™ to do the work instead, as it is playing out your program log. One of the big benefits of this approach is that it is very forgiving about missing files. By letting TuneTracker™ retrieve the files a split second before they are needed, you'll have the opportunity to add files right up to the very last minute.

To get a sense of how # GetPlay works, let's use an imaginary situation. Let's say you have a daily one-minute program called "Today in Tech History." It arrives on CD once a week, and you normally dub the shows into your /boot/Station/Programs folder as soon as the CD arrives in the mail each week. From now on, dub them in with filenames that look like this:

TechHistory_11-03-06.mp3
TechHistory_11-04-06.mp3
TechHistory_11-05-06.mp3
TechHistory_11-06-06.mp3


Then, in your format clocks/master logs, the line you add to your programming should look like this:

  •   Example:

    # GetPlay /boot/Station/Programs/TechHistory_%D.mp3

TuneTracker™ will see the line and automatically substitute the current day's date for %D when looking for the file. Thus, you only need to add the line once to your master log, and from then on you never have to touch the logs again! Just make sure your files follow the same naming scheme all the time and you'll be all set.

NOTE! Click "Read more" to learn how you can specify not only the day, but the hour, in the filename, a great time-saver if you have voice-tracks in your logs...make one format clock instead of 24!

Read more about using this feature (including European date option).







# Overlay (Command Center™ Only)

Overlay lets you play an audio file at a specified time, "over the top" of other programming you're running. This is useful for situations where you're broadcasting a meeting, concert, lecture, or other
block programming that runs past the top of the hour, necessitating the playing of a station-ID over the top.

The complete list of overlays for a given day's programming must be placed at the beginning of your program log.


  •   Example:

    # Overlay 20:00:00 Comment StationID
    # Hour 0 (start of day)


The example above will result in Command Center playing a station ID at the top of the 8 p.m. hour. If more than one audio file with the Comment, "StationID" is found, Command Center will rotate through them, playing the next one in the rotation each time that particular type of Overlay is required.

There's lots more information available on this feature...

Read more about using this feature.






# Chime (Command Center™ Only)

A classic radio feature that lets you play a chime or tone at the top of each hour (without ducking the underlying audio.) It's much more flexible than that though. You can rotate through cuts of any type, play them only on certain hours, and play them at any time during an hour. Not only a nice way to subtly indicate the top of the hour, but also to do clever things like the insertion of sound effects at unpredictable times during the day as a part of a call-in contest.

The complete list of overlays for a given day's programming must be placed at the beginning of your program log.


  •   Examples:

    # Chime 01:00:00 Comment Tone
    # Hour 0 (start of day)

    # Chime 10:37:10 Comment ContestSFX
    # Hour 0 (start of day)


The example above will result in Command Center playing a tone at the top of the 1 a.m. hour. If more than one audio file with the Comment, "Tone" is found, Command Center will rotate through them, playing the next one in the rotation each time that particular type of Chime is required. In the second example, an "out of nowhere" sound effect will drop in over your programming, signalling that it's time to call in for the contest, or to add the latest "secret sound" to the list of farm animals they've heard this week, or whatever other sort of "contest mischief" you're up to.






# VT (Voice-Track) (Command Center™ Only)

We feel every element of this command is so important that we aren't going to risk moving any of it to a "read more" page. The full explanation is covered right here.

Important facts about VT:

  • # VT can cause a voice-track to be played over the ramp of a song, timed to assure the voice-track ends just as the singing begins.
  • # VT can be used to find and add a "talkbed" under any voice audio.
  • # VT can do both in one shot, placing a talkbed beneath a voice-track, then segueing into the ramp of a song
  • The item immediately following a voice-track does not need a ramp assigned to it in order to take advantage of just the talkbed feature. Thus, # VT is great as a way of placing music beneath information like bulletins and headlines, weather, traffic reports, sports, PSAs, etc.

# VT identifies the event just beneath it as a voice-track, so TuneTracker™ knows to overlap it with the tracks preceding and following it if those tracks have their
ramp times marked. # VT can also be used to add a talkbed (background music) behind a voice-track or other audio file.

# VT will ONLY overlap an audio file with a song by the number of seconds assigned to that song's OnRamp or OffRamp. If no ramp time is assigned, overlap will be no different than any other normal transition

The song's ramp will be ducked (reduced) in volume until the voice-track is finished. The amount of ducking is based on the number you have entered in the "Voice track" text box in Command Center System Preferences. A value of around .3 (3/10th volume) works well.
    Example 1

    # VT
    /boot/Station/Voice-Tracks/VT_03-22-09_Seg3.wav
    /boot/Station/Music/Victory/Never Alone.mp3
In Example 1 above, Command Center will start playing the voice-track file, and will overlap as much of it with the song as will fit, based on how long the song's ramp time is.


# VT WITH TALKBED (don't miss this feature!!)

The talkbed capabilities in # VT are extremely useful as a means of putting music beneath voice-tracks, news or sports headlines, weather forecasts, and any other item that is improved by the addition of a background track. To use it, just specify an attribute and value (such as "Comment TalkBed" or "Gender Instrumental") that corresponds to at least one file in your library that's marked that way. If there's more than one match, Command Center will rotate through the available music beds, using a different one each time.

# VT plays the talk bed at a ducked (reduced) volume, based a number value you have entered in the Overlap text box in Command Center System Preferences. A value of around .3 (3/10th volume) works well.

    Example 2

    # VT Comment MusicBkg
    /boot/Station/Voice-Tracks/VoiceTrack_03-22-09_Seg3.wav
    /boot/Station/Music/Victory/Never Alone.mp3

In Example 2 above, Command Center will find an audio file with the Comment, "MusicBkg" and play that music underneath the voice-track, until it's time to overlap the voice-track with the song, "Never Alone." At that point, the talkbed music will go away and the song's ramp will take its place. If your ramp time is accurate, the voice-track will conclude just as the singing or main theme begins. If the song has no ramp marked, the talkbed will play beneath the entire voice-track.

Staying with the example above, if there are multiple tracks matching the criteria, "Comment MusicBkg," then Command Center will rotate through them, always using the next one in the list. If there's only one track matching the criteria, that track will be used every time.

    Example 3

    # VT Comment WeatherBed
    /boot/Station/Weather/EveningForecast.wav
    /boot/Station/Jingles/Jingle03.mp3

In Example 3 above, rather than a voice-track, we have a weather forecast. Command Center will find an audio file with the Comment, "WeatherBed" and play that music underneath the weather forecast. After the forecast is over, the jingle will play. You could just as easily do # VT Comment SportsBed or NewsBed, or anything you like, to enhance the sound of your reports.





# TimeAnnounce (Command Center™ Only)

Command Center™ comes with a full set of professionally-voiced time announcements that can be added to your log whenever you want them.


    Examples:

    # TimeAnnounce
    # TimeAnnounce /boot/path/foldername
Especially when coupled with our Temperature Announcement Package, TimeAnnounce can be customized and personalized in many exciting ways, and be turned into a sellable feature that can generate nice ongoing income for your station.

Read More about using this feature.






# TempAnnounce (Command Center™ Only...requires purchase of
Temperature Announcement Package)

Temperature announcements, a purchasable add-on to Command Center™, are intended to play immediately following a time announcement. Always use the temperature announcements right after a time announcement, because the temperature announcements are worded to follow them, as shown in the example below.

  •   Example:

    # TimeAnnounce
    # TempAnnounce
    Play /boot/Station/Commercials/ttsponsor_1stnationalbank.mp3

As you can see in the example above, the syntax is almost identical to TimeAnnounce. Not only do temperature announcements give your station a great new service and a more "live" sound, they're also easily profitable. The announcement of time and temperature is a very a sellable commodity. Many stations offer a "time and temp" package to advertisers such as banks and other institutions. In the example above, the listeners might hear something like:

"It's 7:35 and 46 degrees. A time and temperature check from your friends at 1st National Bank...the friendly bank, downtown Spotsville. Open your account today!"

Read more about using this feature.






# LiveAssist (Command Center Only)

LiveAssist command toggles Live-Assist Mode on and off. Normally only the "Off" feature is required, at the end of a section of program log, as a precaution against the possibility a show host might walk away and forget to turn Live-Assist Mode off manually.



    Examples:

    # LiveAssist On
    # Live Assist Off
It is worthwhile reading the additional information on this feature if you wish to use it, to assure you make the best use of it for your situation...

Read More about using this feature.




# HotTrack (Command Center Only)

HotTrack is a feature for owners of our ChannelCaster 4, ChannelCaster 8, and ChannelCaster 16 switcher-based systems. It is used to play a digital audio file such as a DJ liner or call letters over the top of a live satellite audio feed, When a relay closure is received on a particular relay channel, Command Center plays an audio file based on the attribute you specify, such as "Comment ID."



    Examples:

    # HotTrack 2 Comment CallLetters
    # HotTrack 7 Comment JonSmith
In the first example above, Command Center will listen to relay channel 2, and if a closure is received, a file marked with the Comment "CallLetters" is played. In the second example, Command Center will listen to relay channel 7, and if a closure is received, a file marked with the Comment "JoeSmith" is played.

HotTrack finds every file matching the criteria you've specified, and rotates through them, so if the same Comment is requested in a future HotTrack, Command Center will play the next matching track in the rotation.

To tell Command Center to stop listening to the specified relay channel, use the "Ignore" command, as described elsewhere on this page.

There's more information available under the "Read More" link, just below.

Read More about using this feature.






# Route-For (Command Center Only)

Route-For is a switcher control feature for use with our ChannelCaster 4, ChannelCaster 8, and ChannelCaster 16 switcher-based systems.. It is used to automatically switch among different input and outputs on the Broadcast Tools line of switcher boxes. Regardless of which of the switcher boxes came in your ChannelCaster package, the syntax you use is the same.

Note that you can cause more than one switcher routing to happen at the same time. See the "Read More" below for details.



    Examples:

    # Route-For 00:10:00 Input 2 to Output 1 NBC News
    # Route-For 00:10:00 2-1 NBC News
    # Route-For 00:05:00 2-1,3-2,4-3,5-4 Multiple Event Switch
    # Route-For 99:00:00 12-3 Church Service
In the first example above, switcher input channel 2 will be opened and sent to output channel 1 for ten minutes. The second example does the same thing as the first, but shows that you have the option to express inputs and outputs more simply. In example 3, multiple audio routings will occur. Separate them with commas but no spaces. In the fourth example, which uses our 99 hour "infinite" designation, the switcher channel will be held open until it is interrupted using our # Interrupt command. In all three examples, the wording at the end will be displayed in Command Center as the description of the switcher event.

There's lots more information available under the "Read More" link.

Read More about using this feature.






# Route-On, # Route-Off

If you use the Switcher or Route-For commands, 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.



    Examples:

    # Route-On Input 2 to Output 1
    # Route-Off Input 2 to Output 1

    # Route-On 2-1
    # Route-Off 2-1

    # Route-On 2-2,3-1,4-4,15-3
    # Route-Off 2-2,3-1,4-4,15-3
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. In the second example, the same thing happens, but it is expressed in short-form style. Either approach works equally well. In the third example, multiple inputs and outputs will be routed. Note they are separated by commas. Do not include spaces!

Read More about using this feature.






# Switcher

The Switcher command is the fast, easy way to schedule an all-in-one switcher event that includes responding to relay signals from the network. In a single line, it specifies the audio input you want, the output you wish it sent to, the maximum length of time it should stay on the air if not interrupted by a relay, the label you wish to display for the event in Command Center, and if you wish, also the location of a list of liners, IDs, and jingles you want played if certain specific relays are received during the satellite event.


    Examples:


    # Switcher 00:12:00 Input 3 to Output 2 Listen 9 NBC News

    # Switcher 00:12:00 Listen 9 3-2 NBC News

    # Switcher 00:45:00 Listen 2 1,4-2,16-3,8-1 Morning Switcher Routings

    # Switcher HotTrackList1 Input 3 to Output 2 Listen 9 Satellite Music Segment Two

In the first example above, Command Center is being told to route audio input 3 to audio output 2 for a maximum of 12 minutes, while listening to relay #9 for a closure from the network. If a closure is received, Command Center will break out of the event before it is scheduled to end, otherwise it'll hold it open for the entire length specified. When the event is ended, its audio routing will be closed on the switcher, and the specified relay will no longer be monitored. The second example accomplishes the exact same thing, in simpler short-form. The third example accomplishes multiple audio routings. The routings are separated by commas but no spaces. Note that when using the short-form, you must put the Listen element before the routing instructions, not after. Just duplicate the style in the examples above and you'll be fine. The fourth example adds the name of a HotTrack list that Command Center should load, which contains details on liners and other elements that should be played during the satellite event if certain relay closures are received. Read more below for details on how to create a HotTrack list.

Read More about using this feature.






# SendRelay

SendRelay causes a relay closure to occur on your switcher box or relay box. It can be used to trigger an external event such as turning on a tape deck, locking the front doors, lowering transmitter power, even starting the coffee maker before the morning crew goes on the air. Any electrical switch function can theoretically be wired up to work with such a relay closure. Since the devices sold by TuneTracker Systems all have a minimum of 16 available relay terminal sets available, the sky, and your imagination, are the only limitations.


    Examples:

    # SendRelay 1
    # SendRelay 12
The first example closes relay circuit #1 on your switcher or relay box. The second example closes relay circuit #12. The closure is momentary. See the manual for your particular product to determine the exact length of the closure.

In addition to automating relay closures, you can also assign one of Command Center's
configurable buttons to send a relay closure, and label it accordingly. You can, for example, have a "Lower Power" button or a "Make Coffee" button.




# SendTone

SendTone is a command that will cause your station to broadcast a tone at any frequency for any length of time. It is placed within your program log between songs or other audio events, so that it plays in sequence with the other items in your programming day. It can be used to broadcast an alert tone, or a trigger tone for automation and syndication purposes.


    Examples:

    # SendTone 25 300
    # TimedTone 1000 1000
The first example plays a 25 hertz tone for 300 milliseconds (.3 seconds). The second example plays a 1000 hertz tone for 1000 milliseconds (one second).





# TimedTone

TimedTone is for special situations where your station might want to send a tone over the air at a specific time, without regard for what else is playing. TimedTone will force a tone to play at that time, even if that causes it to overlap with something else that is already on the air. You can put all of the day's TimedTone events in a list at the beginning of the program log, and Command Center will make "mental note" of them and play them at the appropriate time of day. Unlike the SendTone command, which is designed to be played in log sequence among audio events, TimedTone is hard-coded to play rigidly at an exact time.


    Examples:

    # TimedTone 01:00:00 25 300
    # TimedTone 13:41:25 1000 1000
The first example plays a 25 hertz tone for 300 milliseconds (.3 seconds) at 1 a.m.. The second example plays a 1000 hertz tone for 1000 milliseconds (one second) at 13:41:25 in the afternoon.





# ClearSwitcher

This simple command will clear all open channels on your Broadcast Tools switcher.


    Examples:

    # ClearSwitcher


The command above will give you a "clear board" on the switcher. One exception: if you have selected a "reserve switcher channel" in Command Center System Preferences, that channel will be left open.





# Listen (Command Center Only)

When the Listen command is encountered in your program log, Command Center perks up its ears and begins monitoring the Broadcast Tools switcher relay channel number you specify. It will continue to listen to relay closures on that relay channel, and respond to them with a start-advance, until told to stop doing so by an "Ignore" command (covered below). The Command Center response when receiving a relay closure on that channel will be to advance to the next event in the program log, just the same as if you had hit the Start button or the spacebar. It is useful for cutting away from network broadcasts to take local breaks.



  •   Example:

    # Listen 1
    # Listen ALL
The first example tells Command Center to start listening to relay channel one. The second example tells Command Center to start listening to ALL the relay channels. Be careful with the ALL option, for obvious reasons.

Read More about using this feature.






# Ignore (Command Center Only)

# Ignore tells Command Center to no longer pay attention to relay closures received on a particular relay port of the Broadcast Tools line of switchers. It is advisable to use an # Ignore at the point in the log where a particular network broadcast that calls for local breaks is no longer being broadcast.



    Examples:

    # Ignore 1
    # Ignore ALL
The first example tells Command Center to start ignoring relay channel one. The second example tells Command Center to start ignoring ALL the relay channels. The ALL command is useful as a way of quickly clearing a group of Listen channels. Beware of one thing though. ALL will also clear your default "permanent" input channel as specified in System Prefs, if you're using that feature. If it is cleared, you must go into System Prefs and just click "Save and Use" to re-establish the default relay channel again.

Read More about using this feature.






# TalkBed (Command Center Only)

TalkBed lets you put a music bed beneath a voice-track, news headlines, sports, weather, or any other announcer cut that would benefit from instrumental accompaniment. It's extremely easy to use, and can do a lot to enhance your station sound.

  •   Example 1:

    # TalkBed Comment BGBed
    /boot/Station/Voice-Tracks/VoiceTrack_1234.mp3


The above assumes you've marked the Comment field of at least one instrumental song with "BGBed," though the wording you use can be anything you like. When Command Center sees the TalkBed command, it'll find a a file with a matching Comment and play that music bed under the audio file that follows, normally a voice track file. If there is more than one cut with the same Comment, "BGBed," Command Center will rotate through them, using the next one in the rotation each time.

Read More about using this feature.






# UseButtonPadSet (Command Center™ Only)

Loads and displays whichever customized set of ButtonPad buttons you specify. This allows Command Center to load the proper set of buttons for each time of day automatically.


    Examples:

    # UseButtonPadSet Morning Show
    # UseButtonPadSet Weekend Buttons
    # UseButtonPadSet News Block Buttons
    # UseButtonPadSet Ballgame Engineering Buttons

Use the exact name you gave the set when you created it in the button layout editor. To assure accuracy, you can copy and paste it directly from the editor to the line in your log, using CTRL-C for copy, and CTRL-V for paste.

Read More about using this feature.






# UseMyShowSet (Command Center™ Only)

Loads and displays whichever customized set of MyShow buttons you specify. This allows Command Center to load the proper set of buttons for each person's DJ show or talk show automatically, at a convenient time, such as just before each jock shift begins.


    Examples:

    # UseMyShowSet Sundays By Request
    # UseMyShowSet Bill's Billboard Countdown
    # UseMyShowSet Max in the Morning
    # UseMyShowSet Sheila Clark Show

Use the exact name you gave the set when you created it in the button layout editor. To assure accuracy, you can copy and paste it directly from the editor to the line in your log, using CTRL-C for copy, and CTRL-V for paste.

Read More about using this feature.






# ShowText (Command Center™ Only)

When Command Center arrives at the line in the program log requesting a ShowText, it displays the contents of a text file in the scrolling text box. This is handy as a way to automatically display reminders to DJs, or promo copy for them to read, at the exact right time of day. Use a path and filename to display a text file found on your hard drive, or a URL and filename to display a text file stored on the Internet.

    Examples:

    From local hard drive...

    # ShowText /boot/Station/Scripts/RequestShowTeaser.txt
    # ShowText /boot/Station/Memos/MorningStaffMemo.txt
    # ShowText /boot/Station/Text/PowerChangeReminder.txt
    # ShowText /boot/Station/Text/TimeToLockFrontDoor.txt

    From a web location...

    # ShowText http://www.sloansdrugstore.com/sloansdrugstore_ad1.txt
    # ShowText http://www.websitename.com/directoryname/promo3.txt

The contents of the text file will be displayed in the scrolling text box when Command Center reaches that item in your program log. It will remain in the text box until replaced by another ShowText event, or by a DJ's decision to display other text such as the forecast, a help file, etc.

The actual ShowText lines in your program logs do appear onscreen, looking much like an audio event, complete with a Start button. This is done intentionally, so that if the DJ wishes to, he/she can display the text early, before Command Center does so automatically. To manually display a ShowText file just click on that event line's green Start button.

All text files must in plain text format. All files created on Win If created under Windows, they must be saved in Unix format (no carriage returns).



Table of Contents