Repair One Noisy Section Instead of the Whole Recording
When a fan, a buzz, a gust or a quiet answer affects only part of a recording, repair that part and leave the rest as recorded. What the editor does at the edges, when to use the whole-file fixer instead, and how to compare the result.
By the fix.fm team · Published · Updated
Most recordings are not broken everywhere
A file that needs repair usually needs it in one place. A fan starts halfway through an interview. A phone charger buzzes for two minutes of a one-hour call. One guest leans back and goes quiet for a single answer. Processing the whole file for one of these problems means processing the clean parts too, and every denoiser, hum filter or level boost has a cost somewhere, as why noise reduction makes a voice muffled or robotic explains.
Selection repair is the alternative. Mark the part of the recording that has the problem, repair that part, and leave everything else exactly as it was recorded. This article explains how that works in the free audio editor, what the editor does to the edges so the join is not audible, where the approach stops being the right one, and how to check the result.
What the editor can repair on a selection
The editor's Repair tab works on the clip you have selected, or on the part of a clip you have isolated with a selection. It checks the selected source and offers these four repairs when their checks find a problem:
| Check | What it listens for | Repair |
|---|---|---|
| Background noise | Steady hiss or fan sound under the voice and in gaps | Neural noise reduction |
| Hum and buzz | A pitched electrical tone and its harmonics | Tuned hum filter |
| Too quiet | Low integrated loudness in the selected source | Linked compressor and limiter |
| Wind noise | Deep rumble that rises and falls in gusts | Adaptive high-pass and low-band attenuation |
These are the same repairs that the whole-file noise, hum, wind and quiet-level fixers use. Echo, muffled sound, distortion and one-sided stereo are not available on a selection yet. They still run on whole files in their own fixers, and the audio repair finder tells you which one you need.
A selection can be up to 30 seconds long. That limit bounds the processing work and memory admission; it does not guarantee a particular repair time on every device. High sample rates and hum context can need shorter sections. For a longer stretch, split it into pieces, or use the whole-file fixer.
Isolate the problem first
In the editor, drag across the waveform to select the noisy part, then press Split so that part becomes its own clip. The clip now has its own gain, fades and repair state, and the clean clips on either side are untouched.

Include complete words and place the boundaries in pauses when possible. Processing can change the voice as well as the unwanted sound, so compare those words with the clean audio beside the selection. A boundary ramp reduces abrupt switches; it cannot make a cut in the middle of a syllable sound natural.
Run the checks, then repair only what failed
With the new clip selected, open Repair. Each check reports a plain sentence first, then the number behind it: an estimated signal-to-noise ratio for background noise, integrated loudness for level, the detected hum frequency, or the share of blocks with gusty low rumble.

Press Repair on the failing check only. Running the hum filter on a clip with no hum, or boosting a clip that is already at level, changes the audio for no benefit. A check that reads "Looks fine" is a reason to stop, not a box to tick.
What happens at the edges
Two details make a selection repair sound like part of the recording rather than a patch dropped on top of it.
First, context. The noise repair reads one second of the original recording on each side of the selection so that its model of the noise is not learned from a cut edge. The hum repair reads six seconds, because a hum frequency estimate needs a longer window. That context always comes from the original source file, never from whatever clips happen to sit next to the selection on the timeline, so moving the clip later does not change the repair.
Wind and quiet-level repair use only the selected source interval. Loud clean audio outside a quiet windy section must not decide whether its wind is present. If independent gusts disappear in the stereo mix, the wind check also examines each microphone. Wind repair reduces low-frequency rumble and can also thin the voice. Try the Wind on a microphone sample in the editor, compare Before and After, and lower Amount if the speaker loses body. It cannot recover words overwhelmed by a burst.
Second, the join. The repaired audio is cropped back to the exact selection, and the editor applies a 10 millisecond dry-to-wet ramp at each boundary. That ramp softens the switch between versions. On a hum repair in a quiet passage you may hear the buzz fade over that 10 ms rather than stop dead, which is the point: an abrupt switch can click.
The original audio is never rewritten. A repaired clip keeps a reference to both versions, and the Before and After buttons swap between them for playback and export alike. If you split or trim the repaired clip afterwards, both versions follow.
Compare, then adjust Amount

Play the join at normal volume, then play the middle of the repaired clip and toggle Before and After. Listen for three things, in this order: did the problem get smaller, are all the words still there, and does the speaker still sound like the same person as in the surrounding clean clips. That last comparison is one you only get with selection repair. When the whole file is processed there is no clean reference to compare against.
Amount starts at 80%. Changing it reruns the original selection rather than processing the last result again. Noise, hum and wind scale the blend of original and processed audio; quiet-level repair scales the boost in decibels. Lower it if consonants soften or breaths disappear. In the walkthrough above, 80% took the hiss from 19 dB to 32 dB SNR without an audible change to the voice, and we left it there.
Every step is undoable, including the repair itself. If the clip sounds worse, Undo removes it and the original clip comes back with its fades and position intact.
When to repair the whole file instead
Selection repair is the right tool when the problem is local. It is the wrong tool when the problem is everywhere, when it is not one of the four repairs above.
| Situation | Better choice |
|---|---|
| Hiss under the entire recording | Whole-file noise repair, once, then edit |
| Hum that comes and goes with a refrigerator | Repair each occurrence; the hum filter needs a steady tone |
| One speaker consistently quieter than the other | Track volume in the editor's Tracks tab, not a repair |
| A whole file that is too quiet | Loudness normalization, then check it on the LUFS meter |
| Wind across the whole recording | Whole-file wind repair, then compare voice tone |
| Room echo, distortion or a muffled take | The whole-file fixer for that problem |
Repairing a hiss that runs under the whole file in ten separate selections gives you ten slightly different noise estimates and ten joins. One whole-file pass is cleaner. The reverse is also true: running a whole-file denoiser because two minutes of a two-hour recording have a fan in them processes 118 minutes that did not need it.
Check the finished edit as a whole
Once the repaired clip sounds right in place, listen to the whole piece from a few seconds before the join to a few seconds after the end of the repaired clip, at the volume a listener would use. Then check the finished export's level once, because a repair changes level slightly and a quiet-level repair changes it a lot. The LUFS meter reports integrated loudness and true peak for the whole file, and the podcast audio workflow places that check at the end, after the cuts and repairs are done.
For a complete worked example, editing an interview applies this exact repair in the middle of a cut list, with the exported before and after audio. Audacity's manual describes the same idea for its noise-profile tool in Noise Reduction: select the problem, not the file.