Standard for controller mapping to follow-up on CLAP?

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

CLAP is a great initiative and I'm wondering if an open standard for controller mapping could arise someday too. It is unlikely this will happen from the hardware manufacturer side since having this proprietary (i.e. NKS) is a selling point for them. But I think it is of the interest of plugin vendors, and users of course, to have controller's knobs and faders automatically mapped to the software they are using regardless of the brand of their controller and the software they are using. Of course this will not be magic but having some abstraction both on the feature side of the software (plugin, DAW) and some classification of the various available controls on the controller would enable a "best effort" automatic mapping without having to handle a database of all the possible controllers and plugins which is obviously a doomed approach.

Post

Hi,

There's a draft extension for "Quick Controls" in the CLAP Github repository:

https://github.com/free-audio/clap/blob ... controls.h

Generally feature requests are best posted there, or, if you don't want to get too deep into Github and stuff, simply send your requests and ideas via email to info@cleveraudio.org - which was set up to connect the musician/user side with the dev team (the developers at u-he that are involved with CLAP aren't KVR regulars, and I'm busy elsewhere, so I'd just relay things...).

Cheers,

- U

Post Reply

Return to “u-he”