MWaveShaper oversampling?

[Annabanna]

I use MWaveshaper a LOT as a basic clipper by using squared mode for easy input vs output reference metering, then precisely defining the points on the grid and using the smoothing options to ensure that, for instance, I have EXACTLY 1 db of knee that's perfectly smoothed and can rely on the signal being completely untouched below that knee.

It works great, but as I'm looking at doing something similar on a master where the exact output values are critical and I'm monitoring both pcm and tp values.

I'm wondering whether I've got the highest possible quality dialed in. I don't see the 1x, 2x type options I've noticed on some of the other plugs for oversampling, so not sure if I should crank the smart interpolation, or maybe use it inside mxxx with oversampling cranked on the parent or something like that to ensure I have the most precise possible behavior for the clipping that perfectly smooths through the knee for all ISP's, etc.

[MeldaProduction]

Hmmm, I'm confused, MWaveShaper DOES have oversampling in the plugin toolbar, up to 1024x I think!

[Ploki]

it does

you need to buy the free bundle to access it tho

[Annabanna]

Ahh... I see it now. Thx.

On Mxxx modules, it's one of the tabs on the top right, so I was expecting to find it in those options along with settings, etc. The toolbar tab was minimized, so I couldn't see the option.

Now that I'm thinking it through, though... does oversampling matter in a waveshaper? Since it's just a remapping of input values to output values per sample with no time or other considerations shifting those values in other way, no matter how much inter-sample interpolation you do, doesn't it just collapse back down into the same exact mapping at the original sample rate?

[MeldaProduction]

Actually if you look for a plugin, that would definitely need oversampling, then it is a waveshaper . Without delving into the mathematics here, any distortion is the main subject to aliasing, since it generates higher harmonics, which eventually reach Nyquist and get aliased back. Try a sine wave of say 1k, destroy it using MWaveShaper and check with and without oversampling, you'll definitely hear that.

[Annabanna]

Try a sine wave of say 1k, destroy it using MWaveShaper and check with and without oversampling, you'll definitely hear that.

OK. I definitely hear that. thx.

I use mWaveshaper all the time, but most often as a drum clipper. I wasn't able to hear it clearly under normal use conditions in some of those contexts. Not entirely sure if that's just the nature of the enharmonic transient material or whether much of it is above my hearing limit of 12k or so.

Regardless, I often use it for much milder clipping toward the end of the MB chain, so I'll definitely start using the oversampling there. With this in mind, I may also revisit whether it can be used for very gradual (large knee) clipping on more melodic material as I sometimes do that rather than compression with similar settings.

[MeldaProduction]

I think it could work fine for percussive stuff. The main problems come with harmonic instruments, which become kinda, well, inharmonic