MusicPro System Setup

Setup Requirements

MusicPro v5.07e or greater is required for use with LogMerge. If you do not have the correct version, you must upgrade MusicPro to a current version. No special treatment is needed for music records, however, non-music content such as jingles, liners, voice tracks, DCS directives, etc., require special treatment.

Keyword Flags

DCS-specific keywords are entered in MusicPro via the Liner Codes section of the software. See the section on entering liner codes for specific instructions on how to create liner codes.

Be aware that MusicPro does not provide a time value for non-music records that are exported, and as a result, it is imperative that each hour of the log have as the first line of the format either a standard hour or automated hour marker. LogMerge "counts" hour markers to determine the current hour value. As a result, every hour of the day must be represented by the MusicPro log, even if hours that contain no music. Otherwise, LogMerge will "lose track" of the hours. Note that no "dummy" music records are required (as LogMerge v4.x and prior did) in order to keep track of the correct log hour - as long as each of the 24 hours is on the log and each hour has an hour marker Liner Code entered.

The table below is for MusicPro v6.05 or greater. For MusicPro versions less than v6.05, use "/DCS66" for the beginning of the entry, instead of the "/DCS68" listed in the table.

Keyword / Explanation
/DCS68DCS_HR
	This is an hour marker that would appear as the first element of the format in a non automated (live-assist) hour.
/DCS68DCS_HR_VOICE_TRACK??
	This is an hour marker that would appear as the first element of the format in an automated hour. ?? represents the voice number for the hour. Additionally, this value will be inserted in cart numbers containing ##.
/DCS68DCS_TRAFFIC MERGE??
	Traffic merge point where ?? refers to traffic cluster start time in minutes. See the note below for further details on traffic merge points.
/DCS68DCS_CART_VT_????_MMSS
	Direct Cart Call where ???? = Cart Number where MMSS = length of cart Note: Cart numbers can include DCS macro characters, including: % - Day of week (1=Monday, 7=Sunday) ^ - Current hour (1=1 o'clock, C=12 o'clock) ## - Current Voice (01-99)
/DCS68DCS_DIRECTIVE_LR_mm_????_DESCRIPTION (up to 24 characters)
	Load Directive where LR = type of DCS load directive "LR" OR "LP" (load break or load and play break) where mm = minute value where the directive should occur where ???? = minutes and seconds indicating the length of the load where DESCRIPTION = user description field (24-character max) 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.
/DCS68DCS_DIRECTIVE_LW_mm_rr00_DESCRIPTION (up to 24 characters)
	Load Window Directive where mm = minute value where the directive should occur where rr = the relay number of window to load. For Set Voice, use 99 where DESCRIPTION = user description field (24-character max) 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.
/DCS68DCS_FUNCTION_??_mm_DESCRIPTION (up to 24 characters)
	DCS User Function Call Directive where ?? = DCS function number 01-99 where mm = minute at which to execute function where DESCRIPTION is descriptive only
/DCS68DCS_LN_DESCRIPTION (up to 24 characters)
	Log Note. Log 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 time value used in the Breaknote "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.

Liner Codes Entry

The DCS-specific commands will be entered using MusicPro’s Liner Codes entry. Liner Codes can be entered anywhere in the music log format. Liner Codes are a single, non-alphanumeric character (0-9,a-z,*,@ cannot be used). The program allows for defining the meaning of the liner code, which is where we’ll place the DCS command information.

To enter a liner code in MusicPro, the user touches the [F5] key. A list of available liner codes (the single characters mentioned above) appears, and one is selected and inserted in the format.

To define a liner code, the user touches the [F4] key, select the code to edit and enters the appropriate text. For DCS-specific commands, use the information in the table above.