u-he

TVbene · Post by **TVbene** » Sat Dec 18, 2021 6:12 pm

Could this also be implemented on iOS?

Urs · Post by **Urs** » Sat Dec 18, 2021 6:23 pm

TVbene wrote: Sat Dec 18, 2021 6:12 pm Could this also be implemented on iOS?

I honestly have no idea if that makes sense. It's certainly possible in some way, but I think iOS has a very established AU ecosystem that is hard to beat.

u-u-u · Post by **u-u-u** » Sun Dec 19, 2021 11:10 am

As VCV Rack is open source and they already did some work to make it work inside a plugin environment it should totally be possible to do an open source CLAP adapter for it, shouldn't it?

Edit: And I assume for Surge as well.

sagamusix · Post by **sagamusix** » Sun Dec 19, 2021 11:13 am

This is really great news. I'll look into implementing CLAP support in OpenMPT for the next major version update.

TVbene · Post by **TVbene** » Sun Dec 19, 2021 11:38 am

Urs wrote: Sat Dec 18, 2021 6:23 pm
TVbene wrote: Sat Dec 18, 2021 6:12 pm Could this also be implemented on iOS?
I honestly have no idea if that makes sense. It's certainly possible in some way, but I think iOS has a very established AU ecosystem that is hard to beat.

Thanks for the info. The hassle with iOS and plugins starts when you try to move projects to PC. Besides that AUv3 works really well, that’s true.

Tarnith · Post by **Tarnith** » Sun Dec 19, 2021 12:23 pm

Excited to follow how this develops.

Definitely piqued my interest.

BBFG# · Post by **BBFG#** » Sun Dec 19, 2021 4:22 pm

Inspired me to download the latest Ubuntu (I'm a few versions behind).
Really want to find more resources to read up on CLAP too. Not as a developer, but just to get into the gritty understanding of it.

Maybe please post links of places to start that? Still getting mostly hand clapper pad boxes and explanations of STD slang terminology.

Urs · Post by **Urs** » Sun Dec 19, 2021 4:28 pm

It's really just here https://github.com/free-audio and a lot of talk on various chat/conference servers.

The repository above has instructions on building a CLAP host and example plug-ins with Qt, which is easy to do on Linux, but may be a bit more advanced on macOS and Windows.

Also, if you look closely at some open source plug-in repositories on Github, preliminary CLAP support is shaping up!

sagamusix · Post by **sagamusix** » Sun Dec 19, 2021 6:36 pm

Is there a roadmap for documentation of the interface? There's quite a few headers to browse through, and while they seem to be nicely commented a separate, less code-centric documentation (maybe even with some small examples) that can be easily browsed would be great to have.

defiantnerd · Post by **defiantnerd** » Sun Dec 19, 2021 7:59 pm

if you're familiar with VST2 or VST3, it is quite straight forward. Currently, there is a lot of dependency in the examples and the examples are a bit too basic, but it looks promising.

The big pros are:
- C ABI
- sane Licence

The build process is pretty cumbersome right now, but that may improve (right now, it does not work at all).

karrikuh · Post by **karrikuh** » Sun Dec 19, 2021 8:12 pm

mystran wrote: Sat Dec 18, 2021 12:59 pm
ifso wrote: Sat Dec 18, 2021 9:28 amThe alternative of using a range between 0 and 1 lacks the ability to set automation points to a specific frequency.
Why would that be the case?

The spec defines value to string and string to value methods for the plugin to implement and specifies the host should call these to convert. So as far as I can see, the raw value can be [0,1] and you can still parse "42Hz" into whatever normalize value it happens to map into (and the host can still show "42Hz" to the user even if the automation is acting on a normalized [0,1] range in some perceptually linear domain)...

...or am I missing something fundamental here?

I think a problem may still occur when loading automation data using normalized values. If the value range has changed in a new version of the plug-in, they will be misinterpreted (re-scaled to the new range).

Maybe a good intermediate solution would be to define the value range exposed to the host in an arbitrarily defined linear scale (but not necessarily normalized to 0..1). Such mapping would allow to change the min .. max range in a backward-compatible manner. E.g., a log frequency parameter could be defined as MIDI note number (but continuous), or number of octaves relative to 1 Hz or whatever. The value2text callbacks can still convert this to the desired plain Hz display.

Urs · Post by **Urs** » Sun Dec 19, 2021 10:12 pm

u-u-u · Post by **u-u-u** » Mon Dec 20, 2021 1:40 am

Also how to solve the problem of backwards compability for a stepped parameter?
E.g. a "Band type" parameter of an EQ plugin. If a value option is added or the order changes between two versions of a plugin there could be a mechanism which maps the old indices to the new indices. This way the host could adapt its automation curve accordingly.

bero · Post by **bero** » Mon Dec 20, 2021 1:46 am

As soon as I have time, I will port the CLAP headers also to Object Pascal and then add support for CLAP plugins to my own yet unreleased DAW, which has already long support for VST2.x and VST3.x.

baconpaul · Post by **baconpaul** » Mon Dec 20, 2021 2:03 am

u-u-u wrote: Sun Dec 19, 2021 11:10 am Edit: And I assume for Surge as well.

yup

u-he

KVR Audio

About CLAP