The TuneTracker™ Output Log


As TuneTracker plays through its broadcast day, it keeps a text log of everything that played, logged with the exact time when each event ran. The log also contains any memo lines you have added to your log for reference, and other information, depending on the version of TuneTracker you have.

By default, the output log is saved to /boot/home/, and the filename includes the broadcast date. Output logs are plain text, and may be stored, printed out, or e-mailed. They can also be processed using our CSacker utility (found in the "Extras" folder) to generate custom reports for proof-of-performance, music list submissions to BMI, etc.

During the course of the broadcast day, you can view a scrolling list of what has played by clicking the Output Log  x  box at the top of your TuneTracker™ Basic interface, or by hitting the letter "O" to in Command Center, to display the output log in the scrolling textbox. You can also right-click on the scrolling textbox and choose "View Output Log." Once displayed in Command Center, you can enlarge the textbox by hitting Enter, and can adjust font size, etc., as described on the Command Center Interface page.

In versions of Command Center prior to 4.0, the output log consists of a list of start times, paths, and filenames. Starting with Command Center 4.0, the output log is structured like a comma-separated database with much more information, including Start Time, Artist, Title, Album, Comment, Genre, and others. Command Center 4.0 and up also logs more kinds of automation events, and a variety of error messages to the output log to alert station staff to potential problems in their logs, missing files, etc. Our System Prefs page describes how to choose which audio file information you want included in the output log.

You can use the new advanced output logging to:

• Assure items are playing at their correct times
• See whether your DJs are sticking to the format
• Look for evidences of silences or other problems
• Analyze your programming in spreadsheets, charts, and graphs
• Prove something played
• Confirm something didn't play
• Look for areas where you can improve what your station is doing
• Search for lists of specific items using CSacker
• Prepare reports for ASCAP, BMI, and SESAC
• Assure Internet Broadcasters are in compliance with DMCI
• Comply with FCC regulations

We encourage you to spend some time studying the contents of your output logs. As you do, you'll discover they're a rich source of not only information, but as a Programmer, inspiration.



Table of Contents