Studio - Register Instrument As Plug-in

This sub-menu is used to install plug-ins for the currently selected instrument(s).

•	All Plug-in Formats - install a plug-in for each selected instrument for use with all supported plug-in environments.

•	VST3 - create a plug-in for each selected instrument for use in Steinberg's VST3 environment. Any application supporting VST3 will be able to store and restore SysEx for this instrument as well as edit it (if supported).

•	VST2 - create a plug-in for each selected instrument for use in Steinberg's VST2 environment. Any application supporting VST 2.3 or 2.4 will be able to store and restore SysEx for this instrument as well as edit it (if supported).

•	MFX - create a plug-in for each selected instrument for use in Cakewalk's MFX (MIDI Effects) environment. Any application supporting MFX will be able to store and restore SysEx for the instrument as well as edit it (if supported).

•	All Plug-in Formats - install a plug-in for each selected instrument for use with all supported plug-in environments.

•	AU - create a plug-in for each selected instrument for use in any host that supports Apple's AU plug-in format including Logic and Performer (AU plug-ins must first be downloaded, see below)

•	VST3 - create a plug-in for each selected instrument for use in Steinberg's VST3 environment. Any application supporting VST3 will be able to store and load SysEx for this instrument as well as edit it (if supported).

•	VST2 - create a plug-in for each selected instrument for use in Steinberg's VST2 environment. Any application supporting VST 2.4 will be able to store and load SysEx for this instrument as well as edit it (if supported).

AAX: AAX support only requires a single plug-in. The single plug-in supports all instrument modules currently installed in Midi Quest regardless of whether they are installed in the Studio or not. As a result of this AAX feature, it is only necessary to install the AAX plug-in once and all available instrument modules will be supported. If there is an installed instrument which is not being used by the stand-alone version of Midi Quest and it should also not be displayed as an AAX plug-in option, the instrument's .ini file in the Instruments folder must be deleted. Pro Tools should not be running during the management of AAX instrument modules in Midi Quest as it can result in the failure of all related AAX plug-in operations

VST2: When installing VST2 plug-ins, Midi Quest Pro automatically creates an associated .vstxml file. vstxml files are read by Cubase and used to provide an enhanced VST parameter including extended parameter names and actual text or numeric values instead of a simple value between 0.0 and 1.0.

If you are using a VST2 host other than Cubase, vstxml files are ignored. To control whether vstxml files are created or not see Studio Preferences.

Download AU Plugins...: This is a Mac only option. Apple has radically changed the rules around creating and using AU plug-ins. As a result, Midi Quest Pro is no longer able to create AU plug-ins based on installed instrument modules as it has with previous versions. With Midi Quest 13 Pro, all 1000+ AU plug-ins are pre-created and must be downloaded individually. To download an AU, select the instrument module in the Studio Window, from the menus choose "Studio / Install Plug-ins for / Download AU Plugins...". This will download the AU plug-in. You can then choose "Studio / Install Plug-ins for / AU" to install the plug-in to the correct location.

If there are any issues downloading the plug-ins from within Midi Quest, the plug-ins can be downloaded and installed manually. The path you enter in the browser looks like this:

https://soundquestwebfiles.s3.us-west-2.amazonaws.com/AUPlugins/[INSTRUMENTNAME].pkg.zip

where [INSTRUMENTNAME] is replaced by the name of the instrument you want. In addition, there are two special modifications: a) any space in the name must be replaced with “%20” and, b) any "+" character must be replaced with "pl".

For example, to download the Korg EX-8000, [INSTRUMENTNAME] would be “Korg%20EX-8000” so the full path is:

https://soundquestwebfiles.s3.us-west-2.amazonaws.com/AUPlugins/Korg%20EX-8000.pkg.zip

Yamaha DX7: https://soundquestwebfiles.s3.us-west-2.amazonaws.com/AUPlugins/Yamaha%20DX7.pkg.zip

Alesis QuadraSynth S4+ Mod: https://soundquestwebfiles.s3.us-west-2.amazonaws.com/AUPlugins/Alesis%20QuadraSynth%20S4pl%20Mod.pkg.zip

2.	Display the Studio/Install Plug-ins for sub-menu and select which environment(s) to create a plug-in for

3.	For Windows, the OS will ask for confirmation to run "MQSetupRegistry" to perform the operation

4. For Macintosh, the OS will request your password to confirm creation of the AAX plug-in(s)

If the plug-in installation process fails in Windows, please report the issue to Sound Quest so it can be addressed. However, it is possible to install plug-ins manually so it is possible to create the plug-ins yourself.

1. Go to the folder where Midi Quest Pro is installed. This is typically c:\Program Files\Sound Quest\Midi Quest 13 Pro\Win64. This is where the source plug-ins are located.

2. Copy the appropriate plug-in and paste it into the directory for its plug-in type. The default directory locations are:

3. For VST3 and VST2, rename the copied file to the instrument name. A VST3 for the Korg Kronos would be "Korg Kronos.vst3".

important! In most cases the instrument name on disk is the same as displayed in the Studio window (eg Korg Kronos). In a small number of cases where the name uses OS sensitive characters such as "/", you must use the file name and not the name displayed in the Studio window. For example, the 01/w as displayed in the Studio window is "Korg 01/W" but the instrument name on disk is "Korg 01-W". The plug-in must also be named "Korg 01-W" in order for it to function correctly.

Midi Quest Pro
Midi Quest
Midi Quest Essentials
Midi Quest one