sdk.steinberg.net

Do you use the VST3 WYSIWYG editor? Then you can use the UIViewSwitchContainer.

Yes there is, see the value-inset attribute or CKnob::setInsetValue().

Cheers,
Arne

Hi,
does the validator loads your plug-in?

Cheers,
Arne

Hi,
sure you can register your own custom view so that you can use it via xml.
See: https://steinbergmedia.github.io/vst3_d ... w_creation

Cheers,
Arne

Hi Chris, in VST3 an instrument declares all its changeable properties via parameters. In your case, you create a parameter for the damper pedal and you can use IMidiMapping to tell the host that this parameter should map to the damper pedal MIDI control change message. The host will then translate ...

For poly articulation see https://steinbergmedia.github.io/vst3_d ... ssion.html.

If the validator lists your plugin then you can use the validator to check if it can load your plugin by just calling "validator.exe $PATH_TO_YOUR_PLUGIN".

Hi,
you can use the validator example with the "-list" argument to step thru the code to see why it fails to load your plug-in.

Cheers,
Arne

Hi, your frustration comes from the misunderstanding that you can build MIDI plug-ins with VST. VST describes an audio plugin API. That you could misuse version 2 for building MIDI plug-ins was not intended. You need a MIDI plug-in API which does not exist across hosts. And for key switching support...

Why not describing the use-cases you want to implement which you are struggling with? The one use-case I can decipher from your rant is to talk with external devices. In this case the answer is, talk with the device directly. Then you can be sure that your messages are send to the correct device, no...