Broadcast Tools ADMS 44.22 Manual de Serviço descarregar pdf (Página 188)

XStudio 3188

time.

In our example, for instance, all three of the time approximate breaks could be called in the first 15

minutes of the hour or the last 15 minutes of the hour and all would be performed in sequence.

While all breaks in our example are of the same length, they could be different with no difference in

how XStudio performs them. The key in that case is to match the lengths of the breaks in sequence to

what the program provider will be doing.

Resuming Normal Satellite Programming

In our example, we handled a 1-hour program. You'll see on the example log that at 5:00 PM, we have

a normal load directive (not a time approximate directive). The effect of this directive is that at 5:00 PM,

regardless of where we are in terms of the playback of time approximate breaks, XStudio makes this

directive the "active" directive. In short, our log is back to normal.

The program service sends its program end relay closure at the end of the event. In our example, that

closure comes at 4:59:50. When XStudio detects the closure, it performs the end program Action you

defined earlier, which in our example includes playing a 10-second station ID, a Remap Input Relays

task that restores responsiveness your default relay closures, and an Update Switcher task that puts

our normal program service back on the air.

5.7.2 Local Automation Programming Example

This example shows how to "program" XStudio for local automation. Local automation generally means

that all content to be aired is placed on the broadcast log (schedule) and that XStudio is responsible for

playing the audio from the log without user intervention.

For this example, we'll assume the station is programming a music format that it is locally automated

all hours of the day, seven days a week, and that the XStudio default operating mode is Automation.

You may wish to review the Program Start Options for XStudio, paying particular attention to the

property settings for Mode at Startup, Load Today's Log at Startup, and Play Log on Startup.

We'll also describe how you can suspend local automation to run a live air shift.

Unlike running satellite automation, which was described in another programming example, running

local automation with XStudio does not require use of an audio switcher unless you have special

requirements or are running a mixed format, operating some hours of the day in local automation,

others in satellite automation.

Constructing the Log

The key to running local automation successfully lies in constructing the broadcast log (program

schedule). You can construct a log directly within XStudio or with one of our log editing tools. However,

the most common method of constructing the log is to use a music scheduling system to create the

music portion (plus fixed audio items like jingles, etc.), use a traffic system to create the commercial

portion (commercials, scheduled promo's, etc.) and use our LogMerge utility software to combine or

"merge" the two logs into a finished log that XStudio executes.

For this example, we are going to concentrate on the finished log and what it should contain rather than

the mechanics of putting together the music and commercial logs. The combining or "merging" of the

two dissimilar logs is covered in the LogMerge documentation and is not as complicated as it might

sound. Once you get everything set up for the combining process, it takes very little time on a daily

basis to produce a finished log for XStudio.

Here are some guidelines for a log to be used in local automation:

We recommend that you use the music scheduling system and the log you export from it as

the "master" log, placing everything you need to execute your format on the music log with

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

Comentários a estes Manuais

Sem comentários

Broadcast Tools ADMS 44.22 Manual de Serviço Página 188

Comentários a estes Manuais