Floating-point audio to integer delivery: check scaled peaks
A floating-point working representation can hold values outside the normal full-scale range, but that does not make every overloaded recording recoverable. Before an integer delivery, inspect and scale the actual signal as needed. Distinguish numerical over-range values from distortion already introduced by a microphone, converter or earlier processing stage.
Open the relevant downloader · Platform tools and access limits
Find the layer where overload occurred
Keep the unchanged recording and examine representative loud events. A waveform reaching a boundary may suggest an issue, but its appearance alone does not prove where distortion originated. Compare listening evidence and the known capture or processing path. Lowering level cannot reconstruct peaks that were already flattened earlier in the chain.
A float working file provides a representation for processing, not a guarantee about the original capture hardware. A low-level export of an already distorted recording can still sound distorted. Avoid describing any format label as proof of unlimited microphone headroom or a promise that clipped voices will become authentic again.
Prepare a separately scaled integer export
When intact over-range values exist in the working signal, make a controlled gain adjustment before an integer conversion so the intended peaks fit the delivery range. Check the complete recording rather than assuming the first loud passage is its maximum. Account for enabled effects that may change the signal after your adjustment.
Select the actual required sample format and retain sufficient level margin for the intended delivery. Quantization and encoding introduce separate considerations; changing bitrate is not a substitute for addressing over-range samples. Do not repeatedly overwrite the only float source while comparing alternatives or searching for a suitable level.
Verify the resulting sound and representation
Inspect the exported file’s actual sample representation where applicable, then listen to the previously troublesome events in the receiving application. Check that the delivered signal has not introduced new clipping and that quieter material remains usable. A meter inside the project does not establish what a differently configured export contains.
If distortion remains after a sensible level change, investigate an earlier clipped stage or another processing cause. Keep the evidence and explain the limitation rather than promising restoration. This service can provide available source streams; it does not repair captured overload or certify arbitrary edited audio as an unchanged master.
Worked example
Suppose a working float signal has intact peaks above its normal full-scale reference. Lowering gain before a separate integer export can bring those peaks within range. If the original analog capture already flattened a shouted syllable, lowering the same passage merely makes the distorted syllable quieter; it cannot recover its missing shape.
Related guidance
Sources and verification
Reviewed 2026-10-09. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.