CLAP... thoughts?

[Hanz Meyzer]

OMG Bazille, nice! Will turn it into an almost unlimited powerhouse.

[Echoes in the Attic]

Including Repro?

Not yet. We've added Bazille though.

Repro-5 uses its own dedicated voice management. It's some extra work to add polyphonic modulation to Repro-5, which we'll do once our implementation is production ready in the voice management that Ace, Bazille, Diva and Hive share.

Repro-1 is going to be clap too right? Even though it’s mono, that would still be cool to be able to use Bitwig modulation without the knobs being automated.

[chk071]

Isn't RePro-1 and RePro-5 the same synth?

[EvilDragon]

Two different plugins sold as a bundle. The synths themselves share the similar DNA but definitely have departure points.

[chk071]

It's likely that they, if anything, both get updated to CLAP though, right?

[Urs]

Repro-1 is going to be clap too right?

Of course. At the same time as Repro-5 naturally, when both of them are ready to go.

[pdxindy]

OMG Bazille, nice! Will turn it into an almost unlimited powerhouse.

Yes! There are a fair number of Bazille parameters that cannot be modulated directly. With CLAP most of those will be modulatable per voice using Bitwig modulators!

[10bd01]

How is adoption progressing on this?

[moss]

How is adoption progressing on this?

It is coming along nicely! I did several "CLAP News" videos if you want to follow the progress. The playlist is here:

[Urs]

How is adoption progressing on this?

Here's the news from two months ago...

https://cleveraudio.org/news/half-a-year-in/

[] Peter:H []

I think it would be fair to mention and strike out the misconception that CLAP means automatically more functionality in plugins.
The video of moss mentions VST3 note expressions which according to the video have not been implemented by many synth companies (btw why is that,why did companies didn't do it but now brag for per note stuff?). And the same "not implemented here" goes for CLAP. If companies just wrap stuff as-is it will stay as it is functional wise but with another ABI. Example is Vital is CLAP, but CLAP without an implemention of Voice Stacking. So actually as a end user I have a different installation location. I my self stick with VST3 here.
User should notice - CLAP does not automatically mean more functionality. About other aspects of CLAP I don't talk here...

[Urs]

We have to think in larger terms than just what's being ported from old to new. In 10 years most plug-ins will support features that CLAP has introduced first. Many of CLAP's features will be part of the common frameworks and thus available to anyone using these frameworks then.

For any dev who's fed up with "always the common denominator" might see a solution in CLAP. That is, CLAP is designed (by ABI, by license, by wrapper technology) to be used as an internal plug-in format from which others derive.

It does not happen within a few months though.

[Urs]

(I might also add, that plug-in formats which have become more restrictive over the years have slimmed down the common denominator... absence of full MIDI support for starters... thus some developers will go for CLAP just to preserve features that they have already had in other formats...)

[anttimaatteri]

as long as this whole vst installs mess is cleansed
vst2 32bit
vst2 64bit
vst3 32bit
vst3 64bit

i go for all of it.
one clap to rule them all

[jamcat]

Someone should develop a really essential suite of free MIDI FX for CLAP. That would incentivise DAWs to adopt CLAP as a universal MIDI plugin format, which is something that doesn't really exist now, since VST3 can't/won't do it. The key is to fill a hole in the market.