Just completed draft GUI for new limiter plugin. The next step is try to use it in some projects and make presets. And also to determine unneccessary functionality. After that the plugin will be ready to test.
Here’s some screenshots to show the progress.
Read more of this post
Just did last changes in true peak limiting module allowing to clip sound without inter-sample clipping. First it was mentioned in this post. And this is the last version.
After that I’ve made union of all modules to new Limiter6 plugin mentioned here. Unfortunately it has too many parameters and without GUI and levels indication it’s truly brain damage to try to use it:
The concept was changed a bit. Now this is slow RMS limiter followed by very fast peak limiter followed by the clipper and ended with true peak limiting stage. All stages can be turned on and off. Peak limiter and the clipper can work in M/S mode. Peak limiter can also work as high-frequency limiter. The whole plugin can work in stereo mode for master or mix busses and in mono mode for instrument tracks which I believe can be useful.
The conclusion? I have to do simple GUI for it and try to use the plugin in sample projects to find its strongest and weakest points. That’s the way.
It’s -20 C (-4 F) behind the window, a lot of snow and I’m really disappointed with peak limiter module. So I did a try to enhance it. You can check this [peak limiter VST plugin (x86,x64)]. I think it sounds better this time.
Now I can continue to build up my new mega-limiter from all modules I have (see previous post). The codename for this project is now “Limiter 6” (in japanese it sounds like “rimitta roku” which I like).
On the first look it’s gonna be too many knobs and switches. So it’s really a challenge to place them all on GUI and make it usable. Maybe I should remove or hide some of them…
I’m continuing my work. Good luck!
Okay, I have started making the new limiter from all modules I have.
The signal chain will be: DC Cut Filter -> RMS Limiter -> Peak Clipper -> Peak Limiter -> Output Clipper
- DC Cut Filter – to cut unnecessary lows (and to remove DC offset);
- RMS Limiter – to stabilize crest factor and to average loudness;
- Peak Clipper – to cut very strong peaks to help peak limiter not to “thump” on them (can work in M/S mode, have different knees to switch);
- Peak Limiter – to limit peaks (can work in M/S mode, can work as high-frequency limiter just to soften the sound);
- Output Clipper – (can work in true peaks mode to avoid inter-sample clipping or in simple mode just to clip samples, has switchable auto-gain mode to automatically level up the sound to -0.3 dbFS).
Maybe soft-knee control can be useful for Peak Limiter (I’ll check this soon). Maybe DC Cut Filter is better to place just before output clipper (I’ll check this later). I have no ideas about GUI yet.
By the way, I found that use regular compression curves with no high ratios (4:1 for example) for RMS limiter is better than limiting curve. I reimplemented the last RMS Limiter module (see previous post) with “Ratio” parameter and I think it sounds now pretty good. (Actually, I love how it sounds :-).) If you interested in you can check this [RMS limiter VST plugin (x86,x64)].
PS. I think the idea to show each small step of development of new plugin is better than keeping silence for year and after that to show only the last final step: the release version. I prefer continuous development process on each step of that you have something to check and to listen.
My idea is the slow RMS limiter before peak limiter/clipper helps to maintain constant crest factor and improves sound. So I did simple plugin to check this idea. Download it here: [slow RMS limiter VST plugin (x86,x64)].
The plugin parameters:
- “Gain” – input gain boost before any processing;
- “Thresh.” – RMS limiting threshold;
- “Attack” – think of it like RMS window size for signal level detector. The attack time is in seconds. The minimum value is 0.05 = 50 ms.
- “Release” – gain reduction release time. This time is time constant based (the time for GR to fall from 100% to 36.8%). In minimum “Off” position release time for gain reduction is not used;
- “Sidechn.” – sidechain high-pass filter (based on Molot one);
- “DryMix” – mix output with raw input (before gain boost) to fatten it up;
- “Lookahd.” – control lookahead. If “On” 10 ms lookahead is used. If “Attack” parameter has minimum value lookahead really helps to limit kick peaks for example. For greater attack times it helps to soften the sound. You can turn it off for taste or for realtime usage (if “Off” the plugin has zero latency).
The plugin is a bit tricky to tune up but I like it! Now I think it’s time to mix all my module prototypes to single cool limiter plugin!
PS. According to this site statistics “Most visitors came from The United States. Germany & Japan”. Maybe it’s a good idea to make translation of Molot GUI or even Molot manual to German & Japanese languages? Does anyone eager to help? Ж-)
I think I’ve got some kind of concept for upcoming clipper/limiter plugin. This plugin is planned to contain these modules:
- input clipper
- peak limiter (a.k.a “thin” limiter)
- signal limiter (a.k.a “thick” limiter)
- peak meter / output clipper
All modules are optional and can be turned off. Peak limiter has very fast attack/release and used only to limit peaks of signal. This “thin” limiter can optionally be used as HF limiter to limit only high-frequency components of peaks. Signal limiter has long attack/release settings to limit signal “body”. This “thick” limiter can be used in brickwall mode or in analog-style mode to pass parts of attacks through. Final clipper can work in inter-sample peaks suppression mode. And I think some high-pass filter to remove DC offset can be useful. That’s the concept.
Also I already implemented some ideas for peak limiter as test plugin. You can [download] it to check (Windows VST 32-bit and 64-bit).
What’s done in this test plugin:
- very fast attack/release limiter plugin
- only 6 samples of latency (in 44.1 kHz) so it can be used realtime
- it’s intended to limit signal peaks only so it sounds bad when limiting the signal “body”
What’s not done in this test plugin:
- no oversampling
- no inter-samples peaks detection
- no high-frequency limiting yet
So that’s it.
Read more of this post