
Reference 179
© Copyright 2003-2015 C-R Media All Rights Reserved.
These "walk-away" or "automated" times are generally organized in one of two ways:
1. All program content that is to be aired is present on the log and is played by XStudio. This is
commonly referred to as "local automation". In this scenario, XStudio will play log content
from a starting point on the log in a sequential manner. Periodic adjustments for over-
scheduled content may be made, using so-called "hard sync" and "soft sync" methods,
which are driven by the log.
2. Program content - music or talk show content - is delivered to the station via satellite and at
certain times throughout an hour the station is signaled to insert local audio content; typically
commercials, local weather and local news, for a specific amount of time. This means that
the satellite program feed needs to be taken off the air, the correct local content played and
then, the satellite program feed needs to be restored to the air. In addition, the local station
may be called upon to play jingles or liners on-demand based on a signal from the program
service. This is often referred to as "satellite automation." This approach requires XStudio
to respond in a non-sequential, asynchronous way to outside stimuli, typically as a result of
an input relay.
As you might guess, these two scenarios need to be handled quite differently by XStudio, which is one
of the reasons multiple operating modes are available to customize the behavior of XStudio for a
particular type of automated performance.
Perhaps the best way to understand how all the pieces tie together is to look at specific examples.
5.7.1 Satellite Automation Programming Example
This example shows how to "program" XStudio for satellite-delivered programming. It is a simple
example that assumes the station will use a single satellite-delivered programming service all hours of
the day, seven days a week and that the XStudio default operating mode is Satellite. You may wish to
review the Program Start Options for XStudio, paying particular attention to the property settings for
Mode at Startup and Load Today's Log at Startup.
We'll also describe how you can suspend automated programming to run a live air shift.
To program satellite automation for XStudio, there are three jobs to do:
Tell XStudio how and when to play ad hoc audio items when signaled by the programming
service. These items include audio generally described by most programming services as
liners, jingles and station ID's. They can occur at almost any time during a given hour.
Tell XStudio how to handle local commercial breaks. The breaks will be signaled by the
programming service and unlike the ad hoc items, will generally occur within a relatively
small window of time 3 - 4 times per hour.
Create a broadcast log for XStudio that contains the needed instructions (Log Directives)
regarding local breaks, length of the break and the audio items to be played for each break.
If a station is using satellite programming exclusively, the broadcast log is typically created
with a traffic system and exported directly for use with XStudio as the only content the station
needs to put on the log is the local insert material - commercials, promo announcements,
PSA's and the like. The majority of the program content, whether it is music or talk
programming, is supplied by the service provider in real time.
The Program Service Clock
Each satellite programming service will generally provide one or more format clocks that visually
outline in a general way what program elements occur and when, including information about specific
signals sent (closures) by the service for commercial breaks, playback of liners, etc. The example
clock shown is taken from a well-known service, paired down to just the essentials and marked up for
this example.
Comentarios a estos manuales