defiantnerd

I agree with @abique, I would suggest using a reverse URI identifier. Try to be consistent, since the plugin_id is also being used to generate UUIDs for the wrappers.

How should compatibility be signalled?

We still need to extend the enum: ``` enum clap_plugin_state_context_type { // suitable for duplicating a plugin instance CLAP_STATE_CONTEXT_FOR_DUPLICATE = 1, // suitable for loading a state as a preset...

I am not sure if this is really a good idea since it is not officially recommended though one could argue that it might not affect our target application: https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-shell-setup-folderlocations-programdata...

Which compiler flags do we want exactly: - /W4 Enable warning level 4 or even /Wall? - /WX Treat warnings as errors -Wextra and -Wpedantic have no equivalent in Visual...

I have enabled them for a test and there are a few issues we need to solve first. Interesting enough, those issues should have been detected by GCC/Clang, too. ??

I've checked out the 1.2.0 version of the SDK and it requires(!) c++20 - I am not sure if we already want this, the runtime library is strictly tied to...

your project does not properly compile because it does not adding the VSTGUI path correctly. Use this diff: ``` diff --git a/CMakeLists.txt b/CMakeLists.txt index b97881d..d5e2b51 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt...

Oh, and I always recommend Xcode over Ninja, it is just less alien to the Mac platform.

I found the bug in Ableton :) Live does not recognize the VST3 calling sequence. I filed that as a bug at Ableton. The wrapper is updated accordingly. Nevertheless, some...