[FEATURE] Alternative oversampling algorithms (low latency vs. low alias) #10
Description
Problem
The plugin now oversamples if the input signal is e.g., 48kHz and the capture is e.g., 192kHz. I appreciate that the oversampling algorithm was chosen to be the one with lowest latency, but the problem is that the current low-latency oversampling creates quite a lot of aliasing when compared e.g., to effect instance oversampling in Reaper. There seems to be a lot of spectral components over the nyquist limit (e.g., in case of 48kHz signal, the oversampling algorithm should not produce components that are over 24 kHz). As shown in the attached spectrogram, those components get folded back (aliased) to the produced output.
Proposed solution
As an alternative (maybe user selectable), use an improved oversampling algorithm that does not produce higher frequency components that then get aliased back.
Additional context
Sine sweep spectrogram, on top using Reaper's per plugin oversampling, below using NeuralAmpModeler oversampling.
