Questions & Answers

Add support for CLAP (CLever Audio Plugin) plugin standard [Completed 7.0]

+112 votes
6,013 views
asked Jun 16, 2022 in Completed Feature Requests by duncanhamilton (260 points)
recategorized Oct 12 by Lukas Ruschitzka
CLAP is an open source, cross-platform standard with advanced features, such as polyphonic modulation. Early support for it has been given by u-he and Bitwig.It would be excellent to see this plugin format supported in Studio One, both for S1 users and to support the plugin development community.

GitHub page here: https://github.com/free-audio/clap

12 Answers

0 votes
answered Oct 12 by Lukas Ruschitzka (261,210 points)
 
Best answer
Completed in 7.0
+4 votes
answered Jul 1, 2022 by jesperjakobsen (270 points)
Things are beginning to accelerate regarding CLAP. Bitwig has support (beta). U-He, Audiothing and TAL have beta versions of some of their plugins out.
+6 votes
answered Jul 3, 2022 by Photontic (1,140 points)
It should be noted that PreSonus is already listed as one of the developers who are evaluating this new plug-in format.

Reference: https://u-he.com/community/clap/ - scroll down to the bottom for the developer list.
+5 votes
answered Jul 25, 2022 by Scoox (17,270 points)
edited Jul 25, 2022 by Scoox

Dang! Polyphonic modulation?? This CLAP thing looks very good. For anyone wondering, here is an official overview video. Very impressive. Being an open standard, it has a chance of taking off, as long as enough DAW and plugin developers decide to support it. Obviously Steinberg and Apple, respectively, will not cooperate, at least not initially. Pro Tools? Dunno. I see no point in all these standards that fulfill the same task to varying degrees. Would be better to have one to rule them all.

I'm guessing supporting some of these features will require effort on both sides, the DAW and the plugin developers. Maybe Steinberg and Apple will updated their respective VST and AU standards to copy some of the features of CLAP. Either way, a bit of competitive innovation always means the users win.

+4 votes
answered Oct 17, 2022 by webhamster (2,130 points)
A very needed improvement over current plug-in formats
+3 votes
answered Dec 23, 2022 by alpatemrah (600 points)
I think the biggest feature is that it has better multithread support. Most modern computers are multicore and we have to rely on workarounds like audiogridder to utilize our idle processor cores.

Clap seems to bring a solution to this problem and I would really want to take advantage of this.
+2 votes
answered Jan 22, 2023 by alexkyrlis (1,050 points)
This is simply a must-have. Better sooner than later! Be the first major DAW to support it!
+1 vote
answered Feb 19, 2023 by wikter (380 points)
edited Apr 2 by wikter

I've already found FREE plug-ins not available in VST that works fine under CLAP inside Bitwig.
Luca from Audiority announced this on KVR. That means VST2 should be terminated on all new DAW developments, that may include Studio One V7. That means most of my plugins should be wasted on my next S1 update. Really upsetting. Please, read this thread in KVR about the Steinberg statements.

Hi guys,

looks like Steinberg terminated all previous agreements that will allow us developers to build VST2 plugins. The new agreement is here: https://github.com/steinbergmedia/vst3s ... eement.pdf

and a Dev forum thread we came across: viewtopic.php?t=508845&start=420

I don't know how many of you is still using VST2 as a format but, at this point, we will be forced to not include this format with the next updates and new products.

Luca

+2 votes
answered Sep 26, 2023 by Koldunya (420 points)
maybe this is coming soon? Bitwig just announced they and PreSonus came up with an open DAW file format, DAWproject.

https://www.bitwig.com/stories/bitwig-and-presonus-are-making-it-easy-to-share-projects-between-programs-271/

Here's to hoping.
+2 votes
answered Dec 21, 2023 by amyyue (310 points)
All FabFilter products now support CLAP!
0 votes
answered Apr 2 by wikter (380 points)
Now that Steinberg has announced the END of VST2 licenses, may be the moment to evaluate the chance to lose compatibility with hundreds of VST2 plugins that were never ported to the VST3 PROTOCOL. Shame.
0 votes
answered May 8 by fransvannispen (5,910 points)
Nice. Yet another plugin format I need to keep on my system. AAX, VST, VST3 and AU alone was not enough!

It would be nice if projects could bridge between these, so opening a project which used the VST version can fall back to the AU or CLAP version if those are available. Then we can slightly migrate to 1 final format and do not lose project backwards compatibility.
...