Next comes a column showing the owning service. Each log is owned by exactly one
service, which determines under what circumstances the log can be played and where
electronic log reconciliation (ELR) data resulting from log playouts is sent (for an
overview of Rivendell services, see section 1.1.3).
Next comes three “status indicator” columns (“MUSIC”, “TRAFFIC” and “TRACKS”)
indicating the log's degree of readiness for air. A red indicator indicates that the
particular data element is required but currently missing, a green indicator indicates an
element is required and present, while a white indicator indicates that an element is not
required. Additionally, the “TRACKS” column contains a pair of numbers indicating
how many completed voice tracks exist in the log versus how many total track markers
exist (the subject of voice tracks and track markers will be covered in more detail below).
When all three of these status indicators show either green or white, the summary status
indicator (at the beginning of the log's entry in the list) will show as a green check mark,
while a red indicator in any of these three fields will show a red ex. (NOTE: because a
log sports a red ex does not indicate that the respective log cannot be played. It is merely
a visual indicator to allow logs to be quickly “eyeballed” for completeness).
Next comes a pair of columns indicating the valid start date and end date for the log.
Finally, there is a column indicating the log's origin –i.e. the place, date and time it was
originally created.
A report that lists the available logs on the system can be generated by touching the Log
Report button.
A new log can be created by touching the Add button and entering a name, or an existing
log inspected and modified by touching its entry on the log list and then touching the Edit
button, resulting in the log being opened in the Edit Log dialog as shown in Illustration
20. The Edit Log dialog consists of three parts: the top section, where much of the
information shown on the log list can be inspected and modified; the middle section,
which shows the list of events comprising the log, and the bottom section, where buttons
for modifying and saving the log are located. Each event in a log can be one of several
different types, indicated by the icon displayed at the start of the line (see Table 6 for a
breakdown of the various icons). The following types of events can be incorporated into
a Rivendell log:
5.0.1 Audio Carts
The first, and usually most common type of log event is an audio cart. As the name
implies, audio carts are Library entries that contain audio material intended for playout.
Audio carts were covered in detail in Chapter Two in the discussion about RDLibrary.
Comentários a estes Manuais