Very interesting tool, i just tried for short time but for real its like ott with clipper and with low CPU work, and... compile in 5mb xd. (windows version)

as he said in his video:


What do u think?

 

Is it zero-latency?

 

rly free ?

 

plugin calls NSScreen safeAreaInsets unguarded. Loads in Logic but crashes instantly. Hopefully he doesn't mean "better than OTT" about the Xfer version.

 

Unusable, its lagging and freezing in Ableton

 

Tried in Reaper Linux as VST3.
Works without problems. Very little CPU.
Autogain would have been nice, but hey, it's free!
Unfortunately I am not experienced enough to judge whether it is better than any other.

Note: I downloaded beta 8 which is new since 2026-02-07.

 

Last edited: Feb 7, 2026 at 1:28 AM

works fine for me, vst3, ableton, M4 mac. Its good. More control than classic OTT - Ableton's, and then Xfers. Better than some of the other ones Ive accumulated over the years. Not as immediate as Xfer / Ableton, but useful in other ways. i appreciate the different preset crossover curves. I think my favorite "OTT" type processor is Squeeze, from GMaudio. A free M4L device that is insane. Highly recommended if you are into OTT and have ableton. It can be subtle or the most extreme gut wrenching sonic mayhem.

 

I don't know if I've sunk to the point where I can accept web GUIs in my plugins yet

(It does look like a competent plugin though)

 

Would you like to explain that? I am just a hobby-musician, but the interface looks pretty clear to me?

 

Yeah, it looks good, but it's using web tech. HTML/JS/CSS. I want my GUIs programmed in C, C++, Rust, Zig so they stay lean (RAM) and speedy (CPU/GPU). C#, Swift if you hold a gun to my head. So wasteful and inefficient. Possibly why Axvap's Ableton is lagging out.

What's next? Full blown Chrome tabs inside my DAW?

 

Hmm, still not clear what you mean but I realize I am not a very techie person. For me it is important that the GUI is intuitive, the plugin does not crash and the CPU is low. This plugin has all as far as I can see. I don't mind the language in which it is written.

 

Basically, the plugin (on Windows) spawns 6 instances of msedgewebview2.exe, using ~120 MiB RAM and 13% of my CPU in the background. Plus CPU and RAM for the plugin's DSP = ~130 MiB RAM and 14% CPU in total. That's many times more than OTT or any OTT clone that I've tried.

I just like lightweight stuff.

 

Yeah, and that's why it's lagging as f in my Ableton. That's the first time I encounter a plugin that does this for GUI

 

Polarity-MD

Four-band dynamics with upward + downward compression, per-band clipping.
Works on Windows, macOS, and Linux in VST3, CLAP, and LV2.

Update: 2026-02-07: Beta8 is live

https://polarity.productions/polarity-md/

 

Since I use Linux, I don't have that 6 instances of "msedgewebview2.exe", but I did some more testing after your findings and I must admit, this plugin does some very strange things. Although the CPU is low when used on a track, a very disturbing thing happens when closing the effect: the CPU raises with some 10%. When adding the plugin again, the CPU raises a bit but after closing it raises again with more than 10%. After 4 times adding and closing closing and having no tracks in my project, my Reaper just uses 50% CPU for not doing anything. What is going on with this plugin?

 

The crash I mentioned in my Logic is due to incompatability with macOS Catalina. Since there are no minimum system requirements on the page listed, I tried it. It disappear crashed Logic, but I was able to check the crashdump information. It's a beta but I don't think it will be fixed. The problem isn't that it is incompatible, it shouldn't have even loaded with that error.

It's a free plugin, so I'm not complaining about it. This is just info. But, Xfer's OTT is also free and doesn't do anything like this. I barely use OTT anyway, since Pro-C can do upwards compression, but I'm not a big upwards compression into a clipper sort either. If I'm going to use Kclip3, it's already a multi-band clipper. By bringing up the input side of Kclip3, you are bringing up all the quietest parts anyway; it's just bringing up the peaks also. A standard compressor or limiter first addresses the same thing anyway, it's just an inverse.

 

Crashed in Ableton Live 11 Suite/Catalina Intel
same way