About CLAP

[Urs]

Hahaha, no, we have our own framework which is quite complex. But we will eventually try to get multitouch working. It's just not the total top priority atm, as we're doing CLAP, localisation, hardware accelerated UIs and so on...

[Offenz]

Will it be possible in the future to convert patches made using Bitwig Grid as CLAP format?
It appears that at least Bitwig devices are made in the same format as CLAP.

[teilo]

Will it be possible in the future to convert patches made using Bitwig Grid as CLAP format?
It appears that at least Bitwig devices are made in the same format as CLAP.

No. They are not the same format at all. Also, patches don't work that way. CLAP is a plugin format standard. Grid is a Bitwig-native modular device, or rather a whole interconnected ecosystem of devices.

[Urs]

Yeah well, as I said elsewhere, Grid is some kind of rocket science and space technology. They could probably make a Grid CLAP from it, but let's not give them ideas while we're still working on Z3.

[baconpaul]

1) Why was get_factory() introduced, i.e. what use besides `clap_plugin_factory* get_factory(CLAP_PLUGIN_FACTORY_ID);` is planned here?

We had initial thoughts about factories that let us bootstrap claps in converter contexts so if say a clap could also fully interoperate with a different format version of itself or with a different synths data there could be mapping factories. So like bitwig could load a clap of surge over an old track in non clap format using a mapping factory or surge could provide a factory to load tracks from similar synths. The idea didn’t develop enough for 1.0 so we removed those drafts and just have the single factory now

[FrettedSynth]

Look very much forward to CLAP success.
Not a developer but surely as a user.
OK is it Wednesday yet lol

[liquidsound]

9 minutes to Wednesday in Berlin...

[EvilDragon]

...but it's not work hours.

[FrettedSynth]

...but it's not work hours.

Party Pooper

[liquidsound]

...but it's not work hours.

At least a recorded message!

[audiojunkie]

Hello there! My write-up on CLAP, written before v1.0 was tagged on GitHub, is now out of the paywall at LWN. Enjoy! (Or not )

https://lwn.net/Articles/893048/

I’m honored to be quoted in your article!

For the record, I’ve been enthusiastically on-board with my full support of CLAP since those early pages. For quite a while, actually.

[Urs]

Something like 6-7 hours to go before we post betas here, something like 8 hours to go until we update our website.

I have prepared Venn diagrams, let artificial intelligence create answers to XKCD 927 and I'm generally in high spirits.

Bit restless tonight, hope I'll get another hour or two of sleep in once my brain stops farting.

[NAD]

There must be at least a few counterexamples to XKCD 927, maybe industrial stuff that most people have never heard of? And file formats, surely... Oh, how about UTF-8, does that count?

[ThomasHelzle]

Well, every now and then a new standard IS better or allows to do stuff more elegantly.
VHS was the standard, then DVD, then BluRay and UltraHD BluRay and streaming...
I don't think anybody wants VHS back desperately

The Atari was the standard computer for sequencing back in the day and it was great for the time, but I wouldn't want to exchange one and the fitting monochrome fishbowl-monitor for my current machine and 75" monitor

I'd say there are tons of counterexamples if one looks at the bigger picture, the annoying stuff is just the dozens of parallel things that basically do the almost same thing at the same time, like Amiga vs Atari, both of them left behind by evolution mostly, both needed at the time to find out where to go.

Who would have expected initially that Steinberg would manage to botch VST3 so badly that basically nobody wanted to use it for so long and that they would use thumbscrews instead of improvement to convince people?

I personally don't think XKCD 927 even applies...

Cheers and best of luck!

[mystran]

I wrote a long reply (that I decided not to post) on how XKCD927 doesn't really apply to either Unicode (solves a different problem than other character sets; other character sets tried to choose characters for a limited range while Unicode takes a range that's large enough that you just need to choose where you put the character, not what characters you allow) or UTF-8 (solves a different problem than other Unicode encodings, namely that of ASCII interop and compact storage for scripts that are mostly ASCII).

XKCD927 applies to multiple standards trying to solve the same problems over and over again. In case of audio plugins, there simply isn't a "no-nonsense" API with "no-nonsense" licensing terms, so I'd go so far as to claim there simply isn't another standard that tries to do what CLAP seems to be trying to do, hence XKCD927 is not necessarily relevant. Ultimately though, it'll be the market that decides .. but XKCD927 is not an absolute rule, it's rather more of a warning about avoiding additional standards unless they actually add some real value.