Optimal parameters to apply on small chunks of data for streaming application about noisereduce HOT 4 CLOSED

Hi Hugues,

I assume you are using the stationary version of the algorithm? The stationary version of the algorithm should be the same for long vs short clips if you are providing the same noise clip as input. It doesn't make sense to perform non-stationary noise reduction because you are basically providing stationary input if the timescale is too short.

If you have some metric of quality it is possible to search parameter space that way - e.g. training a prediction model on the output and seeing what set of parameters perform best.

All the parameters are in the main readme. I would focus on the prop_decrease, time_constant_s, freq_mask_smooth_hz, time_mask_smooth_ms, sigmoid_slope_nonstationary, n_std_thresh_stationary

These all relate to how the mask is built.

Best,
Tim

from noisereduce.

Thank you very much for your answer Tim.

Yes, I am using the stationary version. I will try to optimize on the parameters you indicated!

Best

from noisereduce.

Interested in how to get this working for streaming audio also, did you ever get something working @HuguesGallier ?

from noisereduce.

Hello @DamienDeepgram,

I couldn't find satisfying parameters for small chunks of data (200ms). When I process each of them separately, the quality of the resulting audio file when I join the treated chunks is not satifying.

So I will probably just remove the noise when I really need to (for instance, before speech to text).
Otherwise, you can find this other library if you want to remove the noise directly from the microphone itself with a LADSPA plugin (if you are on Linux).

from noisereduce.