Centralized clocking for reliable Genlock across studios
A broadcast facility can accumulate separate timing domains: a video reference for playout, an audio clock for mixing, PTP for networked devices and NTP for automation. When those sources drift, Genlock may appear healthy until frame slips, lip-sync errors and inconsistent recording boundaries emerge during a live show.
Broadcast 3.0’s centralised clocking gives these workflows a common timing authority. A facility can distribute disciplined frequency and phase from one controlled source, giving Ruby consoles, Power Core nodes, VisTool software and AutoMix processing a stable relationship to the same reference.
Establishing one timing authority
Centralised clocking is an architectural service, not a single box. It determines which source has authority, distributes frequency and phase, and exposes status to each room. Genlock remains a per-device function, but every generator follows a traceable house reference instead of an unrelated local oscillator.
The Lawo Broadcast ecosystem presents Broadcast 3.0 as a connected workflow across audio, playout, monitoring and control. In that model, a central timing plan links studio hardware with software services, allowing live programme material to share one predictable frame and sample relationship.
Designing the reference hierarchy
Choose the master clock and its reference deliberately. A GPS-disciplined grandmaster can work where a reliable antenna is available; elsewhere, an incoming house reference may be more dependable. Map source priority, PTP domain, outputs and holdover behaviour, and prevent any device from feeding timing back into the source it consumes.
Use distribution frames or splitters rather than daisy-chained consumers. Keep house sync one-way, label every leg, and separate clock traffic from production data where practical. Hardware-timestamped PTP can deliver phase across a managed LAN, but switch configuration and congestion determine real performance.
Redundancy should change authority predictably. A backup grandmaster can take over after a source failure while each node holds its disciplined state briefly. Document which alarms inhibit playout, how long holdover lasts and what operators must do after a source change.
Connecting real and virtual studios
In one studio, distribute the reference to playout, vision control, recording and audio infrastructure. Route critical timing through managed switches or dedicated distribution, and test with the production load present. An overnight test can conceal congestion, overloaded connectors and clock-quality changes that appear only during a full shift.
Between Sydney and Melbourne, or from a Perth bureau to a remote production site, ordinary internet latency cannot be treated as a studio cable. Use a contribution system with dedicated timing transport and monitoring; do not extend an unqualified PTP domain across a WAN. Each receiver should identify whether its reference is native, transported or held over.
Virtual radio tools require the same discipline as physical equipment. RƎLAY VRX can bring virtual sources and remote monitoring into a distributed team, provided upstream sources remain disciplined and event logs use one convention. A software timeline cannot repair an unstable reference.
Adapting the design for Australian operations
Australian television commonly runs at 25 frames per second, including 1080p25 playout in Sydney and Melbourne, while some studios retain 1080i50 or 50 fps workflows and legacy PAL sites still distribute SMPTE 311M sync. A consistent 25 Hz house reference is therefore essential. In radio-only facilities, video frame lock may be absent, but audio sampling, recorder transport and automation still need coherent timing.
Time-zone handling is a local trap. Sydney and Melbourne move between AEST and AEDT, Brisbane remains on AEST and Perth uses AWST, so wall-clock labels change twice a year in the east. Keep the timing engine on UTC or a stable reference, apply daylight-saving rules only in schedules and logs, and never disguise a local clock adjustment as disciplined holdover.
Mining operations, regional festivals and outback broadcasts add temporary studios with generator-backed power, intermittent links and uneven GPS reception. These sites need automatic source selection, local holdover and a clear return-to-reference procedure. Centralisation helps when a remote node follows a documented policy rather than a technician’s memory during changeover.
Local content operations have the same dependency. A local advertising insertion guide from another broadcast market shows how automated inserts rely on stable programme boundaries; at Australian radio networks, every station, replay server and monitoring feed must log the same cut points without drifting.
Verifying phase alignment and resilience
Validate the installed chain rather than trusting configuration alone. Check frame phase against a trusted source, listen for audio discontinuities and inspect logs for repeated frames, slips or unexplained time jumps. Test each fallback with the main reference deliberately removed, including the interval needed to reacquire phase.
Monitoring should distinguish source loss, holdover, loss of lock and drift. Publish those states through the control layer, with timestamps and the active source visible in the gallery and engineering room. Set thresholds around what the workflow can tolerate, not merely whether an electrical signal is present.
Run failover drills before a major live event or network migration. Record how the master clock, each distribution leg and critical endpoint behave, then restore the preferred path and confirm phase alignment again. Keep a dated signal-flow diagram and operating procedure beside the racks.
Comparing clock distribution methods
No single reference suits every site. The practical design combines a disciplined primary source, distribution suited to the building, and documented behaviour when the source is unavailable.
| Approach | Best suited to | Main strength | Operating constraint |
|---|---|---|---|
| GPS-disciplined grandmaster | Primary facility reference | Independent, traceable frequency and phase | Requires a reliable antenna and clear reception |
| Incoming house reference | Facilities with stable upstream sync | Broadcast-native and straightforward | Creates an upstream dependency |
| PTP/IEEE 1588 | Managed LAN distribution | Precise, scalable and monitorable | Congestion and switch configuration affect performance |
| House sync or blackburst | Legacy Genlock distribution | Familiar frame-aligned reference | One-way and less flexible than packet-based timing |
| NTP | Automation logs and control timestamps | Widely available and easy to deploy | Insufficient precision for audio or video phase alignment |
For a Lawo installation, map the choice to the actual signal path: mixer and I/O clocking, gateway timing, playout references, automation timestamps and monitoring. Judge the central service by end-to-end phase, not by the number of connected devices.
The design succeeds when one authority, one documented hierarchy and tested recovery replace competing studio clocks. Remember that Genlock is the final lock at each device; resilient centralised clocking keeps that lock coherent across studios, cities and temporary production sites. The practical measure is whether operators can identify the active reference, understand its status and predict failover.
