If you are upgrading from an older version of LogMerge, an additional button will be presented if you installed LogMerge on the same machine as the older version.  This button enables you to convert your existing station setups to the newer version's scheme.  After once converting, the additional button will no longer be displayed.  See Appendix A for more information on the LOGMERGE.INI file, where station merge settings are stored.

Station Calls

Enter the call letters of the station for which you'll be merging files.

Use Traffic Log Files

A check box. If you wish to use traffic log files in the merge process, "check" the box, otherwise, "uncheck" the box.

Check DCS/Maestro Inventory

A check box.  If checked, all carts that appear on the finished (merged) log will be evaluated to see if the cart is in the audio inventory and whether or not the cart is valid for the log date.

If the cart exists in the audio inventory and is valid for the log date, LogMerge will substitute the correct cart length (to AUX mark) for the scheduled length of the song coming from your music scheduling system and use the description from the inventory.

Convert DCS macro characters in ALL hours

This is a check box that when selected, causes LogMerge to convert all occurrences of DCS, Maestro & XStudio macro characters in cart numbers from either the music log or traffic log.  If not "checked", only the music log will have macro characters converted.

Retain ALL log notes in output log

A check box, that when selected, will cause LogMerge to pass ALL log notes from the source logs, either music or traffic, to the finished output log.

LogMerge's default behavior (if not checked) is pass log notes through from the source logs only when an hour is not defined as automated. The presence of VOICE TRACK flags in the music log dictates whether or not a log hour is automated. See the section on setting up your music log output for the music system you're using for more details.

Skip Open Traffic Avails

A check box.  When selected, LogMerge will "skip" any source traffic log avail position that is considered "open" and not place it on the final output log.

Depending on the traffic system you use, this option may have no impact.  Computer Concepts traffic systems, for instance, will export unfilled log positions and insert a cart number of "****".  If you want these open positions on the final output log, leave the option unchecked.

Keep log descriptions from source logs

This option will force LogMerge to pass the original traffic log and music log descriptions for carts through to the final output log.  Note the default behavior (unchecked) is to replace the original description for a cart with the audio inventory description, if the cart exists in the inventory.

Source DCS Station Number

This is the "station number" you defined in your traffic system's log export configuration. This information is used to determine which log that's exported by the traffic system is to be used as the source traffic log for the merge. A typical entry would be: 1

Valid entries are 1-9, A-F (for stations 10-16).

The generic DCS Generic Log File naming convention (as it comes from the traffic system) is in the form mmddyySn.LOG where:
 
mm = Month
dd = Day
yy = Year (2-digit)
S = Station (fixed letter)
x = Station number (1-9, A-F for 10-16)

Target DCS Station Number

Enter the "station number" you wish this merged log file to be written to. This is the On-Air station number. An example would be: 1

Valid entries are 1-9, A-F (for stations 10-16).

The provision for a source station number and a target station is made to allow for differences in traffic system export capabilities and for situations where you may wish to actually change the station number of the log.  Normally, the source and target station numbers would be the same.

Music Path

Enter the location where your music system's exported log files will be located. i.e.:

C:\MSCAN\AMLOGS

You can also use the directory picker adjacent to the field to select the music directory.

Traffic Path

Enter the location where your traffic system's exported log files will be located. i.e.:
 
F:\DCS\TRLOGS

You can also use the directory picker adjacent to the field to select the traffic directory.

Working Directory

Enter the location of your working directory. This would usually be the directory in which you installed LogMerge, but you may choose any valid directory location.  Error files are placed in this directory.

C:\LOGMERGE

You can also use the directory picker adjacent to the field to select the music directory.

Output Directory

This is the location to which you want the finished, merged file to be sent (saved). Typically, this will either be the LAN (local area network) directory which is defined as DCS' working directory, i.e.:

F:\DCS

You can also use the directory picker adjacent to the field to select the output directory.

DCS Inventory

Enter the directory location and file name from which you want LogMerge to retrieve inventory information (the cart numbers, lengths, dates, etc.). This would typically be the LAN directory you set up as the DCS working directory in the DCS configuration. The file names are a bit different than you might expect, as they are tied to the assigned DCS node number (again from the DCS configuration file). These are:
 
Node        File Name    
1        CMINV00.DAT (those are zeros)
2        CMINV01.DAT
3        CMINV02.DAT
4        CMINV03.DAT
5        CMINV04.DAT
6        CMINV05.DAT
7        CMINV06.DAT
8        CMINV07.DAT
9        CMINV08.DAT
10        CMINV09.DAT
11        CMINV0A.DAT
12        CMINV0B.DAT
13        CMINV0C.DAT
14        CMINV0D.DAT
15        CMINV0E.DAT
16        CMINV0F.DAT
 
Here's an example entry for this field:
 
F:\DCS\CMINV01.DAT

You can also use the file picker adjacent to the field to select the inventory file.

Music Scheduling System for this Station

Select one of the available music systems, either Selector(TM), MusicMaster Type 1, MusicMaster Type 2, POWERGOLD, MusicPro, Music 1 or Results 98.
 
If you're using MusicMaster and are unsure whether or not it is what LogMerge defines as a Type 1 or Type 2, check the date stamp of the MusicMaster file named LOG2ASC.EXE. If the date is prior to October, 1993, select Type 1. If the date is later, select Type 2.