• US: +1-800-476-7226

Software and services for the radio industry.

Automation System: Enco

Modified: 2017/05/17 11:09 by EricCrocker - Uncategorized
Edit

Enco

back

WORK IN PROGRESS - Please understand that we are actively rewriting much of our documentation and this page is currently "under construction"; if there's anything that you'd like to see added to and/or expanded upon, please let us know by sending us a smile.

Edit

Introduction

RadioTraffic.com converts to a specific Enco ASCII Flat File log format.

Edit

Station Configuration

To configure RadioTraffic.com to work with Enco DAD, you will first need modify the station configuration to utilize Enco DAD as the automation system. In the administration module, open 'Stations'. Select the station you want to configure and double click. Once the station configuration is visible, select the 'Files' tab. Select the 'Product' to Enco DAD using the drop down selection tool. The 'Automation Log Path' is where RadioTraffic.com will export the log to, so set this to the file system folder that Enco DAD will pull the file from. The 'Station Identifier' will need to match the 'station number' described in the Enco DAD User Manual (which is a number from 0 to 9).

By default, RT sets the 'transition' code to an A. If you have a need to change this, you can use the 'Station Identifier' field to do so by adding an optional pipe delimited value containing the transition code you wish to use. For example, if you have a station number of 1 and want the transition code to be an S, you'd type in 1|S.

The exported file name will look something like mmddyyTs.LOG where mm is month, dd is day, yy is last two digits of year and s is the station number.

Edit

Cart Numbers

Enco DAD system can use cart number from 00001 to 99999.

Edit

Automation Commands

RadioTraffic.com automation commands map directly to various Enco DAD playlist event types. Most commands require a function definition (A, S, L, N) and optionally support additional parameters delimited by the pipe symbol (|).

Edit

Chain Events

There are two types of Chain Events available in Enco DAD, the Chain and the Smart Chain. To create these in RadioTraffic.com, you'll need to enter:

Cart #: CHAIN
Command: A, S, L{|{*}{8 characters}}

The usage of the asterisk (*) will automatically use tomorrows date when determining the playlist to load. Otherwise, you can define the playlist directly.

Edit

Delay Event

Cart #: DELAY
Command: A or L{|delay}

Delay is the amount of time in seconds to perform the delay. If not provided, a value of 0 will be assumed.

Edit

Timed Event / Branches

Cart #: TIMED, HARD, HARD2, HARDALL, SOFT, SOFT2, SOFTLMT
Command: A or L{|delay}

The cart numbers map to type of events defined within the Enco DAD user manual. Each variant maps as follows:

TIMED - Timed Event
HARD - Basic Hard Branch
HARD2 - Forward Hard Branch
HARDALL - Basic Hard Brach 'All Hours'
SOFT - Basic Soft Branch
SOFT2 - Forward Soft Branch
SOFTLMT - Basic Soft Branch with a 'limit' of delay seconds.

The delay parameter is only used with the SOFTLMT type of branch.

Edit

Command/Rotate/Playlist Cut

Cart #: 6 digits
Command: A, L, S or N

Command/Rotate/Playlist cuts allows you to play an audio file (or other "event") directly without the scheduling subsystem. Examples may include liners, jingles, macros, rotations, etc. Not all "commands" are available to all types of cuts; please review the Enco DAD user manual for further details.

Edit

Other

At this time, the above are the officially supported event types. If you need others that are not currently implemented, please contact customer service with details and we'll be happy to add them.

Edit

Log Notes

Log Notes automatically export as Enco DAD "comments".

Edit

Programs

Programs currently export as "comments".

Edit

Avails/Breaks

Avail markers do not export to the Enco DAD export and are used strictly inside of RadioTraffic.com as a means of scheduling.

Edit

Log Reconciliation

The filename that RadioTraffic.com is looking for when executing matches the {id}MMDDYY.DBF pattern. The identifier portion needs to match the station number that is configured for the log export in order for automatic portion of the reconciliation to be able to match upon.

The as-play database file is created daily with a file name of {id}MMDDYY.DBF. The user value is defined via an ASPLAY Environment (or Launch (batch file) settings) variable. For the purposes of automatic reconcilation, this value needs to match the 'station number' described in the Enco DAD User Manual (which is a number from 0 to 9).

In order to successfully reconcile items coming back from the automation system, the criteria has to be resolved:

  • The value in the "cut" column has to match the cart number exported by RT.
  • The value in the "group" column has to match the "category" configured for the cart number exported by RT.
  • The value in the "wasplayed" column has to contain a "T". This value identifies that the spot did, in fact, successfully air.
  • Rotations exported and executed in the Enco automation system are fully supported.

Edit

FAQ

TODO Add any questions as they come up to this section.

Edit

Additional Information

For additional documentation concerning working with playlists/ASPLAY files in the DAD system, please refer to the Enco on the subject: