Common hosting API to implement as a hosting facade

[atsushieno]

Currently we state like "we don't offer a stable API yet, and you should use commonly used plugin frameworks like JUCE or LV2 API" which covers huge amount of existing plugins that I have access to sources (OSS). Hosting part is however not much. We do not have LV2 hosting adapter (i.e. treat AAP plugins like LV2 ones) and I'm not sure if it is even doable, considering that we need some metadata (*.ttls). And "use JUCE" is often unacceptable for host developers (at least licensing wise).

I'm not sure what would be feasible. Supporting CLAP for hosting is an idea. I thought it involved too much host-plugin interactions that are not cost-free on Binder-based AAP land, but it seems RT-hard interactions seems to be done in the event stream.

It is okay if it works only as an API facade for hosting (i.e. what we need to implement is CLAP "plugin" API). Internals can remain as is.

[atsushieno]

RT-hard interactions seems to be done in the event stream

This is partly true but not overall, e.g. when they use thread-pool extension (involves bidirectional function calls within an audio processing call).

[atsushieno]

I had a quick review on clap-wrapper, and figured that it is not in real world use (much?) yet. I cannot find any single project that makes use of it. We'd wait for a while.