VST 3 Interfaces
VST 3.6.14
SDK for developing VST Plug-in
|
MIDI Mapping Interface. More...
#include <ivsteditcontroller.h>
Public Member Functions | |
virtual tresult | getMidiControllerAssignment (int32 busIndex, int16 channel, CtrlNumber midiControllerNumber, ParamID &id)=0 |
Gets an (preferred) associated ParamID for a given Input Event Bus index, channel and MIDI Controller. More... | |
![]() | |
virtual tresult | queryInterface (const TUID _iid, void **obj)=0 |
virtual uint32 | addRef ()=0 |
virtual uint32 | release ()=0 |
Static Public Attributes | |
static const FUID | iid |
![]() | |
static const FUID | iid |
MIDI Mapping Interface.
MIDI controllers are not transmitted directly to a VST component. MIDI as hardware protocol has restrictions that can be avoided in software. Controller data in particular come along with unclear and often ignored semantics. On top of this they can interfere with regular parameter automation and the host is unaware of what happens in the Plug-in when passing MIDI controllers directly.
So any functionality that is to be controlled by MIDI controllers must be exported as regular parameter. The host will transform incoming MIDI controller data using this interface and transmit them as normal parameter change. This allows the host to automate them in the same way as other parameters. CtrlNumber could be typical MIDI controller value extended to some others values like pitch bend or after touch (see ControllerNumbers). If the mapping has changed, the Plug-in should call IComponentHandler::restartComponent (kMidiCCAssignmentChanged) to inform the host about this change.
|
pure virtual |
|
static |