Setup Requirements
No special treatment is needed for music records, however, non-music content such as jingles, liners, voice tracks, DCS directives, etc., require special treatment. Review the Keyword Flags section below for details.
Be sure that the Music Path and Traffic Path in your LogMerge setup for a station are different locations. This is because the actual filenames of the source music log and source traffic log will be identical. |
DCS and Maestro-specific keywords are entered in Results 98 via the Liner Notes section of the software. See the section on entering liner notes for specific instructions on how to create liner notes.
Keyword / Explanation |
|
---|---|
@HMxx |
|
This is a marker that can be placed in the format to tell LogMerge whether or not a given period of time is automated (voice-tracked). |
|
@TMxx |
|
Traffic merge point, where xx refers to the traffic cluster start time in minutes. Note: The time value used in the liner note "Traffic Merge" must be the time the commercial break starts on the traffic log. If this value points to a time which does not exist on the traffic log an error will be generated in LogMerge, conversely if the time is beyond the first element LogMerge will miss the preceding spots. |
|
@VTxxxxmmss |
|
Direct Cart Call Note: Cart numbers can include DCS macro characters, including: |
|
@DDttmm????Description (Description up to 12 characters) |
|
Load Directive where tt = type of DCS load directive "LR" OR "LP" (load break or load and play break) Time approximate can be used by placing a ~ (tilde) character as first element in the description field, time update by placing a $ (dollar sign) character as the first element in the description field. |
|
@DWmmrrDescription (Description up to 16 characters) |
|
Load Window Directive where mm = minute value where the directive should occur For Set Voice, use $xx in the description, where xx equals the voice number. For other windows, use $xxxx, where xxxx is the appropriate value for the window contents. Refer to your audio system documentation for more information. |
|
@DF??mmDescription (Description up to 16 characters) |
|
User Function Call Directive |
|
Log Notes |
Liner Notes - No special keyword is needed. Liner Notes are viewed as a DCS/Maestro/Studio Log Note. Liner Notes will be included in the final log only in non-automated hours as a default. To force all log notes to be included in the final log, set the Keep All Log Notes setting in configuration. |
The DCS and Maestro-specific commands are entered using Results 98's Liner Notes entry. Liner notes are scheduled using Results 98's feature called "scheduled stopset liners". Creating a liner note is a two part process:
1. | The Results 98 Daypart clock is used to build a list of music categories. By designating Category 16, "Stopset" in the daypart clock, you are telling Results 98 not to schedule music in that time slot, instead it should select a 'Stopset Liner". Editing the daypart clock is done in Results 98 on the Setup menu by selecting "Edit Daypart Clocks". |
2. | Part two of the process is creating the actual liner note. Liner notes are created on the Setup menu by selecting Stopset Liners. Results 98 has "rotating liners" and "scheduled liners". To create Liner Notes to be exported to DCS, use only "scheduled liners". Scheduled liners are created by selecting first the day, then hour you are scheduling. Results 98 will display each time slot of the daypart clock and prompt you for the liner you want to scheduled. When you add a liner that is to be one of the DCS/Maestro keywords in Results 98, be sure that each character is in the appropriate position. Each character in the liner must meet the special requirements of the DCS/Maestro keywords. For specific commands (keywords), use the information in the table above. |