Broadcast Tools ADMS 44.22 Manual de servicio descargar pdf (Pagina 187)

Reference 187

2. In our example, your Action to resume normal programming will include a second Remap Input

Relays task which restores the default input relay mapping to the switcher.

Now, we're ready to join the special program when the program start is signaled by the provider. When

program start is signaled, the Action created in step 4 above will be executed. The program's audio

channel will be opened on the switcher and all normal relay closures will be inactive and just the

special event relay closures will be responded to by XStudio.

Revising the Log

The main difference between normal programming and special event programming is how the log is

constructed. Special events like sports broadcasts present a challenge in automated execution

because the timing of commercial breaks is not predictable. The timing of local breaks is dictated by

the flow of the game and they could occur at intermittent intervals. However, most events of this kind

do have a fixed number of breaks that will be taken during the course of the event and the breaks will

occur in order.

In order to tell XStudio that breaks are not time-sensitive, we use time approximate load directives for

the in-event commercial breaks, as shown in our example log.

Special Event Log with Time Approximate Directives

In our example, the special event begins at 4:00 PM. The log has a standard load directive at that time,

so at 4:00 PM, the first break of the special program becomes the "active" directive (active break). At

this point, we will have received the start event signal from the programming service and the program

is one the air. XStudio is positioned on the log for the first break and is awaiting the break relay closure.

You'll notice the next 3 directives on the log are time approximate directives and that the first of them is

marked as the "NxtA" (next time approximate) directive. The 5:00 PM directive is a standard load

directive - it's at that time we'll be returning to normal programming in our example.

When the first break is called for by the program provider, the 4:00 PM break in our example is played.

At that point, XStudio marks the 4:10 PM time approximate directive as the "active" directive - meaning

it will be the break played when the next relay closure for a break arrives. Unlike normal programming

using standard load directives, though, XStudio "locks" onto this directive and will not move from it until

the break plays. This means the break could com as late as 4:25 PM and unlike normal programming,

the "locked" break will play even though there's a directive at 4:20 PM. In effect, once XStudio starts

processing time approximate directives, the breaks are now played sequentially without regard for the

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

Sin comentarios

Broadcast Tools ADMS 44.22 Manual de servicio Pagina 187