Configuring VisTool for on-air talent control
A radio presenter should be able to identify the live item, bring up the next source and recover from a wrong cue without hunting through menus. The touchscreen is part of that chain, not merely a display for the console.
A useful VisTool layout therefore starts with decisions rather than features. It puts routine actions within reach, protects consequential controls and makes status readable at a glance, even when a producer is speaking and the studio is busy.
VisTool software forms part of a wider broadcast workflow. Understanding where the workstation sits among routing, audio processing, automation and playout helps prevent a tidy screen from hiding an unreliable signal path.
Changes should be prepared away from transmission, tested with the actual programme material and checked by the person who will use them. This approach keeps touch operation predictable and leaves little room for accidental activation during a live cross.
Map the presenter’s decisions
Start with a shift’s rundown, then list the actions a presenter may need: select a microphone, hear a source, acknowledge a caller, launch a recorded item or move to a commercial break. These actions form the skeleton of the layout; every additional control should earn its place.
Keep critical functions together, but keep frequently used items apart from consequential ones. Lawo’s broadcast ecosystem provides useful context for how VisTool sits alongside Ruby consoles, Power Core nodes and other studio components.
Design a clear main screen
Divide the working area into current programme, next cue, source controls and monitoring. The current item should dominate, while the next item remains visible enough to prepare before the presenter speaks its cue.
Use text and colour together to distinguish live, ready and unavailable states. Red, amber and grey can reinforce labels, but colour alone is insufficient for colour-vision differences or glare. Include a clearly identified clock with its time zone when a networked show crosses states.
Separate routine and exceptional actions
A main page should handle the repeated sequence of a show: introduction, interview, music bed, traffic bulletin, advertisement and return to the presenter. Less common routing or extended monitoring controls belong on a separate view, reducing the chance of a stray touch.
Give sensitive actions deliberate protection. Where VisTool supports confirmation, use it for operations that could interrupt programme audio; otherwise keep them on a secondary page and provide unmistakable feedback after execution.
Comparing the main layout regions clarifies what deserves permanent space:
| Layout area | Presenter need | Placement | Key distinction |
|---|---|---|---|
| Current programme | Know what is live | Main screen | Keep it visually dominant |
| Next cue | Prepare the following item | Main screen | Show order, not just a source name |
| Source selection | Change mic, phone or playback | Main screen | Show actual route and status |
| Extended routing | Reach occasional destinations | Secondary screen | Separate it from routine controls |
This prioritisation makes the screen easier to scan while preserving access to specialist functions.
Connect controls to the studio
A polished layout cannot compensate for incorrect routing or delayed status. Confirm that each touch action changes the intended source and that feedback reflects reality. On larger installations, Power Core network scaling explains the capacity considerations behind shared audio infrastructure.
For a national network, a presenter in Brisbane may be working with content heard in Sydney and stations across regional New South Wales and Queensland. Label sources by role and origin, and avoid controls whose meaning depends on being in one particular studio.
Test controls before transmission
Test the complete path, not just the interface: select the source, confirm the route, listen for the expected signal and verify that unrelated feeds remain unaffected. Repeat important actions at normal pace and under time pressure, including at the end of a busy programme segment.
A plant precommissioning checklist for instrumentation loops offers a useful parallel: prove the signal before depending on it. The wording differs, but the broadcast principle is the same.
Account for Australian schedules
Australian commercial radio has well-known Now and Next conventions, with operating requirements governed by the Australian Communications and Media Network codes. Make the station identification and scheduled item easy to verify, while keeping automated announcements distinct from presenter-led cues.
Time handling needs particular care. New South Wales and Victoria shift between AEST and AEDT on the first Sunday in October and April. South Australia and Tasmania follow those dates, while Queensland and Western Australia remain on standard time. Store networked schedules with explicit time-zone rules and test them around these transitions.
A practical traffic bulletin, local advertisement or pre-recorded promo should have its own readable status. The presenter should know whether it is queued, playing, failed or finished, rather than relying on an indistinct stop button to tell them.
Keep the layout under control
Give each studio a named configuration and keep a copy of the approved version. Record what each page contains, restrict editing during live shifts and rehearse changes with the same source types used by the show. Shared patterns are useful across metropolitan and regional stations, but local destinations should remain clearly identified.
The layout to remember is a working map of the show: current programme prominent, next cue visible, critical actions protected and every change verified before air. A dependable touchscreen does not need to display everything; it must make the right action obvious and keep the broadcast under control.
