CLAP... thoughts?

[beely]

Don't think AAX itself has any problems with ARM. It would be PACE holding back AVID in this case.

As I understand it, the entire Pace toolkit is ARM native now, so I'm not sure why Pace would be holding Avid back. Could you explain what you mean here, as I might be misunderstanding something..?

[Urs]

I wrote a lengthy reply to the question of "development effort" and "cost", but then I realised that's better suited for the Dev forum than Instruments.

In short: We did go for CLAP exactly for the reason that AAX/AU/VST2/VST3 are not "in sync" with host/OS/CPU updates. Our concept for CLAP is to be able to independently update either of these as they become available over time.

I'll post that slightly longer version in the Dev forum some time later, if anyone is interested.

[AdvancedFollower]

Seems interesting but I'm not going out of my way to try it e.g. by switching DAWs. If it becomes big enough I expect all major DAWs to support it eventually.

[DNnX]

Steinberg feels safe until CLever Input Output is announced

[PeterP_swe]

Additional APIs or platforms generally add some bulk short-term workload as you add support and then some long-term workload when you need to fix things that break.

On the plus side, if Avid actually adds CLAP support, developers can eventually drop AAX, so the number of supported formats would stay the same.

AAX still isn't M1/X/2 native AFAIK, so maybe the reason Avid are interested is because CLAP codebase is (and has no platform OS specific dependencies) and it will be less work for them to add support than to update and continue supporting AAX.

I wonder if Avids interest has something to do with Epic and the Unreal Engine. If CLAP manages to grab a foothold in the games industry then I can see why companies with a lot of investment and footprint there would be interested.

[fisherKing]

i certainly have no problem with the idea, just wish there was a uniform standard. but apple (for example) is not going to budge on it's AU format, and as a longtime logic user, am not going to abandon the platform.

still, as we've seen, multiple standards can co-exist...

[dionenoid]

Yay. Another CRAP thread. We now have a couple in every subforum.

[noiseboyuk]

i certainly have no problem with the idea, just wish there was a uniform standard.

[fisherKing]

i certainly have no problem with the idea, just wish there was a uniform standard.

funny, true,, not funny....

[pdxindy]

i can only say i am following it. see what it brings, for me, of course.... per voice parameter modulation, well... me like (the CPU overhead??).... optimized bidirectional communication, finally! and optimized host - plugin - multihread...

Who knows what it will bring for Reaper and other hosts...

As a Bitwig user who primarily uses u-he synths, I find the per voice parameter modulation to be one of the best improvements ever!

Been using it a lot for some days and am not noticing significant CPU overhead for my uses. It adds so much to my favorite synths!

[fisherKing]

"i've read thru these ancient scrolls, and the world has 6 minutes to live unless we follow these instructions..."

"tell the world NOW"

"i'm getting it translated into every language; it should be ready in about 7 minutes...."

[Urs]

i certainly have no problem with the idea, just wish there was a uniform standard.

Minus927.jpg

[Held]

XKCD 927 mentions character encodings which is actually an example when a new standard improved the situation. Encoding text in any language other than English was a mess and there were a bunch of incompatible standards until Unicode came along; A universal standard that covers everyone's use cases. Who would have thunk.

And CLAP has the potential to do the same thing. It might replace AAX, so the number of format will stay the same. VST2 is on the way out, so the number of formats will be reduced. And it works well with MIDI which Steinberg is actively trying to prevent in VST.

So yeah, a new standard can absolutely improve things. Not that most existing plugin formats are a standard anyway like Urs already mentioned.

[zvenx]

Hmmm.. I know you have been dying to drop that one Urs

I would argue something like Microsoft Word (and RTF) is an industry standard.

I am curious where you got the definitions that you are using from.

rsp

[fisherKing]

Hmmm.. I know you have been dying to drop that one Urs

I would argue something like Microsoft Word (and RTF) is an industry standard.

I am curious where you got the definitions that you are using from.

rsp

what's great about a lot of this is; regardless of platform, a jpg is a jpg, a pdf is a pdf (etc etc). and apple's pages (for example) can open & export to word. i use affinity photo for photo editing, and can open (and export to) a photoshop file.

the audio plugin situation is not like this, of course. but i'm just gonna go back to making music, and let the developers sort it out (go for it, urs!).