
In all cases, a new log is initially generated by touching the Create New Log button. If the
log for the selected date and service does not already exist, it will be created at this point
(becoming visible in RDLogEdit). It the log already exists, it will be overwritten.
(NOTE: if completed voicetracks exist in the old log, they will be deleted when the log is
overwritten!)
When generating a log, RDLogManager will look for possible problems (such as
scheduled carts that are missing in the Library) and generate an exception report if it
finds any.
Once generated, the status lights in the Generate Log dialog indicate which (if any)
additional import data are needed to complete the log. Two types of status light exist:
Available, which indicates if the required data file is available to RDLogManager, and
Merged, indicating whether the data has been merged into the log as yet. Each light can
show one of three different colors: GREEN, meaning “yes”, RED, meaning “no” and
WHITE, meaning “not required”.
For an example, see Illustration 53. This is showing a log that has been generated and
has music data available but not yet merged. To perform the merge, touch the Merge
Music button. The dialog now changes to that shown in Illustration 54, indicating that
Music data has been merged but that traffic data is still needed. Once a log has reached
this state – that of having any necessary music data merged – it can be voicetracked
without having to wait for traffic data to become available. Traffic data can be merged at
any time before, during or after the generation of voicetracks. The actual traffic merge is
performed by touching the Merge Traffic button, resulting in a dialog like that shown in
Illustration 55. (NOTE: the configuration of the various data file names and parser
Illustration 52: The Generate Log Dialog
Comentários a estes Manuais