Melda Clipper (MWaveshaper?)

[bilrobins]

Hey guys

I'm just looking for a tool to shave off some peaks to give more headroom, etc. Is MWaveshaper just as good at (hard?) clipping as anything else? Keeping it as simple and transparent as possible would be great.

Also I've read that aliasing can be an issue - is this the case when just shaving off (mostly inaudible) peaks?

CHEERS

[vanerio]

Yes! It is a very good clipper too!
I compared it to some clippers out there and it works perfect.

[MeldaProduction]

And you can probably use Math module in MXXX too I keep recommenting this one to make it useful
But also MSaturator, just put the threshold up.

[bilrobins]

Hey, thanks for the responses - super useful. The maths module eh? I'm lucky enough to have the Complete Bundle - so I'll have to check that out. Should I be scared!? Sounds complicated

[smadger]

I was looking at that the other day, I have a feeling it's super powerful but would love some videos to help explain how to use it or some presets to explore how it can be used - they're aren't any at the moment

[MeldaProduction]

Hehe well, generally if you don't know you need it, then you don't need it . No really, sometimes it gets handy for more scientific stuff.

[tinktink]

Resurrecting an old thread here. I keep trying to use MWaveshaper as a clipper so I can take advantage of the low CPU and great oversampling options (plus I've become a Melda fanboy in the last year), but I constantly get overshoots. Do you mind sharing the settings you are using?

[Held]

Do you mind sharing the settings you are using?

I tried it, and the clipping only seems to work, if I disable oversampling. With over sampling enabled, I also get overshoots of up to 3dB. This seems like a bug.

[MeldaProduction]

It's not a bug - basically when you oversample something, do some processing, and downsample afterwards, you may (and will) end up with higher peaks than before. Just use a limiter afterwards.

[SunlightSpirit]

And you can probably use Math module in MXXX too I keep recommenting this one to make it useful
But also MSaturator, just put the threshold up.

Hey Vojtech,

What is this math module you speak off?

I'm looking for a decent clipper and have your complete bundle

[vanerio]

And you can probably use Math module in MXXX too I keep recommenting this one to make it useful
But also MSaturator, just put the threshold up.

Hey Vojtech,

What is this math module you speak off?

I'm looking for a decent clipper and have your complete bundle

In MXXX add a Utility -> Math module. After that, select Limit mode.

[vectorwarrior]

Better yet, you can use the free MUtility plug for this. I just tried it out with an oscilliscope and it works exactly as expected... although I did note that melda's oscilliscope didn't like it for some reason.

Anyway, you need to use the 'expression' node in MUtility and enter the expression:
limit(x,-p1,p2)

This will allow you to use the two Parameter controls to set the hard limit for negative (parameter 1) and positive (parameter 2) portions of the signal.

The output will probably mute once you set this up, because the defaults are zero. Set them to 100% to set it to full scale.

One extra note, as you limit the signal more, the waveform will be truncated, so if you're really reducing it down it'll get pretty quiet and you'll want to bump the volume up afterwards.

Hope that helps

[Held]

It's not a bug - basically when you oversample something, do some processing, and downsample afterwards, you may (and will) end up with higher peaks than before. Just use a limiter afterwards.

Could that be avoided by using linear phase filters when down sampling? That's what FabFilter uses for their limiter.

It would be nice, if I could use MSaturator/WaveShaper as a clipper to reduce peaks, not increase them.

[sparella]

I'm thinking that MLimiterX is a clipper when attack, release, and look ahead are all zero. You can oversample it without overshoots.