Power Core Signal Generator for Regular Studio Calibration
Using Power Core’s Signal Generator for regular calibration of studio levels gives broadcast engineers a controlled source for checking gains, routing and monitoring. It is particularly useful in a networked Lawo studio, where Power Core audio nodes can sit between consoles, studios and playout systems.
The generator provides a known test condition; it does not make every channel automatically correct. Digital level, acoustic monitoring level, processing behaviour and programme loudness are separate measurements, each needing its own reference and acceptable tolerance.
For teams operating studios in Sydney, Melbourne and Brisbane, consistency matters more than local habit. The routine should serve commercial, community and educational radio while remaining traceable to relevant ACMA licence conditions, Australian broadcast engineering practice and the EBU loudness conventions commonly used for Australian playout.
Set a repeatable baseline
Start by defining the measurement points that matter: microphone preamp output, console feed, Power Core input, mix-minus bus, studio monitor, recording return and transmitter feed. Label each point with its normal operating level in dBFS, because a signal level only has meaning against a fixed reference. For multi-site operations, a general broadcast workflow reference can help place that baseline within documented ownership.
| Calibration check | Preferred source | Measurement reference | Correct action |
|---|---|---|---|
| Digital bus level | Sine tone at a fixed generator setting | Documented dBFS target | Align the selected channel or output |
| Monitoring level | Low-level pink noise, if supported | Calibrated sound-level meter at the listening position | Adjust the monitor control rather than the programme chain |
| Noise floor | Generator muted | Local technical noise specification | Investigate gain structure, grounding or intermittent noise |
| Processing behaviour | Tone followed by representative programme | Expected meters, loudness and channel correlation | Restore processing only after the raw path passes |
Use one primary reference point for routine checks, then compare other paths against it. Record tolerances for each measurement so a small deviation can be distinguished from a genuine fault requiring investigation.
Configure the generator safely
Treat the generator as a test source, not as programme material. Begin with outputs muted or feeds safely terminated, select a conservative generator level, and increase it in small steps while watching clipping meters. Keep the test away from the live transmission path and confirm that an emergency mute is available before changing routing.
In the Power Core control interface, choose a sine tone for stable level checks or a supported noise source for broadband tests; available options depend on the software release and I/O configuration. Route the source to one destination at a time. For the raw-path baseline, bypass EQ, dynamics, delay, loudness processing and AutoMix, recording whether each function was enabled or bypassed.
Measure each critical path
Begin with digital measurements using Power Core’s meters and, where available, VisTool displays. Compare the selected bus with the documented reference, then check left and right channels separately. Stable readings across repeated generator settings indicate that the digital path is repeatable; sudden changes may reveal routing, gain or processor configuration issues.
Acoustic monitoring is a separate calibration. Use a calibrated sound-level meter at the engineer’s listening position, play the selected test signal at a controlled level, and adjust the monitor controller to the agreed target. Do not assume that a particular dBFS value will produce the same sound pressure level in every room or with every speaker system.
Check channel balance and polarity after the level passes. A sine tone can reveal phase cancellation that programme material might conceal, while speech helps confirm intelligibility and gain stability. Record the generator source, output setting, meter reading and any acceptable deviation rather than marking the path simply as “passed”.
Verify the wider broadcast chain
A calibrated studio monitor does not guarantee that the recording return, mix-minus feed or transmitter contribution is correctly aligned. Extend the test through each critical destination, including headphone systems, live rooms, recording machines and remote contribution paths. For installed systems, verify that the generator reaches the intended Power Core input and that no unexpected processing has been inserted downstream.
Signal tests also expose automation problems that meter checks alone can miss. Confirm mute behaviour, talkback isolation, channel assignment and failover routes without sending tone to air. RƎLAY’s automated playlist metadata guide covers a different part of the operational chain, but it illustrates why programme automation and level integrity require separate checks and clear ownership.
Build a maintenance schedule
A practical routine combines frequent confidence checks with less frequent absolute measurements. Operators can confirm a nominated reference level at the start of each shift, engineering staff can inspect the complete signal path monthly, and a full acoustic and digital calibration can be repeated quarterly. The interval should reflect equipment age, studio usage and the tolerance required for broadcast delivery.
Repeat the baseline immediately after hardware replacement, software updates, I/O changes, processor preset changes or unusual signal events. Keep the previous result available so the engineer can identify drift rather than accepting a new setting without comparison. A fault should be investigated and recorded before the affected path is returned to service.
Daylight-saving changes in Sydney and Melbourne can move maintenance windows twice each year, around the first Sunday in October and the first Sunday in April. Add those transitions to the engineering calendar so staffing and access remain available. The same discipline applies to remote facilities across Australia, where a central team may support studios in several cities and time zones.
Keep records and close the loop
Store each result with the date, responsible engineer, software version, generator setting, measured value, accepted tolerance and any corrective action. Keep calibration records alongside maintenance and fault logs rather than in an isolated spreadsheet. Trend the readings across visits, because gradual drift often reveals a failing component, unstable reference or recurring configuration error before it becomes an audible broadcast fault.
The immediate next step is to run and document the baseline calibration during the next quiet maintenance window.
