Is there a plan to use the new CLAP "standard", which is used by VCV Rack 2 pro?

[TheStraight-I]

As it should be known meanwhile a new standard was introduced by Bitwig and u-he - CLAP.
VCV (the pro version) offers an awesome automation possibility, making each existing element (knobs, sliders, buttons) fully DAW-automatable.
As CV-"automation" is no real convincing way of automation (because of its known limitation) and... the usage as DAW plugin makes a good automation capability a must (in my eyes in each case) this would be an important question.

I'n currently not much known to VCV Rack... but in Bitwig automation for me is absolutely essential.
And because of the character of modular systems and their "definition" there should be a lot to be automated. Moreover one should keep in mind, that for sessions automation is a mandatory requirement, because nobody is able to fumble with a mouse at some knobs or sliders. That's (the accessibility for automation and assignment) the reason why I have kept distance to virtual modular systems until I heard of the - obviously meanwhile working - VCV Rack2 pro which uses the - allegedly - for automation very well suitable CLAP standard... and because CLAP is told to be open source as well....
Are there any plans?

[dromer]

This is not really a question for Cardinal, but for the framework used to create the plugin -> https://github.com/DISTRHO/DPF
However the answer is currently "maybe". It will depend on available resources (time + money) and these may come at some point. No time-line currently available.

Btw what "known limitations" are there to automations using CV that you are hinting at? Please be more specific as "reading between the lines" is not something you can expect from others on the internet. Currently we also have 24 parameters that you can use for automation in your DAW. Having personally used Cardinal extensively for many projects I've never gone beyond even half a dozen of parameters for any given patch. So please show us an actual use-case where you have to go beyond this limitation.

Also, Rack2Pro does not use CLAP at all, it's only available in VST2 format. So I'm not sure where you are getting your information from ...

Fact is that fully utilizing CLAP means yet another divergence in features from other formats, this means the "compatibility matrix" grows with more columns and rows, making it even harder to properly support all the things. This is just a bad tactic for creating stable software across operating systems and plugin hosts. So even if CLAP would be introduced in DPF it would likely stick to feature parity with the other standards. (aka: don't expect polyphonic automations any time soon)