USE_HARD_CLIPPER=1

[DanH]

@aaronventure Yup, I had mixed results a few months ago, seem to remember the core.snex_node wouldn't compile properly, but I'm sure its been fixed since then! I did use an algo in the math_expr node but it produced a lot of sizzling noise in the exported plugin. Should I be putting it in an oversampling container?

[Christoph Hart]

@DanH a simple clipper is just a math.clip node as master FX.

[DanH]

@Christoph-Hart Just saw the clip node - is that new?!

[Christoph Hart]

@DanH nope has been sitting in the dark corner of the party for 2 years waiting for its moment to shine.

[aaronventure]

@Christoph-Hart According to my RME meter it still blows past 0.0 ever so slightly if I cram enough notes in there, so I'd top it off with a -0.2dB gain.

[DanH]

@aaronventure What's the device? No sign of it going over 0 on my total mix, or DigiCheck...

[Lindon]

@DanH said in USE_HARD_CLIPPER=1:

@aaronventure What's the device? No sign of it going over 0 on my total mix, or DigiCheck...

The RME drivers a famously very very quick...

[aaronventure]

@DanH Babyface Pro FS. Hmm.

But if you're already doing hard clipping, it's always a good idea to clip at -0.2dB , because of inter-sample peaks in D>A conversion. It costs you basically nothing and allows you to make sure that, under default circumstances and at 0.0db gain on your instrument's master gain control, it is not possible for your product to red out on its own. If it does, it'll be because of something the user did.

[DanH]

@aaronventure I agree I tend to do this in my DAW all the time

[aaronventure]

@DanH

If i play a couple of pedal notes with the saw in waveform generator at 0.0dB.

But if I set the gain down even -0.1 dB and play 11 notes.