CLAP 1.0 betas for ACE, Diva, Hive, MFM 2.5

[xtreme sounds]

will this new format auto assign parameters to Bitwigs device page panel? Im still not quite sure the differences here on modulation. Couldnt Bitwig already modulate several different parameters?

[xtreme sounds]

Can Apples Auv3 format be converted easily to the CLAP format? Might be worth looking into for ios developers.

[baconpaul]

Congrats Urs! It was a pleasure working on this with you!!

[webhamster]

Wauw, amazing! Thank you so much for developing this.
Is there a list of developers working on this or are interested in it?

The only things I don't like that much is the name. It sounds great, but makes it impossible to do a Google search.

[baconpaul]

will this new format auto assign parameters to Bitwigs device page panel? Im still not quite sure the differences here on modulation. Couldnt Bitwig already modulate several different parameters?

Automation and Modulation are separate things

Bitwig could (as can all hosts) automate a parameter. That is the DAW can take the same action as changing the dial - monophonically modify the value of a setting in your patch.

Modulation is something else; it indicates a temporary change. Just like an LFO in surge doesn't actually wiggle the pitch slider (but does modify the pitch you hear), neither should a modulation. So CLAP introduces two channels for change, the "automation" change and, if a plugin and host choose to support it, a "modulation" channel. The intent is that "automation" messages would set your patch up and "modulation" messages would transiently, sample accurately, and immediately change the value of the *engine* but not of the *patch*. That's why we call it non-destructive modulation.

Once you have that, though, if the standard allows you to have the host understand the voice management in the synth (which CLAP does) you can do that polyphonically. That is, you have your filter cutoff at 440hz. If you automate that you are destroying your patch. If you monophonically modulate it you are not (your cutoff in your engine is 440 + mod-amount). But if you do it polyphonically each of those comes with a voice id.

This is how surge works as well as the u-he synths. And once you use it in bitwig, you sort of never want to go back.

[EvilDragon]

Is there a list of developers working on this or are interested in it?

Please see the main announcement: https://u-he.com/community/clap/

[Urs]

will this new format auto assign parameters to Bitwigs device page panel? Im still not quite sure the differences here on modulation. Couldnt Bitwig already modulate several different parameters?

There is a draft extension for auto-assignments to macro parameters. This is not yet fully tested, but I'm sure it'll happen in a few months.

Regarding Parameter Modulation (let's call it "PM" from here on), this is very similar to Automation. Automation is also possible with CLAP, of course, in the same way it ever was. PM however leaves the parameter itself untouched, it just temporarily adds or subtracts from it. Such that, if a DAW allows to draw a PM Curve (as opposed to an Automation Curve), once the Region with that curve is finished, the original parameter value is back.

I other words: How often have you automated some parameters of a plug-in in a project and then at some point wondered how to get back to your original setting? - I spoke to some people who have this very, very often. With PM this would be over and dealt with.

[zvenx]

....
I other words: How often have you automated some parameters of a plug-in in a project and then at some point wondered how to get back to your original setting? - I spoke to some people who have this very, very often. With PM this would be over and dealt with.

I have to admit this happens to me often. Have to ensure my automation goes back to 0.
rsp

[BSE|Milan]

Will CLAP allow faster modulation then +/- 25 hz ? or is that more plugin depended

[Lbdunequest]

Congratulations!

[EvilDragon]

Will CLAP allow faster modulation then +/- 25 hz ? or is that more plugin depended

Modulation is sample accurate.

[Urs]

The only things I don't like that much is the name. It sounds great, but makes it impossible to do a Google search.

Then let's get #CLeverAudioPlugin trending and link to cleveraudio.org as much as possible for SEO

[xtreme sounds]

will this new format auto assign parameters to Bitwigs device page panel? Im still not quite sure the differences here on modulation. Couldnt Bitwig already modulate several different parameters?

There is a draft extension for auto-assignments to macro parameters. This is not yet fully tested, but I'm sure it'll happen in a few months.

Regarding Parameter Modulation (let's call it "PM" from here on), this is very similar to Automation. Automation is also possible with CLAP, of course, in the same way it ever was. PM however leaves the parameter itself untouched, it just temporarily adds or subtracts from it. Such that, if a DAW allows to draw a PM Curve (as opposed to an Automation Curve), once the Region with that curve is finished, the original parameter value is back.

I other words: How often have you automated some parameters of a plug-in in a project and then at some point wondered how to get back to your original setting? - I spoke to some people who have this very, very often. With PM this would be over and dealt with.

Thanks I guess if I see some more demo videos showing what it was before and after CLAP I will get it.

[Urs]

Yes, modulation is timestamped, but it would be crazy to send a value per sample. A good update rate is "a value to ramp to every 64 samples", or about 800Hz for a sample rate of 44.1kHz. We have made good experience with this rate in many of our plug-ins.

For audio rate modulation > 1kHz there is the option to provide audio buffers with "CV" as content. We'll see if/how/when this gets adopted among plug-ins and hosts. We certainly have some things for ACE, Bazille and Repro in mind.

[xtreme sounds]

Will this new format help Uhe products not lose typing keyboard focus in Bitwig anymore?