log was generated.
Next, the list of log events (if any) to be inserted before the data import should be placed
in the PRE-IMPORT CARTS list. For audio or macro carts, these can be simply dragged
and dropped from the Library cart list on the left-hand side of the dialog. Meta events
can be inserted by right-clicking on the list and selecting the desired element. It is also
possible to edit or delete elements and set the transition type of each element through the
right-click menu.
The IMPORT section then defines which (if any) source will be used for importing
external scheduling events into the log. Either Music, Traffic or None can be selected. If
Music or Traffic is selected, then RDLogManager will import any events from those
sources that fall within the start and end times of the event (as supplied by the parent
clock). These start and end times can be further broadened by means of 'slop factors'
entered into the Import carts scheduled controls (this is sometimes necessary to get the
import to work properly with certain external scheduler systems). The transition types to
be used for the first and subsequent imported elements can be specified with the First cart
has a and Imported carts have a controls. If Music has been selected as the import source, it
is also possible to specify the event to use to import traffic breaks embedded in the music
log with the Import inline traffic with the control. (Configuration of the actual parser
parameters for data importation is covered in the Rivendell Technical and Administration
Guide).
Finally, the list of log events (if any) to be inserted after the data import should be placed
in the POST-IMPORT CARTS list. Configuration of the events work very similarly to that
of the PRE-IMPORT CARTS list.
The color of the event (as seen in the Edit Clock dialog) can be set by touching the Color
button. The list of services for which this event is valid can be edited by touching the
Services List button. To save the event without exiting the dialog, touch the Save or Save As
buttons.
Section 7.4 Generating Logs
After all of the appropriate hours have been populated in a service's grid, it's time to start
generating logs. To do this, touch the Generate Logs button in RDLogManager's Main
Menu to open the Generate Log dialog (see Illustration 52).
Depending upon how many external scheduling sources are involved, generating a log
involves one, two or three steps. Before performing any of the steps, it is first necessary
to select the relevant service for which to generate the log (using the Service: control) and
the log date (either by entering the date in the Date: control or by touching the Select
button and picking it off of the calendar).
Comentarios a estos manuales