Plug-in Setup Page (Settings Dialog)
The Plug-in Setup page is only displayed when Settings is opened from a plug-in.
The left column determines what events trigger a bulk transmit of the Set along with other trigger options.
There are an extensive list of options:
Components to Send on Event
When a Send Events condition is met as defined in the section above, the plug-in will transmit the specified Set components.
Check Edit Buffers to send Set components to temporary buffer areas in the instrument. For most instruments, these are the instrument`s edit and performance buffers.
Check Banks to send Set components that contain banks.
Check Global Memory to send Set components that are permanent memory in the instrument but are not banks. For most instruments this is a single SysEx type, the unit's Global or System information.
Checking all three items will ensure that all editable elements in the Set are sent. However, This will also take the longest amount of time so if sending buffer SysEx is sufficient, select just the one option.
To use the Korg M1 as an example, check Edit Buffers to send the Program and Combi edit buffers, check Banks to send the Program and Combi bank and check Global Memory to send the Global SysEx.
MIDI Event Routing
Host to Editor - when checked, all MIDI events stored on the Midi Quest plug-in track are sent to the editor for processing
Host to Editor MIDI Port - when checked, all MIDI events stored on the Midi Quest plug-in track are sent to the MIDI port assigned to the instrument
Depending on the capabilities of your OS and MIDI interface(s) you will have options as to how SysEx is stored and transmitted to your instruments.
For the Macintosh, it is recommended that MIDI events intended for the instrument should always be on a dedicated MIDI track that is routed directly to the instrument. The Midi Quest plug-in should then exist as an audio plug-in with the only MIDI events on that track intended for the plug-in and not the MIDI hardware.
For Windows, if you have MIDI interfaces with true multi-client capabilities (where a MIDI interface port can be open two or more times within a single process e.g. Korg Kronos) then the same recommendation applies as for Macintosh. Two tracks, a MIDI track for MIDI events intended for the instrument and an audio track for the plug-in where the only MIDI events are those intended for the plug-in.
For the two cases above, the Host to Editor option can be checked if the audio track contains MIDI events for the plug-in that are intended to automate the plug-in. The Host to Editor MIDI Port option should never be checked.
Given the situation where you are running Windows and your MIDI interface(s) can't be opened by both Midi Quest and the DAW at the same time, it is necessary to use the following configuration...
The MIDI ports required by the Midi Quest plug-ins must not be open in the DAW. This will allow you to open the ports in the Midi Quest plug-in. In this case, all MIDI events intended for the instrument must be stored on the Midi Quest plug-in track. Check the Host to Editor MIDI Port option so that the events are sent to the MIDI port. For this configuration, it is highly recommended that all automation be recorded as VST or AU automation and that the Host to Editor option not be checked.
Both Host To Editor and Host to Editor MIDI Port have an associated button Make Default. Press this button after changing this option if you want this new setting to be used as the default each time a new plug-in is created.
Host MIDI Ports
The Host MIDI Ports section will only appear when working in MFX and OPT plug-in environments in Windows.
These two parameters represent the MIDI ports available to the Midi Quest plug-ins as provided by the host environment.
Unfortunately, the names of the MIDI ports are not available to the plug-ins however it is critical that the correct MIDI ports be selected or MIDI events will not reach the destination instrument.