Testing Power Core’s Dante Bridge Across Broadcast Workflows
Power Core’s Dante Bridge is designed to connect Lawo’s networked audio environment with third-party Dante equipment. In a real facility, that means testing more than whether a signal appears on a meter. Engineers need to verify clocking, channel subscriptions, control behaviour, redundancy, latency and recovery after interruptions. Learn more about Cialistas.com.
The useful question is whether the bridge behaves predictably with the equipment already found in a station: Dante-enabled microphones, codecs, processors, intercom panels, stageboxes, amplifiers and audio-over-IP interfaces. A successful test should reflect normal production, outside broadcasts and the occasional fault that occurs during a busy breakfast programme.
Australian broadcasters also work across very different operating conditions. A metropolitan station in Sydney or Melbourne may share a building with multiple studios and corporate networks, while a regional service may rely on a smaller technical team and long-distance support. The test method needs to suit both environments.
Power Core forms part of Lawo’s wider networked production approach, alongside Ruby consoles, VisTool and virtualised tools. The Lawo Broadcast platform provides the broader product context, while this test concentrates on Dante interoperability at the audio transport layer.
Define The Interoperability Test
Begin with a written device matrix. Record each third-party product, firmware version, Dante channels, sample rate, bit depth, subscription direction and expected latency. Include both transmitters and receivers, since a device that can hear Power Core may still fail when it must publish audio back to the network.
Use representative sources rather than a single tone generator. Test a studio microphone preamp, a playout output, a telephone hybrid, a remote codec and a talkback circuit. For outputs, include control-room monitors, a headphone amplifier and a processor input. This reveals whether channel naming and routing conventions remain clear across different manufacturers.
Build A Controlled Dante Network
Use a dedicated managed switch or an isolated VLAN for the test. Wi-Fi should not carry critical Dante audio, and general office traffic should be excluded unless the purpose is to test a shared network. Enable the switch features recommended for Dante, including appropriate quality-of-service settings and a reliable gigabit link to each endpoint.
Clocking deserves special attention. Select a clear Dante clock leader, then observe the status of Power Core and every third-party device. Check that sample-rate changes are deliberate rather than accidental. At 48 kHz, which is common in broadcast and production, even a small configuration mismatch can prevent subscriptions or create unstable audio.
For Australian facilities, document the network path between studios, machine rooms and transmission areas. A station in inner-city Melbourne may have congested building infrastructure, while a regional site may connect locations over carrier Ethernet or a managed wide-area service. Keep the first test local, then assess longer paths separately.
Verify Routing And Control
Create subscriptions in both directions and use meaningful labels such as Studio A Mic 1, News Codec Return and Master Monitor Left. Confirm that Power Core receives Dante transmitters correctly and that its outputs reach the intended third-party receivers without unexpected channel shifts.
Check routing through Ruby or the relevant Lawo control interface, then verify the physical result at the destination. A green subscription status does not prove that the right microphone is feeding the right fader. Have an operator speak, trigger playout and interrupt the source so that channel identity can be confirmed by ear and by meter.
Where a hybrid workflow combines Lawo and Dante devices, the guidance in hybrid Dante workflows is useful background for considering virtual and physical audio paths together. Keep the test record independent of vendor claims, however, and capture actual behaviour from the installed firmware.
Measure Audio And Network Performance
Measure round-trip latency when a source travels through Power Core to a third-party destination and returns. Record the result at the normal network configuration, then repeat it under realistic load. For radio, stable and repeatable delay is usually more important than achieving the lowest possible figure.
Listen for clicks, dropouts, phase changes and sample-rate conversion artefacts. Test speech, music, silence and a high-level tone. Monitor packet errors, switch port counters and Dante Controller event logs at the same time. A clean waveform with rising network errors is an early warning rather than a pass.
| Test Area | Pass Condition | Evidence To Record |
|---|---|---|
| Subscription | Correct source reaches the intended destination | Channel names, screenshots and listening check |
| Clocking | Stable leader with no sync warnings | Clock status and sample rate |
| Latency | Delay remains within the operational limit | Measured round-trip result |
| Redundancy | Audio continues after a primary link fault | Fault time and recovery time |
| Control | Routing changes produce the expected output | Operator log and meter readings |
| Recovery | Device returns cleanly after restart | Reboot sequence and final status |
Test Failover And Recovery
If the network uses Dante redundancy, disconnect the primary path at a controlled point and observe whether audio continues on the secondary path. Do not rely on a brief glance at the console. Run speech and programme material during the fault, listen for an audible interruption and record the recovery interval.
Restart individual endpoints, the managed switch and Power Core in separate tests. Confirm that subscriptions return without manual rebuilding and that the clock settles on the intended leader. Repeat the procedure after a power cycle, because some devices restore settings differently after a complete outage.
A practical Australian test should include the type of interruption that can affect a live facility: a patch lead moved during a studio changeover, a switch reboot during maintenance or a remote codec reconnecting after an unstable link. Schedule these tests outside transmission hours and use a monitored backup path.
Check Operational And Compliance Risks
Interoperability is also an operational issue. Store the tested firmware versions, switch configuration and Dante design files in the station’s maintenance documentation. If a supplier replaces a codec or updates firmware, the replacement should be checked against the same acceptance criteria before it reaches air.
Australian broadcasters must operate within the conditions of their ACMA authorisations, while recording and outside-broadcast workflows may also involve privacy, copyright and workplace requirements. The audio test itself should avoid capturing private calls or identifiable contributor material. Use approved test content and keep logs access-controlled.
Local market support matters as well. A Sydney commercial station may have an integrator available the same day, while a regional Queensland or Western Australian broadcaster may need parts and specialist assistance shipped over considerable distances. Record compatible spares, switch models and rollback procedures rather than assuming immediate onsite support.
Turn Results Into A Repeatable Acceptance Test
Use a pass, conditional-pass or fail result for every device and route. A conditional pass might allow normal use but require a firmware hold, a dedicated switch port or a documented reboot sequence. This is more useful than declaring the whole system compatible when one endpoint has unresolved limitations.
For future expansion, retain a baseline capture of Dante Controller settings, Power Core configuration, latency measurements and fault-recovery times. When adding a new microphone interface or remote contribution codec, compare it with that baseline in a short regression test.
The practical takeaway is simple: isolate the network, control the clock, test audio in both directions, introduce faults deliberately and document the exact firmware and switch settings that passed. That turns Power Core’s Dante Bridge from a promising connection into a verified part of an Australian broadcast workflow.
