Satellite
Automation Overview
The
following is a general explanation of programming for automation. All cut
numbers are used as examples.
When
you are planning to automate with a satellite, you should have all proper
information from the provider. This includes all possible relay information,
pinouts along with format clocks and concept of how this will ‘sound’ on the
station.
The
components involved in an automated system are:
Satellite
Receiver, DAD workstation, Audio Switcher, GPI Relay Interface and daily
playlists. The daily playlists include Traffic and possibly music with
Scheduling Wizard performing the log integration.
Relay
Control
Basic
control will come from the provider. This is done via relays.
The
DAD computer is going to want to see contact closures not tones. If the
provider is sending tones (25KHz) then you will need to get a tone decoder.
These
closures will be wired from the satellite receiver to the GPI card. For example:
Wire the Legal ID relay from the receiver to a relay of your choice on the GPI
card. This relay will need between 5 and 24 volts.
Once
you have wired your relays you will need to modify your GPI file. In DAD then you can edit the file from the Setup > Readme > GPI file. This file
will have that workstation's name followed by the GPI extension. (onair.gpi
etc..) The number of lines in this file is equal to the number of relays for
your GPI card. There are 8 lines for a GPI 8 card and 16 lines for a GPI 16
card. The first line is equal to the first relay of the card. Each line will
have a set of quote marks. ("") Use these quotes even if the relay is
not currently being used. All lines will open with a quote and close with a
quote mark.
For
a test you can have the 1st line in the GPI file say something to the
extent of: "execute 00050". This will execute the command cut number
00050. In the library you would have cut 00050. This command cut will have the
programming of what you want to do. For a test enter the DCL: ALERT 'this is a
test'
Now
whenever that relay is triggered then the alert popup will be displayed.
If
the station has the Legal ID assigned to a Priority Play button, the GPI file
could be set as follows:
“execute
00100 : play P_Play1”
In
this example, cut number 00100 is a Switcher Command cut turning the DAD audio
crosspoint ‘on’ and playing the Priority Play button. The Switcher Command
cut and it’s associated serial string can be written to add the DAD audio
crosspoint for a set amount of time then turn it off. This same concept can be
used for all liners sent by the provider.
Audio
cuts like liners and ID’s can be played from various places. These can include
the Priority Play and Array buttons along with machines like the Quad deck.
Switcher Control
A
switcher allows on to select various network sources and route them to the
on-air signal. Knowledge of how to
control the switcher is an important part of setting up automation. Configuring
the switcher is not covered within this document but is covered in the Switcher
Control document.
All
stations will be performing basic operations of switcher control such as turning
the network feed on and off. Many
stations can also perform more complicated switching tasks. These might include
the ability to simultaneously route audio out one output for an on-air signal
while at the same time routing audio out the second output for Timed Records or
other audio production.
Network Clocks and Playlists
The
traffic system will generate the daily log, which can be imported into DAD.
A custom import filter can be written to import the traffic log or
general user configurable programs like Scheduling Wizard [SchedWiz] can be used
to import the traffic log.
If
Scheduling Wizard is to be used, one will recreate the network clock adding any
station specific events to the clock. These events could be network news as the
top of the hour; special long form shows that are programmed to play thought the
day and general insertion of traffic.
The
traffic log will need to match what the satellite provider is doing. If the
network takes a break at 18 minutes after the hour then you will need to have
the traffic log have a break at 18 after the hour.
This becomes important in SchedWiz as the position of the break within
the clock will determine what time it should import traffic data from the
traffic log.
In
the general sense, the provider is going to send a relay for a stopset. You
might want the computer to perform several steps when it receives this relay.
For example, you might want it to turn the switcher crosspoint for the network
‘off’ and turn the crosspoint for the audio from DAD ‘on’. At the
same time it will play the commercials until it reaches the end of its stopset
and return back to the network.
To
do this you would have the GPI file programmed to perform a function.
These commands can be programmed on the GPI line directly or enclosed
within a command cut. For example: execute 00049. Cut 00049 in the library will
hold the following DCL's.
PLAY
PBK1
Also
this cut would have in its Switcher Field the name of the switcher command. For
example: DAD or TAKE 2. This will turn the switcher off of the satellite network
and turn on the proper crosspoint for the DAD computer. The commercials will now
play. When the stopset is done there must be a command to return the switcher to
the network. This command cut will be the very last element in the spot break.
This command cut will also have an AUTOLOAD transition. This return to network
cut would be programmed like the following.
#00051
Again,
in the switcher field you will have the name of the switcher command.
When this cut is played in the playback deck at the end of a break, it
will switch the switcher back to the network source.
You
will have a return to network cut in every break that the provider has. They
will send the break weather you have commercials or not. When the stopset relay
is triggered, it will play the playback deck and return to the network.