About CLAP

[Urs]

I don't think it applies either. I sure hope I can use the memes I have prepared for this.

My main point is that today's "standards" are actually mostly "platforms". Latter come disguised as standards, but they have strings attached.

[mystran]

My main point is that today's "standards" are actually mostly "platforms". Latter come disguised as standards, but they have strings attached.

I think I've said it before, but I feel like the reason VST2 ultimately "won" the previous round is precisely because it was closer to a standard API than a platform.

[ThomasHelzle]

Yeah, I also think that, while reinventing the wheel isn't too clever, we have much better wheels today than a hundred years ago. Only time will tell if CLAP will let us roll smoother and faster

[Urs]

Only time will tell if CLAP will let us roll smoother and faster

Well, if it's faster can literally be tested from today on as we're releasing two CLAP betas which take advantage of the thread pool feature. Our internal tests have been overwhelmingly positive in that respect.

Smoother will take time: CLAP is very strict about threading, and initially many plug-ins will run into asserts and crash. But once the threading issues are resolved, I'm 100% certain the CLAP plug-ins will run smoother in *any* format, since a major source of crashes in VST3 etc. are undocumented and unenforced threading rules.

[EvilDragon]

undocumented and unenforced threading rules.

Oh dear...

Also

<this post>

4.55 AM. I guess you haven't really slept, then

[Urs]

Yeah, was difficult... not sure if you are aware of what's coming... but it is coming.

[TENETfanboy]

Well, if it's faster can literally be tested from today on as we're releasing two CLAP betas which take advantage of the thread pool feature. Our internal tests have been overwhelmingly positive in that respect.

Smoother will take time: CLAP is very strict about threading, and initially many plug-ins will run into asserts and crash. But once the threading issues are resolved, I'm 100% certain the CLAP plug-ins will run smoother in *any* format, since a major source of crashes in VST3 etc. are undocumented and unenforced threading rules.

So as a Cubase user should I even care about CLAP? Or will it not be applicable to me?

[EvilDragon]

Yeah, was difficult... not sure if you are aware of what's coming... but it is coming.

I think I have an inkling...

[Urs]

So as a Cubase user should I even care about CLAP? Or will it not be applicable to me?

If you like what we do here, you can let Steinberg know that we'd love to collaborate with them on CLAP!

[Urs]

I'll let this thread slowly fade out... the whole discussion will move to a different level in a few hours... maybe better to do it outside our company forum.

[Urs]

u-he Betas:

viewtopic.php?t=582950

[prokoudine]

(Well, we had planned for LV2 support actually, but it looks like CLAP has more potential…)

If Anklang has an nicely designed abstraction layer, you should be able to add whatever Even LADSPA which you have an intimate knowledge of from your BEAST days

[Tim Janik]

If Anklang has an nicely designed abstraction layer, you should be able to add whatever Even LADSPA which you have an intimate knowledge of from your BEAST days

It is really the other way around. Implementing CLAP support means I have to put all the necessary abstractions in place. That's what I'm busy with this very moment

Regarding LADSPA, are there any plugins left, that do not exist as LV2 at this point?

[prokoudine]

It is really the other way around. Implementing CLAP support means I have to put all the necessary abstractions in place. That's what I'm busy with this very moment

Nice!

Regarding LADSPA, are there any plugins left, that do not exist as LV2 at this point?

I was going to suggest Barry's Satan Maximizer just for the fun of it, but no, it's ported. Honestly, everything worth porting has been available in LV2, sometimes twice.

[moss]

My little sum up if you do not want to read 53 pages