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

Reference 119

The keyword side (XSA=) can be upper or lowercase (or a mixture), but must be exactly those 3

characters followed by the equals sign.

When you have completed your edits, save the changes. In the example shown, you'd click on the

[Commit Changes] button.

How do embedded Actions work?

The inner workings of Actions embedded in carts are fairly straightforward. When this feature is

enabled and XStudio signals the audio engine to play a cart, the audio engine looks at the cart

information to determine if there is an embedded Action. If the keyword "XSA=" is found, the 4 digits

following the keyword are extracted and the audio engine signals XStudio to perform the Action,

passing the 4-digit ID value. This special signal is sent a few milliseconds before actual start of

playback. The audio engine then begins playing the cart as normal.

When XStudio receives notification to execute the Action, the same things that are done with all Action

execution are done - XStudio tries to find the Action and if so, starts execution. If the Action is not

found, that fact is logged to the event log and nothing happens. Within the Action itself, all normal

execution rules apply, including any restrictions placed tasks relating to mode of operation, time of day

and day of week. In other words, executing an Action in this way behaves the same as an Action

initiated by any of the other available methods. The only thing that's different is that XStudio double-

checks the ID value it receives to make sure it evaluates to a number. This is done to catch situations

where you might have inadvertently entered the wrong information or somehow managed to create the

keyword (XSA=) when entering a normal cart description.

While not important to the actual Action execution, the length and audio content

of the cart should be considered. If, for instance, XStudio is being used as

network programming originator and needs to signal affiliates for a local break,

it may be that the audio content of the cart could be nothing more than 1

second of silence - enough time to execute the Action, which in this example

would include Send Control Command task to perform the affiliate break signal,

and allow enough time for the affiliate to switch away before XStudio plays the

next cart on the log, which in this example would be the first element of a break.

1 2 ... 114 115 116 117 118 119 120 121 122 123 124 ... 361 362

Sem comentários

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