Broadcast Tools ADMS 44.22 Wartungshandbuch PDF herunterladen (Seite 186)

XStudio 3186

the needed elements for your normal satellite programming operations.

The basic changes needed to transition to special event programming from "normal" programming in

Satellite mode and eventually resume normal programming include:

Changing how XStudio responds to relay closures during the time special programming is

airing.

Setting up Actions to handle the special event's join, local commercial break and program

end signals. Depending on the type of program, there may be additional requirements.

Revising the log to reflect the correct number and length of breaks to be used for the special

program.

Revising log directives so that local commercial breaks are handled strictly in sequence

rather than being driven by time.

Restoring normal operations at the conclusion of a special event program.

To make things as simple as possible for this example, the special event

program we'll be working with is just one hour in length. When broadcasting a

football game, for instance, it is likely the event would last up to 3 or more

hours. The principals of setting up and executing the programming are the

same, though. For longer events, there are just more commercial breaks and

other requirements, like joining the game and finishing up the game, are the

same as in our example.

Transitioning to a Special Event Program

When running satellite-delivered programming, there are normally a number of relay closures signaled

by the programming service to do such things as play a liner, play a station ID, and play a commercial

break to name a few. To transition to our example special program, we'll assume that a relay closure

will be used to start the event, signaled by the program provider. If no such signal is available, you

could perform the transition (or join) using a log directive or a scheduled event.

To join the special program, we need to open the correct channel on an audio switcher, disable

response to relay closures for our regular programming, and make active relay closures that will be

used to signal commercial breaks and and the end of the event. Here are the steps for our example:

1. Create an Update Switcher task to open the correct audio channel used for the event.

2. Create a Remap Input Relays task, which has the effect of "unhooking" relay closures you don't

want to respond to during the event and connecting Actions to input relays so you do respond to

the special program's relay closures. See step 5 for information on the special event relay closures

- you may want to create those items ahead of time so you don't have to go back to this task item

and revise it.

3. Create an Action that contains the two tasks described in steps 1 & 2.

4. Attach the Action created in step 3 to the input relay that will start the event. Note that we're

attaching the start event Action to the default switcher input relay mapping. It is done this way since

the default switcher input relay mapping will be in effect when the special event start is signaled.

5. Create any needed Tasks and Actions to handle things that will happen during the special event.

Typically, there would be an Action to perform the breaks and an Action to resume normal

programming at the end of the event as a minimum. You might also have a requirement for a

station ID or audio bumpers. Any Actions that are to be active and signaled by the program service

will need to be attached to the correct input relays in the Remap Input Relays task created in step

1 2 ... 181 182 183 184 185 186 187 188 189 190 191 ... 361 362

Kommentare zu diesen Handbüchern

Keine Kommentare

Broadcast Tools ADMS 44.22 Wartungshandbuch Seite 186

Kommentare zu diesen Handbüchern