Barricade 4.1.0 has been released :)

[dasdeck]

You're sure that you're not talking about a compressor then?

Yes, 100% sure, just used the term compression to refer to limiting.
I try to do this with every limiter/clipper/compressor if possible.
I find it very impractical to judge transient/compression/limiting behaivour when gain changes in the meanwhile.

[Compyfox]

I forwarded the "Monitor Button" FR to Jeroen as he's not that often on KVR, let's see what happens.


I found a bug in Barricade 4 though (which is already confirmed by the dev):
The True Peak Mode is currently linked to the Compressor (it has to be active in order to use it) and not the Limiter (like it should be).

So if ISP Detection/True Peak Limiting is important to you, currently just activate the compressor for v4.1.0 - or revert to Barricade 3 for the time being.

Jeroen is already on the case and an update will be out ASAP.

[Beatworld]

I found a bug in Barricade 4 though (which is already confirmed by the dev):
The True Peak Mode is currently linked to the Compressor (it has to be active in order to use it) and not the Limiter (like it should be).

Thanks for that, I had no idea.
I bounced a master yesterday with 4.1, not using the compressor.
The funny thing is that Barricade still stopped slightly more peaks getting past the ceiling than another limiter I had been using on the same project the day before.
And that other limiter had TP mode on and working !

[Compyfox]

Which one was it?

[Beatworld]

Which one was it?

TrackLimit.

To be clear, I'm talking about a difference of about 0.1 db

[Beatworld]

Which one was it?

TrackLimit.

To be clear, I'm talking about a difference of about 0.1 db

why can't we delete posts in KVR ??

[djeroen]

v4.1.1 is now available - this should resolve the true peak dependency on compressor being enabled.

[AegisPrime]

v4.1.1 is now available - this should resolve the true peak dependency on compressor being enabled.

Great stuff - thanks Jeroen!

[nicksohn]

v4.1.1 is now available - this should resolve the true peak dependency on compressor being enabled.

It says that the zip file is damaged.

[djeroen]

please try again

You can also download Barricade v4.1.1 (without the full bundle - it's under 'legacy' downloads).

[nicksohn]

please try again

You can also download Barricade v4.1.1 (without the full bundle - it's under 'legacy' downloads).

I tried it 4 times... but never worked fine...

Now.. wait..! It works perfectly fine!! Thanks Jeroen!

[mutantdog]

4.1.1 has a bunch of new limiter types available too.



The Auto modes seem to do away with the attack and release portion.

This week i've been going back through loads of old projects and sticking B4 on in place of B3. Possible case of new-toy-syndrome but everything sounds better with B4 in transparent.

[Compyfox]

Jeroen is working on a manual update regarding these new modes.


Speaking of "Transparent" and "better sounding" - jump between Barricade 3 mode and Transparent, the difference is minimal if you're doing moderate limiting (think -12dB RMS avg). If you're doing onto "make sh*t loud" territory (think -6dB RMS avg or -4dB RMS max), that might be a completely different thing.

[Tp3]

. If you're doing onto "make sh*t loud" territory (think -6dB RMS avg or -4dB RMS max), that might be a completely different thing.

Care to explain ?

[Compyfox]

Thr behavior mode of the limtier changes depending on the selected Limiter preset of course. To my understanding from recent mails, it's a complex interaction of various compression/limiting stages.

The stronger you push the signal (Limiter Gain), the more obious the effect.

So if you're within "normal" loudness values, the difference might be subtle. Push it, and one preset might work better than the other, might sound completely different even (also see Fabfilter Pro L v2 - which uses a similar concept)

Then again, Barricade was never a limiter to go "super loud"