BGC: NOTES
Soundworks

BGC: NOTES / Studio Notes

Sep 10, 2026Studio Notes5 min read

Sound Devices MixPre II: meters still matter in 32-bit float

32-bit float can preserve an unexpected peak inside the file, but it cannot make a good take on your behalf. On the MixPre II, the meter should be read less as a clipping alarm and more as a screen for deciding microphone distance, location noise, and monitoring balance.

In Brief

Separating recoverable file gain from on-location judgment turns 32-bit float from insurance into a more exact recording method.

Separate recoverable numbers from an unrecoverable scene

Sound Devices explains that a MixPre II 32-bit float file can contain signals above 0 dBFS and be turned down later in a DAW without adding noise or distortion. That is a real advantage on a set with a wide and unpredictable range: an actor suddenly shouting, an instrument moving closer without warning, or an impact arriving after a very quiet ambience. There is less reason to record an entire scene unnecessarily low in anticipation of one peak, and less reason to discard a take because its waveform crossed a familiar digital ceiling.

That protection, however, belongs to the numerical range of the recorded file. A microphone capsule overloaded by sound pressure, incorrect powering, a damaged cable, wind striking the diaphragm, wardrobe rub, or a wireless transmitter clipping before the recorder cannot be repaired by a file format. Being able to scale a waveform down after recording is not the same as having captured the source intact.

The first decision after switching on a MixPre II should therefore be to locate the scene’s maximum event, not to choose a reassuring gain number. Ask an actor for the real movement and loudest line. Let a percussionist play one hit at performance strength. At that moment, listen for texture splitting in the headphones, a boom angle changing, or a room reflection jumping ahead of the direct voice.

32-bit float is not a technology for skipping that rehearsal. It is a technology for preventing one gain control from consuming the rehearsal. Once numerical headroom is no longer the only concern, there is more attention available for the capsule, distance, angle, wind protection, cable, and wireless front end—the places where damage may truly be irreversible. A safe file is the result of that observation, not a substitute for it.

Turn the meter from an alarm into a map of relationships

In a conventional 24-bit workflow, the meter is often treated as a display of distance from the ceiling. That job becomes less urgent in 32-bit float, but the display does not become meaningless. It becomes a relationship map: the gap between peak and average level, the gap between voice and background, and the difference in energy between two performers can be compared at a glance.

Imagine an interview voice whose average level is steady but whose sentence endings fall by 15 dB. Raising the file later will not improve the ratio between those endings and the room tone. The location decision has to happen while the meter is falling: follow slightly with the boom, keep a lavalier as a support track, or ask for a noisy appliance to be stopped. Here, the meter is not preventing a clip. It is telling the crew which action is still available.

The headphone mix needs its own distinction. A wide range may be recorded correctly to isolated tracks, yet an LR mix or monitor level dominated by one source can hide wardrobe noise and cable taps on another channel. Input gain, ISO recording level, post-fader LR balance, and headphone volume should not be treated as one control system. Each level exists for a different listener and a different decision.

At BGC, even a twenty-second test take gets three passes. The first is for the emotion of the voice or performance. The second is for the floor of its quietest moment. The third is for the texture of its loudest moment. Only then do we match the meter’s shape to the ear’s impression. A wide-moving meter can describe a stable scene, while a calm meter can conceal a distant microphone and a voice that has lost its center.

In a mode without limiters, listen to the front end more precisely

The MixPre II user guide states that limiters are disabled in 32-bit float mode. This does not mean the recorder is unprotected. It means its multi-stage conversion and floating-point file preserve wide dynamics by another method, while the shape and sound a limiter would impose are no longer part of the recording.

That difference makes it unwise to carry over a 24-bit habit of pushing level into a trusted limiter. In 32-bit float, the useful question is not “how hard should this be limited?” but “what can overload first?” Check the level from a hot condenser microphone in front of a kick, the output of a wireless receiver, a mixer feed entering a line input, and the headphone amplifier’s listening level as separate parts of the path.

On location, it helps to divide the scene into two targets. Keep the recording path open enough to retain a sudden maximum, while keeping the monitoring path consistent enough that small faults remain audible. Rather than turning the headphones down sharply after a peak and missing noise under the next whisper, hold a comfortable reference level and use the meter to follow the full range.

After the take, move the file into a normal listening range with clip gain before judging processing. Recovering a waveform that sat above 0 dBFS and shaping performance dynamics with a compressor are two different jobs; they should not be collapsed into one move. The MixPre II is valuable not because it makes every choice automatically, but because it lets the crew concentrate on irreversible choices during the shoot and reconsider level and dynamics calmly in the edit.