EditMaestro
backWORK IN PROGRESS - Please understand that we are actively rewriting much of our documentation and this page is currently "under construction"; if there's anything that you'd like to see added to and/or expanded upon, please let us know by
sending us a smile.
EditIntroduction
RadioTraffic converts to a specific DCS / Maestro log format. Any references to DCS also apply to Maestro, which uses the same type of log interface to export the log.
EditStation Configuration
To configure RadioTraffic to work with Maestro, you will first need modify the station configuration to utilize Maestro as the automation system. In the administration module, open 'Stations'. Select the station you want to configure and double click. Once the station configuration is visible, select the 'Files' tab. Select the 'Product' to Maestro using the drop down selection tool. The 'Automation Log Path' is where RadioTraffic will export the log to, so set this to the file system folder that Maestro will pull the file from. The 'Station Identifier' will need to match the 'station number' described in the Maestro User Manual (which is a number from 0 to 9).
EditCart Numbers
Maestro system can use cart number from 001 to 999 with a single letter in front to identify the type. In other words, limited to 4 characters alpha/numeric.
EditAutomation Commands
RadioTraffic automation commands directly map to Maestro "directives". These can be configured in the list of automation commands and placed on templates, formats and logs. At the time of this writing, there are five Maestro directives; the LR, LS, LP, LW, CR and XF (undocumented).
The directives you need can be configured by adding new automation commands.
- In the administration module, select 'Templates'. If prompted, select which station.
- In the main menu, click on 'Log Elements' to expand the menu.
- Select the 'Automation Commands' menu item.
- At this point you will see a dialog that displays all of the automation commands available to the station you selected. Click the 'Add' button to create a new automation command.
- On the right hand side, it will display "New Item" in the 'Description' field. Replace "New Item" with a description that will be easily identifiable when editing your templates, formats and/or logs.
- In the 'Command' field, enter the required "directive" as required by the Maestro automation system. In the case of the CR (Close Relay) directive for relay #55, you'd enter CR55.
- Leave the 'Cart #' field blank.
- Click the 'Save' button to commit this new item to the list of available automation commands.
For more information regarding directives, please consult the Maestro User Manual. For specific information related to the log file, be sure to review chapter 11 - Generic Log File Record Descriptions.
If you are, instead, trying to "schedule" a fixed position audio event; the process is very similar to the above except:
- Leave the 'Command' field blank.
- Enter the cart number in the 'Cart #' field.
EditLog Notes
Log notes export automatically and require no additional configuration.
EditPrograms
Programs export automatically and require no additional configuration.
EditAvails/Breaks
Avails automatically export to the Maestro file format as Maestro 'directives'. It is recommended that you specify whether the avail is an LS, LR or LP type by appending the name of the break with a Backslash character (\) followed by the LS, LR or LP respectively. At this time, we will default every avail as an LS type; however, that could change in the future so it is recommended that you take the time to edit the names of your avails accordingly.
EditLog Reconciliation
Automatic reconciliation is supported using Maestro's native aired file format. The file name should be in the MMDDYYSn.ADT pattern where MM is the month, DD is the day, YY is the last two digits of the yar and n represents the station identifier.
Only items flagged as PlayCart are imported.
EditFAQ
TODO Add any questions as they come up to this section.
EditAdditional Information
For additional documentation concerning working with playlists files in the Maestro system, please refer to the Maestro documentation on the subject: