Using the Program Log Queue

Important Things to Know Editing/Reloading Program Logs... The easiest, and most-direct way to make changes to the current day's program log is by dragging and dropping files directly into the program log while it is displayed in Command Center. If you instead opt to use a text editor, Lightning, or TuneStacker to change a program log Command Center is presently using, or the one it will use tomorrow and you want Command Center to notice the changes and act on them, you need to force it to reload the current-day's program log. There are two ways to do so. 1. In Command Center 3.3 or higher: do CTRL-R (for reload). You're done! 2. In TT Basic and earlier Command Centers, go to the Program Log Queue, and double-click on the present day's program log.

The Program Log Queue (pronounced like the letter, "q") is Command Center's way of knowing which program logs you want to play, and in what order.

You can select one of three ways to tell Command Center which program logs to use. You can select the approach that makes the most sense for your situation and the way you like to work, by choosing the "Program log queue type" option on the Misc tab inside Command Center's System Prefs.

1. Editable Loop  This is the approach Command Center will use automatically, if you don't specify one of the other two methods. It lets you drag in program log files using any file names you like, and build as long a list of program logs as you like. Command Center will play one day after another until it reaches the bottom of the list, then it will loop back around to the top and play the first file again. You can access the Program Log Queue by hitting the number 2 on your keyboard (just remember, "TWO for Q"), or by right-clicking on your running program log and choosing "View Program Log Queue." If you have no logs loaded, the empty-looking left side of the Command Center screen is the queue. You can add program logs to the queue using drag-n-drop. The easiest way to access program log files you wish to drag into the queue is to hit the letter "F" on your keyboard, which opens your Favorites folder. By default the favorites folder is /boot/Station/Logs/Program Logs/ (be absolutely certain the path shown in System Prefs ends with a slash / character! Assuming you have stored your program logs in that folder, you can then just drag them into Command Center from that folder, one after another.
   
   The first log you drop into the empty Program Log Queue can be placed anywhere in the window pane, and it will automatically be placed in the top position. Any logs you drop in after that should be hovered over another log already in the queue, and then released. You'll know where it will fall by watching for a blue "drop-line." You can insert logs at the end of the list, or between logs already in the list. You are not limited by the number of positions visible on the screen. By using the scrollbar, you can add an unlimited number of logs to the queue. You can come back later and add more logs to the queue at any time by just re-opening the queue and dropping-in additional logs. To eliminate a log you no longer need, right-click on it and choose, "Remove."
   
   Command Center which program log you wish to broadcast by double-clicking on it. When you do so, Command Center will load that program log into its active memory, find the right time-of-day to begin broadcasting, and wait for you to hit Start.
   
   Important:  If you later make changes to the Program Log Queue, always double-click on the current day's program log to reload it. If you don't, Command Center may not know what log to use when you close the queue.
   
   Important:  Starting with Command Center 4, the editable Program Log Queue loops automatically. When Command Center gets to the bottom of the list of logs, it loops back around to the top of the list and starts running through it again. Thus, if that is not your intention, be certain to keep adding fresh logs to the bottom of the list. If you want Command Center to come to a dead stop after playing through a series of logs, we suggest you use the "Lock-to-Date" approach below.
   
   
   
2. Lock-to-Day  This one's very simple. As you create new program logs, name them according to the day of the week on which you want them to run, as follows: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday. Do not use file extensions such as .log. Just the plain, day-of-the-week for the filename. Store them in the Favorites folder you have specified under the Automation tab in System Prefs. If you have not specified a different one, the default there should be /boot/Station/Logs/Program Logs. Whenever you generate fresh program logs in TuneStacker, overwrite the ones already in your Favorites folder, using the same filenames already mentioned. Command Center will note the day-of-the-week from the computer's built-in clock/calendar and will automatically assure that the correct day's program log is playing.
   
   Important:  This is the best option to choose if you are automatically generating your program logs each week. This process can be completely automated using a script we can develop for you inexpensively. It's a wonderful approach for stations that want to "set it and forget it." Contact us for details.
   
   
   
3. Lock-to-Date  If you wish to create a program log for each unique program day and assure that only that log plays, no matter what, Lock-to-Date is for you. As you generate program logs in TuneStacker, do so into your Favorites folder using the broadcast date as the filename, like this: MMDDYY (Month Day Year). Examples: 112709 means November 27, 2009. 030310 means March 3, 2010. Do not add file extensions such as .log. Just use the date as demonstrated, as the filename. Command Center will stubbornly refuse to play any program log other than the one for the current day's date.
   
   Important:  This approach assumes you will have the required logs in place. If you do not, and Command Center arrives at a date for which there is not a file with a corresponding filename, it will sit there peacefully, doing nothing, until the phone rings at 3 a.m. and the General Manager disturbs your dreams with words of unpleasantness.

Table of Contents