Search found 378 matches
steve, thank you! I compared Noth filter and Hum remover even earlier, the conclusion is that Hum remover gives the best results. I also noticed that the effect works normally for short, up to 3 minutes tracks, if you take more, even selection doesn't help.
Apparently, to reproduce the problem, you need a laptop brand Lenovo , and, preferably, a new one. Then, install Audasity version 2.3.1-alpha-Oct 22 2018, download Hum remover from the Nyquist plug-in page, install, import a track, apply to the entire track, but select nothing, see the execution time.
Unclear. All other effects, if applied to the whole track, work exactly the same and with the same speed in both cases. 1 Nothing selected 2. Select all That is, if nothing is selected, the effect is applied to the entire track and everything, and speed, as usual. But this effect, Hum remover, works...
I've found the reason! If the effect is applied to the entire track, but not selecting all (1), the speed drops sharply, but if you pre-select the track (2), the effect works absolutely normally, as before. But how can it be? Please correct so that it can be both.
Dear experts! After deleting the pluginsettings.cfg file, all values should be reset to their defaults. But for the Noise reduction effect, the last used values still remain, even after reinstalling Windows. Is this how it should be?
And what to check? With absolutely the same characteristics, the plugin works on one machine, but not on the other. I've found another plugin - Mains dehummer. error: (a2 <= -1) or (1 - a2 <= |a1|) (unstable parameters a1 = -2, a2 = -1) in biquad Function: #<Subr-ERROR: #10eb3288> Arguments: "(a2 <=...