LogMerge is looking for an exported traffic log that your traffic system creates with a utility supplied by your traffic vendor. It is the export utility that supports a DCS Generic Log output. Your traffic vendor can supply this utility if you don't already have it. Ask for the `DCS log export utility'.

LogMerge doesn't require much in the way of special treatment of the traffic log. Since most, if not all, of the special DCS log directives (i.e., Load, Load Play, etc.) are handled on the music log, the traffic log exports commercial information and a key word telling LogMerge where to return to the music log for more information at the end of a stop set.

There are two keys to ensuring the traffic log will merge correctly; 1) ensuring the correct break start times; and 2) that there's a "Return to Music" flag at the end of each break.

NOTE: Consult your traffic system documentation for instructions on the correct entry of special DCS, Maestro or XStudio information.

Correct start time for the break

The commercial break start times on the traffic log must match the music system's scheduled break start time (typically handled by a `breaknote' on the music log). If the music log's break start time for the first break in the 6:00am hour is 6:12, the traffic log's first availability on the format must be 6:12. If this isn't done correctly, not all the commercial content will be merged properly.

As an example, if the music system's scheduled break is 6:12 and the traffic log's formatted break start is 6:11, all commercial content scheduled between 6:11 and 6:12 will not make it to the merged log.

LogMerge compares the merged log to the original traffic log as a part of the merge process to validate whether or not all of traffic's scheduled commercials are now on the final log. If not, an entry is made in the LogMerge error file is made.

RTM Program title at the end of the break

LogMerge looks for a special program title to tell it when to return to the music log from the traffic log during the merge process. The program title is the three (3) letters `RTM', which indicates Return to Music to LogMerge. This program title must be present at the end of each of the commercial stop sets in order for the merge to function properly. RTM is the text or description of the program title. Enter the program title in your traffic system as normal, but where the title text would go (i.e., News), type RTM.

Log Notes and Automation

LogMerge automatically strips out any Log Notes you may have placed on the traffic log during automated hours as a default.  To pass all log notes through to the finished output log regardless of whether or not a given hour is automated, set the configuration option Retain ALL Log Notes in Output Log.

Sample Log Format

Below is a sample log format for use with LogMerge (the comments are for information only and would not be a part of the format):

LogMerge will pass all meaningful material between the beginning of a break and the RTM marker, including program titles, log notes (non-automated hours), etc.

The traffic system's log export utility will generally have a setup or configuration portion that, among other things, allows the user to set where the exported log will be sent. In a LAN (local area network) environment, this would normally be the audio system's working directory. However, since these exported logs are now being further utilized to included music, another directory needs to be specified. The recommended location would be one under the audio system working directory named something like TRLOGS or LOGS. An example export directory would be: F:\DCS\TRLOGS

If this directory does not already exist, it will need to be created on the target drive before exporting your first traffic log.

If the exported log is to placed on floppy disk for transport to another PC, the typical export location would be A:\ or B:\ - one of the floppy drives.

Special Considerations

Some traffic systems will not export a DCS Generic Log file properly unless each break has a Directive associated with it.  One such system is CBSI, which documents in it's DCS export utility that if a standard DCS Load Directive (D-LR in CBSI's Table of Event Names documentation) isn't present at a particular time for a cluster, the spots will be placed with the preceding DCS directive.  In an hour-long program block, this would result in all commercials being scheduled at the top of the hour, not spread properly throughout the hour.

To work around this, LogMerge provides for recognition of a directive (D-LR in CBSI's case) with text of "CBSI" as a "special case".  If LogMerge finds a directive in the traffic log with the text "CBSI" in the first 4 characters of the directive description, it will skip the item.  The effect is that this special directive serves as a place holder to ensure the commercials are placed in the correct place in the hour.

The CBSI traffic system is the only known vendor that places such a requirement on their DCS Generic Log export utility. If your traffic system has this requirement, too, then use the same technique described to have LogMerge discard the unwanted directives.

 

---