defiantnerd

`CLAP_PLUGIN_FEATURE_ANALYZER` is already mapped to `PlugType::kFxAnalyzer`: https://github.com/free-audio/clap-wrapper/blob/5ba58f16a7816085d46cb8b7bb40b1eb1d9561d2/src/detail/vst3/categories.cpp#L64 Do you mean it should be mapped to `kFx`? Actually, I am not sure. The question is two-fold: - Why is the VST3...

Hm, we will try to figure this out. In the meantime you can also implement CLAP_PLUGIN_FACTORY_INFO_VST3 where you can override all VST3 options, also the feature string.

ok, the VST3 SDK lists: ```c++ SMTG_CONSTEXPR const CString kFxAnalyzer = "Fx|Analyzer"; ///< Scope, FFT-Display, Loudness Processing... //... SMTG_CONSTEXPR const CString kAnalyzer = "Analyzer"; ///< Meter, Scope, FFT-Display, not selectable...

@mthierman there is a conflict left, it looks like there should be both upstreams should be accepted. Do you agree?

Hey, thanks for your input. I'll check it out tomorrow.

Hi, thanks for bringing up this issue. But this "fix" is at the wrong place. Actually, the wrapper relies on the VST3SDK function `str8tostr16` which is actually incorrect. We have...

You're right, @baconpaul - it is UTF16. I was under the impression they limit it to UCS2 because all their code does that (or even less). I am not sure...

I'd like to put that into proper util functions, add the caveats for the illegal codes and overflow, then we can add this to all other places we transforming u8...

Released in 0.11

> Hi @jatinchowdhury18 > > I have some questions with the interface. > > 1. Is this scratch memory thread-local? > 2. Can you get the scratch memory pointer from...