How Zetta thinks about a voicetrack.

Zetta's Voice Tracker shows a break in context: the previous asset on the first track, the voicetrack in the middle, and the following asset as the tail. RCS notes that talent can voice track any transition in the log, not only the ones holding an empty voicetrack position, because every asset and log transition is identified by a unique ID.

The tools around that view are about finishing the segue, not just recording audio. RCS documents Auto-Ducking, Trim In and Trim Out, volume points, and single or multi-track audio edits. It also warns that editing a voicetrack edits the transition, so heads and tails need to be reset in the Log's segue editor.

Where RoboJock fits.

RoboJock starts from the same log your team built and writes each break for its real window: the outgoing record, the incoming intro, and what sits around it. The read comes from a voice trained on a real radio professional's voicetracks, then it goes to your team for review before it is delivered.

The finished break is delivered as broadcast audio with the identifying details your import needs, such as a cart or asset reference, the log position, and segue information. It lands in Zetta as an asset your team can audition, trim, and adjust with the same Voice Tracker and segue tools they use today.

Remote and multi-station Zetta workflows.

Zetta2GO is a browser-based Zetta service, not a separate app, and RCS advises securing it with a VPN and Zetta credentials. Since Zetta 5.21.1, its Voice Track module mirrors Zetta's own, including Trim In, Trim Out, and volume points. That makes it a practical place for a program director to check RoboJock breaks from outside the building.

For groups, RCS describes ZCast as sharing audio assets, logs, and voicetracks with heads and tails, segue transitions, and splits between sites. Shared delivery is useful, but each station's clock and local references still need their own approval.

PILOT CHECKLIST
  1. Confirm which Zetta stations, logs, and dayparts RoboJock should write for.
  2. Agree on the asset naming and category convention for delivered breaks.
  3. Decide who reviews breaks, and whether review happens in RoboJock, Zetta, or Zetta2GO.
  4. Test one hour end to end, including heads, tails, and a segue reset after any edit.

Sources

Product names belong to their owners. Feature descriptions come from each vendor's published material; confirm details for your version with your vendor.

Book a demo for your RCS Zetta station