PreSonus Studio One 7 apparently imminent

[lfm]

There is something strange about VST3, and many developers have problems with it.
- seems to be many ways to do the same thing, like multi out VST instruments

I had issues in Sonar and StudioOne 4.x with Bluecat Audio Patchwork
- Sonar says 2 outs, StudioOne says correct outs but nothing happend when trying to activate second stereo out
- and not until v2.47 of Patchwork it worked in Cubase

Talking to Bluecat devs they said something about busses and stuff, not sure what the choices are.
- seems much more complicated than VST2

Patchwork VST2 works fine though so staying on v1.74 on that since no problems.

But with Spitfire Audio Eric Whitacre choirs Sonar gets VST3 and all outs. No problems at all.
- so Spitfire do what Bluecat cannot

Since we can expect Steinberg to drop VST2 alltogether for Cubase first of all, and good reason to not use Cubase, I think.

So CLAP could be welcomed to be new standard, if it actually works and is accepted everywhere.
- but sceptical to volunteer based products that just stop development at some point
- I had with version handling software like Bazaar that was just dropped, download software like youtube-dl that was replaced thankfully by yt-dlp, but no guarantee that happends.

Don't know if any fees anywhere for CLAP, but might stand a better chance if there are, so developers can be paid, doing fixes and maintenance.

[audiojunkie]

(Um is there some controversy with CLAP that I'm not aware of?)

Other than it not working?

Just because Presonus’ implementation has some bugs doesn’t mean all implementations are bad. It doesn’t mean the format is bad. It means that Presonus needs to fix their bugs. CLAP works great on several other DAWs.

But you know this already. You’re just wishfully hoping that it fails so that you can save face after bashing it from the beginning. CLAP isn’t going away. Steinberg made sure of that with their licensing agreements.

[audiojunkie]

a growing number of devs are so fed up with Steinberg that they’re willing to go through the hassle of supporting a new format [...] I don’t think I’ve ever seen a single dev say that they like VST3.

I don't know of a single dev who doesn't support VST3.
But hardly any support CLAP.

Those are the hard, stubborn facts.

It’s funny you should say that. Everyone felt the same way about VST v.1 TWENTY+ YEARS AGO. CLAP is being adopted SO much faster!

[teilo]

[Not feeding the trolls]

[Mr Arkadin]

[Likewise]

[gentleclockdivider]

a growing number of devs are so fed up with Steinberg that they’re willing to go through the hassle of supporting a new format [...] I don’t think I’ve ever seen a single dev say that they like VST3.

I don't know of a single dev who doesn't support VST3.
But hardly any support CLAP.

Those are the hard, stubborn facts.

VST3 came out 16 years ago , developers held on to the last moment to keep developing for vst2
Clap otoh is only a few years ..just give it some time

[qtheerearranger]

For those that don’t want to support clap…

Here’s a recent video published by one of steinbergs influencers. Notice how much steinberg wants us to be thankful for vst and the costs that go into updating it lol. Seriously so thankful for clap.

[dastewart]

Bloody hell! I was just curious to know if CLAP was more CPU efficient than VST for those plugins that support both, like the Fabfilter stuff.

Why on earth is everybody getting so hot under the collar? As somebody who knows nothing about coding for any of these formats (yes feel free to quote me on that) VST3 and VST2 both seem to work fine with Studio One. I have examples of both and don't notice a difference but choose to use VST3 where it's available simply because, numerically, VST3 is 50% better than VST2

[teilo]

Bloody hell! I was just curious to know if CLAP was more CPU efficient than VST for those plugins that support both, like the Fabfilter stuff.

Why on earth is everybody getting so hot under the collar? As somebody who knows nothing about coding for any of these formats (yes feel free to quote me on that) VST3 and VST2 both seem to work fine with Studio One. I have examples of both and don't notice a difference but choose to use VST3 where it's available simply because, numerically, VST3 is 50% better than VST2

Because for whatever reason, certain people are offended by the existence of CLAP, so the mere mention of it triggers them. They've tried to explain why, but none of their answers make any sense.

Regardless, the answer to your question is: theoretically yes. Unlike VST, CLAP has a built-in host-mediated multi-threading model. This requires host and plugin support, because it allows the host to determine whether and when the plugin can multi-thread. This is necessary because otherwise multi-threading can have unintended consequences. Hosts generally need to run all the plugins on a track in a single thread. Some plugins can attempt to run multi-threaded on their own, which prevents the host from properly allocating threads in an intelligent manner. Host-mediated multi-threading solves this problem.

Bringing this back around: Presonus has been very tight-lipped about their CLAP implementation, and it is clear they have bungled it. Not only do we not know which CLAP features they support, but some CLAP plugins that work just fine everywhere else fail in S1, or crash S1 entirely. The many other CLAP hosts have not had this problem, so it seems to me that the S1 CLAP support was rushed. (Those other hosts being: Reaper, Bitwig, FL Studio, MultitrackStudio, Mulab, Qtractor, Anglang, EXT64, Zrythm, and a few other obscure hosts).

EDIT: Good lord, they've screwed this up so bad. U-he plugins load, but as soon as you play a note, S1 crashes. It's like they hired an intern to implement CLAP support, and did no code review or testing.

[vurt]

Guys, just don't feed the troll.
It's clear he has some (very weird) issues. Let's keep on topic.

we are not feeding him, we are poking an old wound, to make it fester.

[jamcat]

a growing number of devs are so fed up with Steinberg that they’re willing to go through the hassle of supporting a new format [...] I don’t think I’ve ever seen a single dev say that they like VST3.

I don't know of a single dev who doesn't support VST3.
But hardly any support CLAP.

Those are the hard, stubborn facts.

VST3 came out 16 years ago , developers held on to the last moment to keep developing for vst2
Clap otoh is only a few years ..just give it some time

Most major plugin developers adopted VST3 fairly quickly. But for those that didn't, the thinking was this: they supported VST, TDM/RTAS/AAX, AU. So every DAW user could buy their plugins and use them in their DAW of choice. There was no DAW that supported only VST3 and not VST2. So there was no impetus to support VST3. They weren't going to lose any sales over it. It's really that simple.

You'll notice that when Avid switched over from RTAS and TDM to AAX, all Pro Tools supporting developers jumped on AAX quickly. And they all soon discontinued TDM/RTAS support. This is what Avid demanded, and they backed it up in their own development cycle. Steinberg could have played hardball like Avid, and had the changeover completed in a few months. But Steinberg did no such thing. So some developers took a more "as needed" approach. Once Steinberg dropped VST2 support in Cubase, 15 years later, that finally put pressure on the few remaining holdouts to invest resources in porting to VST3.

CLAP is in the same position as VST3 had been. It's why there is only a slow drip of mostly indie developers supporting it. It's for the same reason that some held out on VST3: there is simply no incentive to support it. If a developer supports VST3, AAX, and AU, then they have every user of every DAW covered. They can sell their plugins to anyone. To force widespread adoption of CLAP, it would require some DAW to support only CLAP. And none are willing to do that. Not even CLAP's own developer.

The reason VST3 had much quicker adoption among the top-tier developers (who have almost all completely ignored CLAP so far), is because the VST platform was, and is, ubiquitous. Mainstream users used VST, and naturally wanted the next iteration of it supported. CLAP OTOH is pretty niche, and will remain that way. Like Linux.

[jamcat]

Bloody hell! I was just curious to know if CLAP was more CPU efficient than VST for those plugins that support both, like the Fabfilter stuff.

Why on earth is everybody getting so hot under the collar? As somebody who knows nothing about coding for any of these formats (yes feel free to quote me on that) VST3 and VST2 both seem to work fine with Studio One. I have examples of both and don't notice a difference but choose to use VST3 where it's available simply because, numerically, VST3 is 50% better than VST2

Because for whatever reason, certain people are offended by the existence of CLAP, so the mere mention of it triggers them. They've tried to explain why, but none of their answers make any sense.

teilo has it backwards. It's the CLAP boosters who get hot under the collar anytime anyone brings some reality into the conversation. It's because KVR is prone to some culty behaviour.

But the CLAP cultists are free to get back to us when Universal Audio, Waves, Arturia, IK Multimedia, Eventide, and Brainworx all start supporting CLAP. Though I doubt any of us will still be around for that day. Or that it will ever come.

[anttimaatteri]

new version looks good with the new bitwig/ableton style session view. dunno about the rest. if they have a midi capture its quite a good daw to buy for a new searching customer

[MirkoVanHauten]

So there's absolute no necessity to support CLAP because all DAWs offer other options, yet the users most popular DAWs and plugin devs are implementing it? If that doesn't sound like a win... We went from "in 2 weeks nobody will ever talk about CLAP anymore" and "fine, but the big players like FL Studio or Studio One will not adopt it", to a much quicker adoption rate than VST3. Including public statements about why they like CLAP, e.g. because it's a free and well thought format. Delicious. Kudos to Presonus.

[aMUSEd]

a growing number of devs are so fed up with Steinberg that they’re willing to go through the hassle of supporting a new format [...] I don’t think I’ve ever seen a single dev say that they like VST3.

I don't know of a single dev who doesn't support VST3.
But hardly any support CLAP.

Those are the hard, stubborn facts.

https://nakst.itch.io