Digital Program Levels

Canonical Definition

Digital program levels describe complementary properties of recorded or streamed audio, including stored sample amplitude, reconstructed peak risk, and perceived program loudness.

The Main Measurements

Sample Peak

A sample-peak meter reads the values stored in the digital signal. Under the common peak convention, the maximum representable sample is 0 dBFS sample peak. A file below that value can still produce a higher reconstructed waveform after conversion or resampling.

Sample peak is useful for finding digital overload and for understanding how close stored samples are to full scale. It is not a perceptual loudness measurement.

True Peak

A true-peak meter estimates the continuous reconstructed waveform between stored samples. That matters because interpolation, sample-rate conversion, digital filtering, or lossy encoding can create peaks that are higher than the original sample values.

True peak is normally reported in dBTP. The measurement depends on the meter algorithm and standard. It is primarily a program-delivery and conversion concern, although converter output stages still need enough real analog margin to reproduce the result.

LUFS

LUFS is a standardized loudness measurement using frequency weighting and time behavior intended to track perceived program loudness better than a simple peak or unweighted average meter.

Common report types include:

• Momentary loudness: short window for immediate program behavior.
• Short-term loudness: longer window for local program density.
• Integrated loudness: the measured program over its defined duration and gating rules.
• Loudness range: a statistical description of variation in program loudness.

Delivery Margin Is Context-Specific

Streaming platforms, broadcast systems, games, cinema, podcasts, and local playback can use different targets and tolerances. A value such as -1 dBTP may be a practical delivery target in some workflows, but it is not a universal law and should not be transferred automatically to a car-audio DSP or amplifier calibration.

Always state:

• the delivery platform or standard
• integrated, short-term, or momentary loudness
• sample peak and true peak separately
• the meter standard or implementation
• whether the file will be resampled or encoded again

Why This Is Separate From Automotive Gain Structure

Music-delivery meters describe the program. Car-audio gain structure must also establish the clean analog and digital limits of the hardware:

• source output
• DSP analog input and ADC
• DSP internal processing
• DSP DAC and line output
• amplifier input and output
• speaker thermal and mechanical limits

A file with conservative true peak can still overload a badly matched analog input. A loud master can remain below sample full scale and still demand more sustained amplifier and speaker energy than a dynamic master. Program measurements and hardware calibration belong in the same system record but are not interchangeable.

Example Report

Common Mistakes

• Using LUFS as though it were a clipping ceiling.
• Using sample peak as though it guaranteed safe reconstruction or encoding.
• Calling RMS and LUFS interchangeable.
• Applying a mastering true-peak target to amplifier gain overlap.
• Quoting loudness without the measurement window or standard.
• Assuming normalization changes the original file in every playback system.

Related Resources

• True Peak and Headroom Planner
• Level References
• Headroom
• No-Clip Gain Structure
• Sample Rate Conversion and Dithering

Standards Notes

ITU-R BS.1770 defines algorithms for measuring audio program loudness and true-peak level, while ITU-R BS.1771 covers indicating-meter requirements.

• ITU-R BS.1770-5
• ITU-R BS.1771-1