About CLAP

[digitallysane]

(the name is the least important thing about it atm. As long as people get upset about it rather than the interface and concept itself, I'm totally happy. I guess a nice side effect is that it keeps people occupied channeling destructive energy on unimportant things while elsewhere other people make the actual decisions, bringing things forward)

If you couldn't be bothered to even set a name that has some quality, the same can be inferred about the rest of the work on the project.
The name is one of the very few things the project has at the moment, and what it transmits about the project is neither quality, nor pragmatism (as correctly pointed in other posts above re: ease of finding info thru a web search etc).
Same goes for "clever" replies/posts when people point out a problem with the project right at its start.

[MirkoVanHauten]

Q.E.D... If the only thing known to you is the name, you've already did a bad job on researching. There are plugins known using it, DAWs known supporting it, there's a public codebase known, there are posts over posts about the goal of CLAP and what it already does different to improve the plugin format, and even discussions and explanations about the name... I wonder what would come up if I search for AAX or what quality AU does transport. But now I get why ProTools is responsible for more hits than Fruity Loops

[Funkybot's Evil Twin]

I'd argue if the biggest complaint about CLAP is the name, then they're actually doing something right.

[digitallysane]

I'd argue if the biggest complaint about CLAP is the name, then they're actually doing something right.

The biggest complaint being about the only (or one of the very few) thing(s) publicly known about the project, yet. An excellent start!

[sjm]

(the name is the least important thing about it atm. As long as people get upset about it rather than the interface and concept itself, I'm totally happy. I guess a nice side effect is that it keeps people occupied channeling destructive energy on unimportant things while elsewhere other people make the actual decisions, bringing things forward)

I would respectfully disagree that "making it easy for users to search" is an unimportant consideration. I'd say that that sort of consideration should be important (why isn't it?). Is it the most important thing? Probably not, but that doesn't mean it isn't important, just less so than other things.

If you take an approach where only one thing matters, and all other considerations are trivialities to be ignored, you will go exactly the same route as VST. So yes, there are probably more important things than the name, but that doesn't mean the name is "unimportant". That's a logical fallacy.

It's not like there's a trade-off here either. Just call it something unambiguous (and inoffensive I guess) and move on to the actual important things. It would be a real pity if something so trivial comes back to bite us all in 5 years because people thought they knew better and didn't want to listen to legitimate concerns. I wonder if any of that sounds familiar...

[teilo]

(the name is the least important thing about it atm. As long as people get upset about it rather than the interface and concept itself, I'm totally happy. I guess a nice side effect is that it keeps people occupied channeling destructive energy on unimportant things while elsewhere other people make the actual decisions, bringing things forward)

If you couldn't be bothered to even set a name that has some quality, the same can be inferred about the rest of the work on the project.
The name is one of the very few things the project has at the moment, and what it transmits about the project is neither quality, nor pragmatism (as correctly pointed in other posts above re: ease of finding info thru a web search etc).
Same goes for "clever" replies/posts when people point out a problem with the project right at its start.

Oh, grow up.

[digitallysane]

Oh, grow up.

Be clever.

[MirkoVanHauten]

Just call it something unambiguous (and inoffensive I guess)

Good luck dealing with this generation

[Funkybot's Evil Twin]

Names are the easiest things to criticique and/or make fun of and one of the hardest things to come up with. If you'd like me to prove this point, please post your name, any children's names, as well as pet names and I'll be happy to demonstrate. Regardless of whether you think it's a good name, I bet it stuck with you. And if so, maybe it's not so bad.

[DarkStar]

It’s defined in the README.md section, right under the ASCII image:

CLever Audio Plugin.

Oops, I see it now - the ASCII graphics distracted me Are they flowers or fat men with big belly buttons? (No offence)

[Urs]

Sorry, but this thread is about CLAP and u-he. I'm happy to lay out our reasons to follow this path, I'd even welcome technical or conceptual questions.

Please try to avoid all these unrelated issues, I don't really feel like having cumbersome arguments which don't help us or our user base. Everyone is of course welcome to open discussions in forums where they make sense, i.e. where it's easier for me to ignore them.

Addendum: I'll happily refer to this post viewtopic.php?p=8295983#p8295983 which is the third post in this entire thread. I have seen thousands of suggestions for better names, thousands of arguments for and against. If anyone wishes to continue the debate, I am the wrong person to address. Which I had hoped I had made clear on the day I opened this thread. And that's all there is to say about that in this forum.

[sjm]

I guess I'll stick to getting my condescending attitudes from Steinberg then...

[Urs]

I guess I'll stick to getting my condescending attitudes from Steinberg then...

Really?

There are people who are busy preparing open source projects, writing documentation, defining APIs, testing implementations or simply just financing the things that need to be done. If you want to be part of the decision making process I strongly suggest to become creative and actually contribute.

[jinxtigr]

By 2023, every Airwindows plugin will be available as CLAP natively in Linux, Windows, and Mac intel and native M1.

I made no such time-promise when I ported all the plugins to AU64, or to VST, or when I added LinuxVST, but this time I'm in touch with a community that's actively helpful for my poor old uneducated brain (Paul from the Surge Synth project glibly talks about writing a script and doing it with one click of a button. In fairness, he has such a script to get anything he likes from my VST2 codebase into Surge, but the VST2 codebase isn't my preferred codebase or the one I start with…)

[Urs]