Hello,
Can you all add over sampling to all of your Harmonics processors, saturation processors, & distortion processors? Opions ranging from 4x-16x. This will help all the users whether they know about anti-aliasing or not. Thanks in advance.
1 Like
This is a subject that has come up a couple of times on here. Apparently it’s quite a popular request. It’s a good idea too.
Good request! I’ve always expected we’ll see this in an update someday.
In the meanwhile, I will note that Reaper natively oversamples and it works really well with all the Waves plugins I use. I can even set the oversampling as a default option, so that it’s always oversampling.
This is also important to know:
Waves plugins are inconsistent with regard to how high they can go in terms of sample rates.
Quite a few of them can’t go past 96khz, so I just default to x2 oversampling when I use that feature. Some go up to 192khz.
And there’s at least once that you can’t oversample at all – Flow Motion FM Synth is limited to 48khz, which is surprising. But it’s one of their older classics.
If you’re not a Reaper user, there are 3rd party VST containers which can add oversampling, although I would personally find that too much trouble to be worth it.
Anyhow, +1 to your request.
I tend to run my sessions ant 96kHz, which is effectively like having a x2 oversample on every plugin, even ones that don’t support oversampling.
From there I selectively choose elements I want to add more oversampling to using plugins that support it. Using a x2 or x4 oversample on a plugin effectively becomes the equivalent of x4 or x8 because of the project’s 96kHz sample rate, but has half the latency.
Yeah your CPU does work harder. I have a Mac Studio M4 Max, so I have some horsepower there, but if I start running out I just have start freezing some tracks to reclaim again. I only wished that Logic would allow you to freeze it’s Summing Stacks and Auxes as well.