Broadcast Tools ADMS 44.22 Wartungshandbuch PDF herunterladen (Seite 334)

XStudio 3334

8.8.7 Generic Log Construction Guidelines

In order for the generic log to be properly executed by the host audio system, certain guidelines need

to be followed in constructing and/or exporting the log. This topic provides basic guidelines intended to

ensure that the generic log executes properly on the host system.

The original specification published by Computer Concepts Corporation,

Lenexa, KS, did not include log construction guidelines. This content is provided

to minimize pitfalls that might be encountered in constructing and/or exporting a

generic log for use by the host audio system.

Each Log Must Contain an ID Record

The first record in the generic log file must be an informational record (ID Record) in order to be

considered valid. If the ID Record is not present, the log will not be processed by the host audio

system.

Audio Items (Spots, Music etc) Must be "Anchored"

When loading the generic log, the host audio system uses non-audio log records as anchor points for

the the audio items. Typically, a Directive record type is used, but Program Title and Log Note records

can also be used. The host system groups the audio items following the anchor as a sequence based

on the anchor item's time value. Consider the following fragment of a generic log file:

...

D0020LR00400 Load Required Brk <== "Anchor Point"

C0020:01T118Get Well Games 00059CM

C0020:02T120DENTYNE/reg or sugarfree 00029CM

D0100LR00300 Load Required Brk <== "Anchor Point"

C0100:01T004DIET COKE/Q:Diet Coke! 00059CM

C0100:02T010VERNE & BUBBA'S DONUT 00049CM

C0100:03T110DoubleTree 00058CM

...

As you can see in the fragment, a Directive is scheduled at 00:20 (12:20 AM). The following audio

items (commercials in this case) have the same starting times in terms of hour and minute (12:20 AM)

and contain a seconds value. The two commercials in the example are "anchored" to the Directive.

The next grouping is at 01:00 (1:00 AM). The host system typically creates "spacing" so the visual

representation of the log appears similar to an original paper log document.

This concept of anchoring is particularly important if the host system is running satellite automation.

The Directive "anchors" have the effect of grouping the breaks (stopsets) for playback when the

programming service signals a local breakaway.

In live programming segments, using one of the record types that serves as a content anchor assists in

making the log visualization on the host system easier to use.

Audio Items (Spots, Music etc) Must be Written in One-Second

Increments

While it may be counterintuitive, audio items following an anchor item in the generic log need to be

incremented by one second for each item following the Directive, Program Title or Log Note. The main

reason for this requirement is to maximize the number of elements a log contains.

Since the generic log structure uses the time values as unique record identifiers, incrementing by one

second increases the number of records that can be contained within the generic log substantially.

Review the generic log file fragment to see how this construction appears in the file:

1 2 ... 329 330 331 332 333 334 335 336 337 338 339 ... 361 362

Kommentare zu diesen Handbüchern

Keine Kommentare

Broadcast Tools ADMS 44.22 Wartungshandbuch Seite 334

Kommentare zu diesen Handbüchern