Broadcast Tools ADMS 44.22 Wartungshandbuch PDF herunterladen (Seite 185)

Reference 185

mode, XStudio will not cross over a log directive to continue playing, so only the audio items

on the log between the active directive and the next one on the log are played. During this

time, the Action is waiting until the break length time expires.

At 3 minutes since the audio playback started (based on our example break length), the last

task in the Action task list is executed, updating the audio switcher to restore the satellite

programming service channel back on the air.

If a break on the log is empty (contains no audio items), no wait time for the

break is communicated to the running Action and the next task in the list is

executed immediately. In our example, this would mean that the satellite

programming service audio channel on the switcher would be turned off, then

back on within just a few milliseconds. The effect from a listener point of view is

that the programming service stayed on the air.

Because the local break length is controlled by the log, only one Action needed to be defined for our

example, even though example format clock we used had different lengths for each break. As long as

the log directive for each break had the correct length, we can use the same Action for all breaks in all

hours, which simplifies programming for satellite automation.

Getting Things Started

When you are running satellite automation exclusively (as in our example), once you have produced a

working daily log and set up the needed Actions, there's nothing to do to get the ball rolling as all

activity is controlled by the satellite programming service.

In our example, XStudio starts up in Satellite mode and loads the daily log. So, when XStudio has

completed its startup process, the correct log is loaded and the operating mode is correct. From there,

it's a matter of waiting for the programming service to signal what it wants done.

Suspending Satellite Automation Manually

In our example, the radio station is running satellite automation 24 hours a day, 7 days a week. But

what if we want to prevent XStudio from handling the Actions we have programmed for a period of

time, say to run a 4-hour live show? In our example - and in many other cases - it's a simple process.

You can suspend automatic response to the program service signals by simply changing the XStudio

operating mode to something other than Satellite. Use the main menu item Options | Operation Mode

and select a different mode, like Live mode.

As soon as the mode is changed to something other than Satellite, the Actions we created will behave

differently. For instance, if the Return Liner signal arrives from the programming service, XStudio will

locate the Action named "CRM Return Liner" and begin executing its list of tasks, as before. However,

since every Task in the list is valid only during Satellite mode, each task is ignored. Thus, no switcher

update occurs and XStudio does not play the cart RL01 (the two tasks in the Action).

XStudio does make note of receipt of the signal from the programming service in the application event

log and adds a record to the daily audit report data file.

When the live show is done, use the main menu Options | Operation Mode to select Satellite mode.

XStudio will again process signals from the program service as normal.

5.7.1.1 Satellite Programming - Special Events

Special events programming while operating in Satellite mode might include satellite-delivered sports

broadcasts, music specials like count-down shows or any other satellite-delivered programming that

varies from normal operations. This example assumes you are familiar with and have constructed all

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

Kommentare zu diesen Handbüchern

Keine Kommentare

Broadcast Tools ADMS 44.22 Wartungshandbuch Seite 185

Kommentare zu diesen Handbüchern