Call For Usage of Vendor Subfolders in CLAP Path

[FunkybotsEvilTwin]

As a matter of organization and courtesy, it would be nice if the CLAP spec called for Vendor subfolders within the CLAP plugin path. Some vendors do this, other vendors (Fabfilter for example), do not. I made the suggestion to Fabfilter but their response was 'we don't do this for any other format so won't for CLAP'. Understandable. But hence, why I think it would be good if the spec itself called for this. It's just a best practice type issue IMO.

Examples:
C:\Program Files\Common Files\CLAP\AudioThing
C:\Program Files\Common Files\CLAP\Fabfilter
C:\Program Files\Common Files\CLAP\U-he\

[abique]

I'm OK to encourage it, but not to make it a requirement.

[FunkybotsEvilTwin]

Thanks! Any enocuragement within the official docs/SDK would be welcome.

Whenever I go in my VST3 plugin folder via an Explorer window, it's a mess. Most plugins are in the root, with hundreds and hundreds there, but some plugins have individual folders, some vendors have folders, and if I've had to manually install a plugin, it can be anywhere (nothing you can do about users though). It would be best to avoid that with CLAP.

So any standardization or best practices that get called out in regards to file management would certainly be appreciated. In the short term, it may lead to issues with plugins currently installed in the root and updates going to a vendor sub-folder, but I think over the lifetime of CLAP, it would be a big benefit if vendors followed the encouraged approach. And the sooner the better.

Thanks!