Broadcast Tools ADMS 44.22 Wartungshandbuch PDF herunterladen (Seite 183)

Reference 183

only (uncheck all others). Save ([Apply]) the task. This task will be used to signal XStudio to

play the audio items on the log that correspond to the break.

3. Create a new Update Switcher Task. Name the task "CRM Return to Sat". In the Updated

Switcher dialog, select the correct audio switcher. Turn row 1, channel 1 "On" (the

programming service channel). Change the Valid Modes option to be Satellite mode only

(uncheck all others). Save ([Apply]) the task. This task will be used to put the satellite

programming service audio back on the air after completion of the local commercial break.

Notice that for our example we didn't change the status of any other switcher input

channels.

4. Create a new Action. Name the action "CRM Commercial Break". Drag the tasks "CRM Local

Breakaway", "Play Local Break" and "CRM Return to Sat" into the Action Task List from the

available tasks table, in order. XStudio executes tasks in an Action in the list order, so we want

to be sure that only the XStudio playback channel is on the air, play the commercial break audio

and finally, switch the satellite programming service back on the air.

5. Assign the new "CRM Commercial Break" Action to the corresponding Relay Input on the audio

switcher. This in effect "connects" the Action to the satellite service's closure.

You've probably figured out by now that when XStudio executes an Action, it performs the Tasks in the

list in order, one right after the other, until all Tasks in the list have been performed. You might be

wondering how we get XStudio to wait long enough for all the commercials to play before switching

back to the satellite programming service in this example.

The answer lies in the broadcast log construction and how XStudio handles a Start Play task when the

task calls for playing audio from the log and the current operating mode is Satellite. Essentially,

XStudio uses the log to communicate to the running Action the length of the commercial break and the

Action automatically waits that long before performing the final Task in our example.

Commercial Break Log Format

The broadcast log (program schedule) has to be structured in such a way that at the time the satellite

program service sends a signal for the local commercial break, XStudio knows which set of

commercials (audio items) to play and the required length of the break. Additionally, the log determines

whether or not XStudio actually plays a break or, because there are no commercials to play, in effect

skips the break altogether, keeping the satellite program service on the air.

The key log element in all of this is the Log Directive. Specifically in our example, a Load Required

directive is used. In our sample clock, there are a number of local breaks. We will focus on the break

that the format clock indicates will occur at 20 minutes past the hour. Here's what needs to be done for

20-past local commercial break:

1. Position the Load Required directive on the log. Most satellite programming services do

not signal all local breaks at the specific time listed on the format clock. Instead, they are

taken within a "window" of time, typically within plus or minus 5 minutes of the target time. In

our example, this means the earliest the service will signal the break is 15 minutes past the

hour, the latest would be 25 minutes past the hour. So, our Load Required directive needs

to be placed at 14 minutes past the hour, one minute in advance of the earliest time the

break will be signaled. When the PC clock hits 14-past, XStudio will mark the directive as

"active", meaning that from that time forward (until another log directive becomes active),

when the program service signals a break, it is the content associated with this directive that

will be played.

2. Set the break length. The Load Required directive has a field for entry for the length of the

break. In our example, the 20-past break is 3 minutes (3:00).

3. Fill the break with audio content. Basically, this means that you need to have items on the

log immediately following the Load Required directive that add up to 3 minutes worth of

playback time. All audio items on the log, beginning with the Load Required directive and

1 2 ... 178 179 180 181 182 183 184 185 186 187 188 ... 361 362

Kommentare zu diesen Handbüchern

Keine Kommentare

Broadcast Tools ADMS 44.22 Wartungshandbuch Seite 183

Kommentare zu diesen Handbüchern