KVR Audio

BrokenTrance · Post by **BrokenTrance** » Sat Aug 13, 2016 5:02 am

I use MLimiter, but i have no idea if it's good

Tp3 · Post by **Tp3** » Sat Aug 13, 2016 5:40 am

BrokenTrance wrote:I use MLimiter, but i have no idea if it's good

It's good as long as you remember that it is NOT a limiter ... (despite its name)

Tearing Riots · Post by **Tearing Riots** » Sat Aug 13, 2016 10:59 am

BrokenTrance wrote:I use MLimiter, but i have no idea if it's good

Best free saturator

Here´s another challenger, xhip limiter. Win only (32/64), 4000 samples delay but light on the cpu, tweakable and very clean. The gui is not working for me in the latest version but i don´t care:

http://xhip.net/effects/

BrokenTrance · Post by **BrokenTrance** » Sat Aug 13, 2016 11:50 am

Yeah i have no idea what i am doing. I use it to get a louder sound.

SaschArt · Post by **SaschArt** » Sat Aug 13, 2016 7:45 pm

thecontrolcentre wrote:
SaschArt wrote:http://vst.saschart.com/easylimiter

Best performance, very efficient and easy to use. Consumes less resources in the VST limiter area, far, incredibly less.
64 bit?

1. Try to use easyLimiter.dll , lot of x64 machine works and resource consumption is the best
2. Use easyLimiter_x64.dll from download archive if not work

aciddose · Post by **aciddose** » Sun Aug 14, 2016 12:31 am

Tearing Riots wrote:Here´s another challenger, xhip limiter. Win only (32/64), 4000 samples delay

The latency compensation only works with the hidden "LTC-comp" (use host GUI) parameter enabled. Otherwise the plug-in reports zero latency and the real latency depends upon the setting of the attack and look-ahead parameters.

I've no idea what might cause the GUI not to show up, I'll see if I can fix this.

Look-ahead is the percentage of the attack time to delay the signal. At 100% you should get brick-wall limiting although of course this introduces some latency.

It also can work well with lower look-ahead settings (near 50% is good) and the combination with the hold parameter can give you zero steady-state distortion (like on a sine) although often lower hold settings perform better for normal material.

Tearing Riots · Post by **Tearing Riots** » Sun Aug 14, 2016 11:08 am

Thanks for chiming in here and the additional info.

aciddose wrote: The latency compensation only works with the hidden "LTC-comp" (use host GUI) parameter enabled. Otherwise the plug-in reports zero latency and the real latency depends upon the setting of the attack and look-ahead parameters.

That´s not how it works for me in bitwig studio. Compensated latency shows 102,4ms@44.1kHz no matter if LTC-comp is on or off (reloaded the engine just in case). Though this can be a somewhat 'special' host sometimes.

aciddose · Post by **aciddose** » Sun Aug 14, 2016 10:30 pm

I've had a bit of trouble trying to get hosts to update correctly. I suspect many only check the latency value when they reset/resume processing.

http://xhip.net/effects/releases/xhip_limiter_64bit.zip
http://xhip.net/effects/releases/xhip_limiter_32bit.zip

I've updated the limiter, it may work now although you may have to stop+start playback to get the latency to update.

It wasn't working correctly and was always reporting 100 ms latency regardless of settings.

edit: The GUI issue is now also fixed.

Best free limiter VST?