Configure RƎLAY Hot Key for Instant Station ID Stingers
An identification sting may last only a few seconds, yet it has to land cleanly between a presenter’s links, an advertisement and the next song. RƎLAY’s Hot Key gives the operator a direct route to that cue, replacing a hunt through automation menus with one deliberate action. The useful result is not merely speed: it is consistent handling of a station ID when the studio is busy.
That pressure is familiar in Sydney and Melbourne, where tightly sold drive-time breaks leave little room for hesitation, and at many regional stations where a small crew may support several sites remotely. A configurable trigger helps a presenter move from a handover cue to the station identification without losing rhythm or reaching for the wrong item.
RƎLAY sits within Lawo’s Broadcast 3.0 ecosystem, where virtual radio tools, studio software and networked audio infrastructure support shared operational goals. Connect the Hot Key to an established playout workflow and document who owns the action during normal operation and failover.
The configuration should answer three questions: which event plays the sting, where that event is audible, and what happens if the key is pressed again. It should also leave emergency-alert, talkback and mute controls unmistakably separate. Those boundaries matter in metropolitan and regional studios, where technical support and staffing levels differ sharply.
Assign the ID to a known playback path
Start by tracing the station’s existing ID route. Identify the playout event, the audio destination, the processing stage and any monitoring split between FM, DAB+ and streaming. Map the Hot Key to the established station-ID play command, using a clearly named event when the automation system supports one. This avoids assigning the key to a generic live-input or mixer action that could behave differently under load.
Give the cue one authoritative source and one approved output. Whether the chain runs through Power Core, a local workstation or an external playout system, confirm the actual signal path rather than inferring it from the screen. Lawo’s dual-controller Ruby setup offers relevant context for deciding which controller owns the action when a studio has a failover path.
Configure the key and its behaviour
Choose a key that is easy to reach without being adjacent to high-risk controls. An unmodified letter or function key may suit an operator’s dedicated keyboard, while a modifier combination can reduce accidental activation. Test the selection in the actual workstation profile, since another application may already claim it.
Set the action to start playback rather than toggle an on/off state, where those choices are available. Repeated presses should not queue duplicate ID stings, and a held key should not create several overlapping copies. Decide whether the key plays only the ID or a complete identification package containing music, speech and the programme bed beneath it.
Integration with the wider automation system determines how much feedback the operator receives. Lawo’s guidance on integrating VisTool Studio with existing radio automation helps teams connect control events and status information. Verify the trigger name, playback acknowledgement and stop behaviour so that a visible button state always matches what listeners hear.
Match the trigger to the broadcast
A capital-city network may need a crisp, repeatable sting for every break, while a regional broadcaster may use a longer spoken or sponsored identification. The trigger should suit the approved format and the person operating it, not impose a keyboard habit that only works in one studio. Keep separate cues where different IDs or campaign versions must remain distinguishable.
The cue determines what the key should initiate:
| Cue type | Best use | Hot Key action | Main check |
|---|---|---|---|
| Network ID sting | Routine station branding | Start one short event | Duplicate audio on DAB+ or streaming feeds |
| Spoken or sponsored ID | Local campaign or regional announcement | Play the complete cue | Approved wording and break timing |
| Event bed | Music-led identification package | Start the full package | Backing-track overlap and programme continuity |
| Emergency alert | Public-safety messaging | Use the authorised alert workflow separately | Never assign it to a routine ID key |
The comparison is about operational boundaries as much as convenience. One short key action works well for a fixed sting; it is less suitable when a presenter must choose wording, length or sponsorship details. Keep those decisions in the programming or advertising workflow unless the RƎLAY configuration explicitly supports safe selection.
Protect the on-air signal
Test the assigned cue off air on headphones and meters. Listen for level changes, confirm the start point and verify that the processing chain receives the ID at the intended level. Then check the return to programme audio, especially if the sting includes a longer bed or the station is running simultaneous FM, DAB+ and online feeds.
Australian operators must also keep playback within the station’s approved identification format. ACMA licence conditions under the Broadcasting Services Act 1992, together with the Commercial Radio Codes of Practice for commercial stations, govern broadcast content and announcements; a Hot Key cannot replace legal or advertising sign-off. Record any required spoken wording separately rather than treating an imported sting as a complete legal announcement.
Emergency-alert arrangements are another boundary. Australia’s CAP-based emergency-alert workflows and a station’s own alerting procedures must remain distinct from ordinary station-ID playback. Assigning routine identification to a production shortcut is convenient, but mixing it with protective infrastructure could create confusion during an incident. A visible cue label and a separate control location provide a simple safeguard.
Make the shortcut part of the runbook
A Hot Key becomes dependable when the operator, producer and engineer use the same name for the event and agree on what a successful press looks like. Put the key, cue name and playback destination in the studio runbook, alongside a manual fallback for use if the shortcut or workstation fails. Record the expected behaviour of each networked site.
During commissioning, test the cue from the production position, not only from the engineering console. Repeat the action at different programme transitions and under a deliberately busy monitoring mix. Record any mismatch between the on-screen state and the audible result before the setup enters routine use.
At the next roster change, the duty engineer and producer will complete a fifteen-minute off-air rehearsal and record the approved key, cue name and playback destination in the station log.
