Gale Andrews wrote:
I doubt the furnace caused the clicks. You have severe overshoot clipping where the samples reverse polarity. Instead of flat topping at the positive (top) part of the waveform, they shoot down to the bottom (negative) part:
overshoot.png
That abrupt change of direction causes a severe click.
You can zoom in (CTRL + 1) then select a region about the size of the region in the image above, then use Effect >
Repair....
As far as I know we don't have a plugin that deals with that type of clipping by selecting all the audio at once. If there is such, someone will say.
Gale
To expand on Gale's correct answer...
" You have severe overshoot clipping where the samples reverse polarity."
Looking at 24 bit waveforms... as part of the analog to digital process, the initial waveform is captured 48,000 or 44,100 times a second (48kHz or 44.1kHz sample rate)...
... and converted into a large number - so big that it takes (say) 24 bits of memory to store/manipulate (lets ignore 32 bit floating, dither, etc). Because the waveform swings around a center line the number can be positive or negative. It's a whole number so it's a "Signed" (+ or -) "integer" (whole number).
https://en.wikipedia.org/wiki/24-bit
that number calculated from the sampling process (for 24 bit) is somewhere between −8,388,608 to 8,388,607.
When some code tries to push that number past its end point (too big), it loops right around to the negative side and works up towards zero
eg: 8,388,607 + 3 = −8,388,606
or in this case, probably generates an error and is held at −8,388,608 for a few samples before the wavefom starts to come back from 8,388,607 (looking at the image of the waveform).
I wonder if this was handled with later code along the lines of (sloppy pseudocode):
if (sampleValue) greater than "8,388,607" then
sampleValue = "8,388,607" // effectively limiting the number, stops it from "reversing polarity"
end if