Kazrog KClip Zero

[audiotools]

How would you like the auto-gain to be implemented? This is an often requested feature but non-trivial in the context of a clipper. Usual auto-gain works in such a way that it's static formula and depends on the current parameters, but you wouldn't expect it to change when the input signal changes. Then the plugin would act as a compressor, unintentionally.

But with a clipper it depends very much on the input material how the actual perceived loudness changes. For example, if you don't reach clipping and don't use any saturation, the perceived loudness won't change at all.
But if you reach clipping, the new harmonics will actually increase the loudness. Let me what your ideas about auto-gain in a context of a clipper are.

[e@rs]

One thing I wish StandardCLIP did have is a numerical dB indicator of how much has been clipped. I know there's the graphic at the bottom, and the meter, but I find just having the precise number more useful than a waveform graphic (if I've missed this as well then someone let me know!) A bypass would be handy too.

Thank you very much for your suggestions. They are all noted

I also suggested implementing this a while ago...

clpdb.jpg

[audiotools]

Thank you for the reminder

[MacSpares]

Will be grabbing this! Just out of curiosity, what is everyone's most common use for a dedicated clipper like this?

[perpetual3]

Will be grabbing this! Just out of curiosity, what is everyone's most common use for a dedicated clipper like this?

Clip atonal percussion mostly, like snares, claps.

[Trancit]

Clipping anything spiking (as long as it doesn´t hearable distort where it shouldn´t) which could trigger the final limiter too early

[martiu]

I use it mostly on drums to remove spikes that eat headroom, but you can use it on anything.

[ChristopherWD]

I have a lot of material with large spikes like this, so that's where a clipper comes in handy. Compressors tend to have too much "memory" and they'll continue to mess with the content after the snap, making it sound like it's being pulled around. Well, unless it can be adjusted to such an extreme that it turns into a strange sounding clipper anyway...

Many years ago when I was getting into this hobby the discussions around me seemed a lot different on the concept of clipping compared to today; how it was never desirable and I should feel bad for thinking about it. Though, slamming converters and pushing material into saturation to shave off transients? Well that's something else...

[Dark Fiber]

I find the sound of a hard clipper much more pleasant then the sound of a limiter.
So i'll use a hard clipper just before a limiter to do most of the workload.

[imrae]

Many years ago when I was getting into this hobby the discussions around me seemed a lot different on the concept of clipping compared to today; how it was never desirable and I should feel bad for thinking about it. Though, slamming converters and pushing material into saturation to shave off transients? Well that's something else...

Well, the main difference is that hardware clippers don't alias (as long as your converters are implemented correctly!)

Heavily oversampled digital clipping has become more accessible with KClip, StandardCLIP, OVC-128 etc.

(But yeah, there was probably some cognitive dissonance at work as well )

[Trancit]

nevermind

[Calagan]

I guess the main limitation of this free clipper, when compared to most iterations of this effect, is the absence of oversampling.
It may be quite a limitation IMHO... Even when compared to other free stuff, for exemple FreeClip from VennAudio...

[adl]

I guess the main limitation of this free clipper, when compared to most iterations of this effect, is the absence of oversampling.
It may be quite a limitation IMHO... Even when compared to other free stuff, for exemple FreeClip from VennAudio...

It has oversampling, but it´s fixed:
2x online, 16x offline