How Rivendell structures a log.
In Rivendell, a log is a chronological sequence of events, what other systems call a playlist. Each log belongs to exactly one service, which governs where it can play and where reconciliation data goes. RDLogEdit shows Music, Traffic, and Tracks readiness indicators so an operator can see whether a log is ready for air.
Logs come from Rivendell's own scheduler, built from events, clocks, and a weekly grid in RDLogManager, or from external music and traffic schedulers.
How Rivendell voicetracks.
Rivendell places voicetracks in a special voicetrack cart that the VoiceTracker creates and manages automatically. Before tracking a service, an administrator configures a voicetracker group and a pool of cart numbers in RDAdmin. Track markers act as placeholders in the log and can be inserted from RDLogEdit, RDLogManager events, or data from external schedulers.
The VoiceTracker, available in RDLogEdit and RDAirPlay, shows waveform panes for the previous event, the track, and the next event, so transitions can be auditioned and adjusted in context.
Where RoboJock fits.
RoboJock reads the log, writes each break for its window, and voices it with a voice trained on a real radio professional's voicetracks. After your team approves it, the break is delivered with its metadata into the group and cart range you choose.
Your team can still open the VoiceTracker and fine-tune every transition. Nothing about Rivendell's open, inspectable workflow has to change.
- Choose the Rivendell service, group, and cart range for delivered breaks.
- Confirm whether track markers come from RDLogManager or an external scheduler.
- Check that the Tracks indicator reads ready after delivery.
- Audition transitions in the VoiceTracker for a full pilot hour.
Sources
- Rivendell Operations Guide: Generating and maintaining logs
- Rivendell Operations Guide: VoiceTracking
- Rivendell Operations Guide: Using the Voicetrack Interface
- Rivendell Wiki: Log Creation
Product names belong to their owners. Feature descriptions come from each vendor's published material; confirm details for your version with your vendor.