MQ Set Preferences (Options Menu)


These options control the display and operation of the Set windows.



Check this option to enable program wide support for Synchronization on a per Set basis.

For more information on Synchronization, please see the Set chapter.


Create modal patch name files

Midi Quest Pro only

A number of the patch name formats, including Steinberg's patchscripts, Cakewalk's .ins files, and the standardized midnam xml format support storage of patch names by mode because some companies, Korg as an example, support identical bank select values in more than one mode. Sending a bank select and patch Combi mode will select a Combi. Sending the same bank select and patch while in Program mode will select a Program.

With this option left unchecked, Midi Quest will produce a "flat" output where all banks are listed but when in a DAW, selecting a Program while the hardware is in Combi mode will result in the hardware actually selecting a Program - which was not the intention.

With this option checked, Midi Quest will produce a modal output where there is a unique output for each of the performance modes that the hardware can exist in. For Korg, this would typically be: Program, Combi, and Song, with the Kronos adding "Set List" as well. With modal output, you start with the patches available to the currently selected mode and make a selection.


Create ProTools compatible midnam Files

Midi Quest Pro only

In order to create midnam files that display correctly in ProTools, it is necessary to store the name information in a particular way. While meeting the midnam standard, there is an unusual requirement for repetition of information that is not required by other applications that use the xml midnam standard. If you would like Midi Quest to create midnam files for ProTools, check this option. If you are using a different sequencer then is it recommended that this option be left unchecked.

This option appears to now apply only to older versions of ProTools. Current versions of ProTools should properly handle the standard output.


Cubase version

When working with a Cubase DAW, setting this parameter to the appropriate version number allows Midi Quest to start the patchscript creation in the correct default folder.

Particularly on Windows, Cubase uses a rather obscure directory/folder location to access patchscript files. If the patchscript is not created in the correct folder, it will never be made available as an option in Cubase when assigning a patchscript to a track.


Follow Automation

Midi Quest Pro only in plug-in Preferences

Follow Automation is checked by default. As automation events occur in Midi Quest, the editor that the events are associated with is automatically displayed. In most situations, this is the preferred operation because it ensures that the instrument is in the correct mode to receive SysEx parameter update messages and it works well with mono-timbral instruments.

However, if you are working with a multi-timbral instrument where Performance information and the underlying Patches can all be edited simultaneously in real time (such as most Roland workstation synths starting with the D-series), then having editors auto-switch is not ideal and will interfere in the recording of multiple passes of automation. In this case, this option should be unchecked. The advantage is that you will be able to switch between editors and overlay automation without Midi Quest switching windows when existing automation messages require output as SysEx. The downside to this mode of operating a plug-in is that you must ensure that the instrument is in the correct (Performance) mode as the editor may not place it there.


Available in:

Midi Quest Pro


Midi Quest


Midi Quest Essentials

CheckYes(supports a subset of these parameters)

Midi Quest one

CheckYes(supports a subset of these parameters)