General Debug and Information Logs

There are several screens within DAD that allow users to obtain information about the system. There are also several logs that can be configured to record information such as GPI closures.

 

General Information Screens

Within DAD there are four basic screens that can be used for general information. These screens can also be useful in verifying proper system operation.

DCL Processing

Users can use the F-10 screen to view all DCL’s that have been processed by the system. This window will also display other vital information such as database information or errors.

In the example shown, a GPO Pulse and a Send Command DCL are shown. Database information is also shown. This is an example of a user changing a group in the Library.

Using the FLUSH TO button can save this information. A path for the file is listed beneath the button.

 

 

Audio Status

SHIFT+F4 will open the Audio Status screen. This windows displays the activity of the audio cards within DAD.

The Board number, Physical I/O and Device Stream numbers are listed on the left side. A set of meters along with basic audio cut information is displayed in the center portion.

This screen can in useful in determining the status of audio cards and their devices. It is also useful in determining where an audio cut is playing.

 

 

Audio Levels

Unique audio cut levels can be viewed from the SHIFT+F3 screen.

This window will display a fader that allows a user to manually over-ride the playback level of the cut. There will be a unique fader for each audio cut playing. Cut Number and Title are also displayed.

 

 
GPI/GPO Status

SHIFT+F2 will open the GPI/GPO Status window.

Here users can watch the overall status for both GPI and GPO interfaces. 

GPI information is listed on the left hand side with GPO information on the right. The number of overall triggers for the specific interface is shown within parenthesis to the right. A radio button will display to the left when the interface is actively triggered.  If the interface has been disabled, an asterisk will be displayed next to the GPI or GPO.

 

General Information Logs

Users can configure DAD for several information logs. These logs can be used for audio reconciliation to general information about system operation.

 

Asplay logs

Asplay logs are the most commonly used log in DAD. These logs are used to determine what played when, for how long and from where. Many stations use these logs to reconcile their Traffic and Music.

Asplay logs are enabled on a workstation basis. Uses simple add the line:

@SET ASPLAY=%location%

to the top of the DADnet or DADlocal.BAT file.  DAD will log any audio or command that is played from any machine that has been assigned ‘Program’ status within the Channel Assignments.

Asplay logs are saved to the \DAD\ASPLAY directory. In a network environment, these logs are written to the network data drive.

The naming format for the Asplay log can be configured. There are two basic styles.

These styles can be set from the workstations CFI. The workstation CFI line: ASPLAY_LOGGING_NAME_STYLE sets the naming format.

The older style follows the <%Location%>.<DOW> format. For example, ONAIR.MON would be the Monday Asplay file for the ONAIR machine. This file will append to itself each day of the week. This Mondays log will also show information for last Monday.

Another naming format will create a unique daily log. The newer style will follow the <%location%>mmddyy format. For example, ONAIR120102 would be the ONAIR log for December 1, 2002 .

Users can view the Asplay from the Reports button located in the Library screen. 

The Asplay log will list:

  • The Scheduled time and length of the cut.

  • The Actual time and length of the cut.

  • The date of the cut played.

  • The Title of the cut.

  • The Name of the playlist that contained the cut.

  • The machine the cut played from.

    •

     

    Branch Logs

    You can configure your DAD to log every branch  event that is executed using the "LOG_BRANCH" parameter in the workstation configuration file. To turn on branch logging set the line:  LOG_BRANCH = ON

    DAD can either be restarted or issue the DCL: OPEN LOG BRANCH.  Once logging is turned on, DAD will create a daily LOG file in the DAD\LOGS folder on the local hard drive. Log files names follow the format "BIyymmdd.log" and can be opened and viewed using any text editor.    Each branch log lists:  

    • The date and time a branch event was executed.

    • The machine that was playing the playlist containing the branch event.

    • The type of branch event.

    • Numbers and titles of audio cuts in the general vicinity of the branch event.

    • DCL commands that were used.  

     

    Text Box:

    The example log shown was created on May 23, 2000 .  Line two indicates that the branch position was 263.  Line three indicates that a branch event was performed at 6:15:00 a.m.   Line four indicates that an audio cut was playing when the branch event executed.  These lines are followed by information about cuts in the general vicinity of the branch event and internal DAD calculations.  The next branch event executes at line 23 (the third line up from the end of the log).

     

    GPI/GPO logs

    DAD can log every GPI or GPO  event that is executed using the "LOG_GPOGPI" parameter in the workstation configuration file. To turn on GPI logging set the line:  LOG_GPOGPI = ON

    DAD can either be restarted or issue the DCL: OPEN LOG GPI.  Once logging is turned on, DAD will create a daily LOG file in the DAD\LOGS folder on the local hard drive. Log files names follow the format "GIyymmdd.log" and can be opened and viewed using any text editor.    Each GPI log lists:  

     

    • The date and time a GPI/GPO event was executed.

    • The GPO Number and time the relay was opened [r closed.

    • The GPI bit number that received a voltage trigger.

    • The command associated with the GPI.  

     

    Text Box:

    The example log shown was created on December 11, 2002 .  The logs shows that a Pulse DCL for GPO number 2 was executed. This closed the GPO [on] then opened the GPO [off].  Information was also logged for a pulse of GPO 1.  The last eight lines show incoming trigger information for GPI’s. Each of the inputs for a GPI 8 were triggered. Each line shows the DCL associated with the input.

     

    Record Logs

    Record logs are automatically enabled when a user loads a Timed Record list. These logs are saved in the C:\DAD\LOGS directory and follow the format;  "RIyymmdd.log" and can be opened and viewed using any text editor.    Each Record log lists:

    • The date and time a recording event was completed.

    • The date and time a recording event was aborted.

    In the example shown, one can see the cut number with information that it completed it’s recording process. The record deck is listed along with the length of the time for the completed cut.  

     

    Text Box:

     

    Debug Log

    A debug log is very useful in many aspects. These logs are commonly used by ENCO Tech Support.

    The debug log can be enabled from either the DADnet or DADlocal.BAT file, or it can be entered into the workstations environment variables.

    To enable the log from the BAT file, near the top of the file, add the line:

    @SET DEBUG=<any filename.txt>

    To enable the log from workstation environment variables, add a new variable:

    DEBUG with the value being <any filename.txt>.

    This log is saved in the C:\DAD directory with the name you have set for the log.  The debug log will list:

    • The date and time a DCL event was executed.

    • The time it to audio to begin to play.

    • Database information and errors.

    In this example, the time to begin play is shown for five audio cuts. Different DCL’s are also listed.

    DAD will close the Debug log at midnight and save the file as with the filename with the date. 

     

     

     

    Transaction Logging [TransLog or CutsLog] 

    DAD has the ability to track all changes made to the database. The CUTSLOG.DBF file is a database format and is kept in the \DAD\LOGS directory. 

    To enable this log, create a simple file called: TRANSLOG.YES in the \DAD\FILES directory. 

    NOTE: This log can become quite large very quickly. If a user enables a Transaction log they should either check the log size often or disable the logging when not in use

    The contents of the file are:

    DATETIME = Timestamp.
    WORKSTATION = Workstation name making the changes.
    USERNAME = Current user loaded on workstation.
    RECNO = Record number in the cuts database.
    CODEID = Code identifier for reason of change

    the following are data fields copied from the cuts database
    CUT, STARTTIME, ENDTIME, SECTIME, TERTIME, FADEIN, FADEOUT, STARTTALK, ENDTALK, SEGUELEN, SEGUESTART, HOOKSTART and HOOKEND. 

    This list of codes and their corresponding descriptions that are used in DAD’s cuts.dbf transaction logging:


    [Note: this list is not complete, some users might find codes that are not listed below]

    1161 – 1166 editor updates
    165 - rewrite audio to another cut (or DCL Copy Cut)
    1166 - rewrite audio to same cut
    1162 - save
    1163 - del edl 

    1111-1114 – library modify updates
        1111 - add cut via Library ADD
        1112 - saving within modify
        1113 - changed cut number within modify
    1182 - copy cut from modify screen

    1502 – playback machine update

    1061-1066 – record machine updates
        1066 - Creation of cut in database (by Tracker/Segue Edit/rec deck)
        1063 - Cut accepted into record deck and recorded [should always be with 1061 & 1062] 
        1061 - Cut begins recording [should always be with 1063 & 1062] 
        1062 - stop recording [should always be with 1063 & 1061]

    1091 - marked for delete & purge
    1302 - played from within DAD someplace (# of plays update)
    8001 - Modify Lib Database info via DCL 'Modify Cut'
    9992 - Generated when a cut exists within the database now and is 'overwritten'
    9995 - Cut removed via DCL Delete Cut
    RBLD - Rebuild