Just setting up Audacity on a new computer.
I was sure all the sound from my new computer had a reverb effect applied,
(despite all the audio enhancements being turned off).
So I generated a mono bleep in Audacity, and recorded it in stereo, (via stereo-mix).
Low & behold, reverb …
(apart from latency, the red waveforms should be identical to the green original).
Now the bad news: this reverb effect is baked-in, ̶a̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶t̶ ̶a̶u̶d̶i̶o̶-̶d̶r̶i̶v̶e̶r̶ ̶w̶i̶l̶l̶ ̶b̶e̶ ̶r̶e̶q̶u̶i̶r̶e̶d̶ ̶t̶o̶ ̶g̶e̶t̶ ̶r̶i̶d̶ ̶o̶f̶ ̶i̶t̶.̶
How did you get Audacity to record itself? Computers want to play to the outside world and record from the outside world. There is no play and then record that playback unless you applied special routing apps or other software.
Routing apps and other software can generate feedback loops and other uncontrolled pathways leading to reverb and echoes.
How did you do that?
Stereo-mix, (same result with WASAPI).
The reverb effect is on everything, (e.g. browser, media-player), not just Audacity.
I can make the reverb effect worse by applying enhancements, but when “None” are selected the effect is still there.
From years of using reverb I was able to tell by ear it was >20ms, turned out it was 30ms
It’s not an unpleasant effect, but I need to get rid of it.
The sound card can do that. I got a machine from Systems and I couldn’t get it to pass quality enough to put in service. The sound card had “Cathedral Effects” stuck on.