> what’s the point of a new standard when no DAW besides Bitwig supports it?
> Good. This is a space that could use a new, open standard. With Bitwig behind it, I’m paying attention now.
Never believe in the idea of the HN "hive mind" :)
To simplify things down to a single opinion for a population (or even a person) is reductionism.
One commenter is just looking at it from the perspective of the market at large and the other uses a niche DAW, looking at its value for personal use.
Even so, if it doesn't catch on more broadly there's a good chance it's not going to last. Hoping it makes it.
I think it's a fantastic and extremely welcome even if the name is somewhat unfortunate.
I've not really followed the industry, but my understanding is the controlling interests behind VST are unpleasant to work with for everyone involved - so this is a chance to build something better and in the open.
If CLAP can make porting straightforward while gaining sufficient traction among DAWs, I could see it succeeding.
The list of “Following companies and projects are already evaluating CLAP for their host and plug-in software” is pretty impressive and personally accounts for a large amount of my workflow. Hopefully it gets big enough for Native Instruments to implement, Kontakt could benefit significantly from some of the new features.
Given that the code for both lives in the same github account, I am hoping for 'Yes'
I'm also curious (if you're comfortable answering), were you involved with "design and implementation contributions by a group of commercial and open source audio developers from across our industry."?