LV2 is not that old [~10 years?]. It replaced LADSPA plugins. LV2 would be the equivalent of VST3 in comparison to VST2.

But what you said makes sense. Maybe LV2 is not good enough? But it would cut them a huge amount of time from developing a new standard and LV2 is really great. It supports all the VST3 stuff AFAIK. I'm using some LV2 plugins in Reaper in Linux and WIndows. They work well.

I mean why not just taking a very well known open source LV2 standard and developing it further? That's my point. That's why Open Source exists!

p.s. I guess I should visit KVR... omf Crom thankfully I have a full bottle of wine within reach. I'm gonna need it.

Have a nice Saturday night Xupito!

 

Last edited: Mar 5, 2022

I think "quite old" as a plugin standard can only be good. I'm worried about stabilty first, then CPU usage 2nd. Ask developers. A lot of them still hate VST3 [because of aforementioned - only use VST3 if there's no other choice if you crave stability], but Steinberg gave them no choice by suspending VST2 developer's package completely.

 

Judging by the customer basis those (us) idiots will never pressure them enough to do so

 

From what I got so far from that KVR thread, it's pretty exciting. :droolinsky:

Imagine if u-he plugins were only available as CLAP. Would you still use Cubase, Logic, or shitty ProTools still, if you can't have your favourite instruments in it? This feels like a great move from Urs and u-he! Fight the closed VST standard controlled by Steinberg and including JUCE developers into it! :prayers-answered:

I'm all for it. LV2 is great, but since CLAP includes JUCE and it's made up by minds like Urs, and it's Open Source, there's absolutely no reason to doubt its absolute usefulness.

The only problem is it will take 10 years for it to become a standard. Although they already got Cockos [Reaper] onboard. This is all a very, very good thing. What Urs said about the standard is really advanced. More advanced than VST3 or LV2. It will be a happy future for ITB musicians, and us hybrid ones. [that's why I have orange eyes ]

Remember that JUCE is [was] not free. Developers have to pay to be able to use JUCE GUI library for their GUIs. CLAP will make that irrelevant! That's fantastic!!!

Cheers!

 

Apparently CLAP is designed with more modern features than LV2. That being said starting from scratch is gonna make this a mid-long term project until it becomes stable. But it's very promising that it has the backing of some U-He and Bitwig developers.

KVR?! You good sir are a brave one. This goes for you:

Edited: you already came back? Give me back those 2 min of my time!! ... I need to switch from beer to tequila...

 

I've learned one more interesting thing from that thread - LV2 has JUCE support. I mean JUCE GUI library can be supplied with LV2 plugins for free since some time now. Well, CLP will be able to use JUCE for free, too. Gosh, if I live long enough, I might see VST becoming completely deprecated as an audio plugin standard. Interesting. One kinda get used to things after a while, especially after 25 years.

I've been using VST plugins since '97... a creepy thought entered my tiny mind - I could have the same genes as Keith Richards!

p.s. after so much damage I've been doing to my body throughout years, my liver is still doing incredibly well, according to doctors. I did have a heart failure, though. eh.

 

Or maybe: Freely Licensed Open Plugin. That would be a FLOP.

 

FLP for short? Already taken by Fruity Loops Project.

 

You mean I can relive my promiscuous 20s again. Oh WOW I really miss those many days & nights practicing the art of the
Ménage à trois!
I still don't know who came to the party with the clap that one night, but odds are it was Kate. That bitch as hotter than July!

 

I wonder why CLAP is better? Does anybody know?

Well I guess it's because a guy generally knows 3 day later.
Hey Kool Moe D.... Hit It!
Three days later, go see the doctor!

 

Visit the KVR thread and everything hmmmm could probably be a little more clear to you.
Otherwise, enjoy mate. I feel we're at the same "level". fucking saturday night. You mention some shit and I had it. Except heroin. OK, I don't use "uppers". Just anything that can sedate me to prevent me from killing my neighbours and make my apocalyptic, anticaptalist, antisocietal shit. [joking about neighbours, they're lovely]

 

Last edited: Mar 6, 2022

LV2 scored extremely low in developer surveys. And if a plugin format doesn't have buy-in from developers, it simply is not going to be used anyway. Developers that want to create LV2 plugins face a much higher learning curve than anything else out there.

CLAP already has developer buy-in at an early stage, that's what makes it exciting.

 

Like the VST3 SDK has a wrapper for VST2 plugins, CLAP has converters for VST2/3. That means you can wrap your VST2/3 plugins in CLAP. Also by checking u-He's MFM2.5 (it had a CLAP version), I found VST2 and VST3 exports like VSTPluginMain and GetPluginFactory. Internally all these use the same CLAP code with the converters and a DAW not knowing CLAP will load it just fine like a VST3 or VST2 depending on its extension and use it like one

 

They could make some free clap plugins to show the path.
But, aside of licensing questions, does clap format bring some advantage? Is the same plug-in lighter on cpu than if it was made in another format? Or any other advantage?
Until now U-He does not stands out for they concern about CPU hit, so i wonder if they took this in consideration this time.

 

According to the documenttation on the github repo, you can already enable CLAP support in Bitwig beta by manually adding the entry "clap : true" to its .json config file:

To enable CLAP, you need at least Bitwig Studio 4.2 Beta 1 and you'll have to add "clap : true" to:

• Linux: $HOME/.BitwigStudio/config.json
• macOS: $HOME/Library/Application Support/Bitwig/Bitwig Studio/config.json
• Windows: %LOCALAPPDATA%\Bitwig Studio\config.json

 

The biggest technical advantage is that the API is lightweight C, meaning you could theoretically build bindings for any other programming language out there. Most can do FFI in C, whereas, say AU or VST is tied to C++. So CLAP is better suited to language interop.

 

I've heard they are renaming Hive too by taking off the e at the end!

 

Technicalities aside let's not forget the number one reason: save money from VST licenses

 

Exactly. That way plugins can be cheaper, or at least there will be more money for the developers left. Either way is good. Win-Win.

Not to mention it will be much easier to make quality, more stable and compatible, freeware plugins with CLAP and JUCE. Golden!