Source Window
|
Destination Window
|
Comments
|
Default
|
control keys
|
Operation
|
Bank Window
|
Bank Window
|
• | for 1 patch in a Bank, when dropped in the same bank, source is pasted, swapped, or inserted at the destination patch based on the setting in Options/Properties/Bank tab |
• | when dropped in a different bank, source is pasted or inserted at the destination patch based on the setting in Options/Properties/Bank tab |
• | for multiple patches: the selected Patches overwrite the selected Patches in the destination Bank |
• | if there are no selected patches, Patches are placed in empty locations in the bank |
• | if there are no empty locations in the bank and no bank elements are selected, no patches are copied |
The drag and drop facilities for internal bank and bank to bank transfer are greatly enhanced. Following are the available options:
Single Patch in Bank drag and drop in the same bank
Default Operation
|
Cmd
|
Actual Operation
|
Paste
|
none
|
Paste
|
Paste
|
CTRL
|
Swap
|
Paste
|
SHIFT
|
Insert
|
Swap
|
none
|
Swap
|
Swap
|
CTRL
|
Paste
|
Swap
|
SHIFT
|
Insert
|
Insert
|
any
|
Insert
|
Single Patch in Bank Drag and Drop to Another Bank
Default Operation
|
Cmd
|
Actual Operation
|
Paste
|
none
|
Paste
|
Paste
|
CTRL
|
Insert
|
Insert
|
none
|
Insert
|
Insert
|
CTRL
|
Insert
|
|
|
Editor Window
|
• | the first selected Patch is transferred into the editor |
• | the SysEx must be compatible to transfer |
|
|
Set Window
|
• | the entire destination Bank is overwritten by the source Bank |
• | if a Bank of the same type does not exist, the SysEx is ignored |
|
|
Collection Window
|
• | entire Bank is moved to the Collection |
|
|
Library Window
|
• | dialog is displayed to choose between moving all Patches or only selected |
|
|
Patch Zone Window
|
• | all of the Patches in the Bank are uploaded to the Patch Zone web site for inclusion in the Patch Zone collection |
|
Editor Window
|
Bank Window
|
• | the Patch overwrites the first selected Patch in the Bank |
• | the SysEx must be compatible to transfer |
|
|
Editor Window
|
• | the entire Patch is transferred from one Patch to the other |
• | the SysEx must be compatible to transfer |
|
|
Set Window
|
• | the Patch overwrites the identical Patch in the Set |
• | if there is no compatible SysEx in the Set, it is ignored |
|
|
Collection Window
|
• | the Patch is added to the Collection |
|
|
Library Window
|
• | the Patch is added to the Library |
• | the SysEx must be compatible with the Library to transfer |
|
|
Patch Zone Window
|
• | the Patch is uploaded to the Patch Zone web site for inclusion in the Patch Zone collection |
|
Set Window
|
Collection Window
|
• | an entire Set can be copied to a Collection as a unit |
• | click the mouse on the MIDI device image in the upper left corner of the Set |
• | hold the mouse down and drag the mouse over the Collection |
• | release the mouse and the entire Set is copied to the Collection |
|
|
Bank Window
|
• | the source Bank overwrites the entire destination Bank |
• | if the Banks are not of identical type, the SysEx is ignored |
|
|
Editor Window
|
• | the selected Patch is transferred into the editor |
• | for a successful transfer, the SysEx must be the same as in the editor |
|
|
Set Window
|
• | the selected elements overwrite the same elements in the destination Set |
• | if an identical element is not found in the Set it is ignored |
|
|
Collection Window
|
• | the selected element in the Set are copied into the Collection |
|
|
Library Window
|
• | if the SysEx is a Patch, it is transferred into the Library |
• | if the SysEx is a Bank, each Patch in the Bank is transferred into the Library |
• | the SysEx is only transferred if it is compatible with the Library |
|
|
Patch Zone Window
|
• | the Patch or Bank is uploaded to the Patch Zone web site for inclusion in the Patch Zone collection |
|
Collection Window
|
Bank Window
|
• | the source Bank overwrites the entire destination Bank |
• | if the Banks are not of identical type, the SysEx is ignored |
|
|
Editor Window
|
• | the selected Patch is transferred to the Editor |
• | for a successful transfer, the SysEx must be the same type as in the editor |
|
|
Set Window
|
• | the selected elements of the Collection overwrite the same elements in the Set |
• | if the identical SysEx is not found in the Set, it is ignored |
|
|
Collection Window
|
• | the selected elements in the Collection are transferred into the destination Collection |
|
|
Library Window
|
• | if the SysEx is a Patch, it is transferred into the Library |
• | if the SysEx is a Bank, each Patch in the Bank is transferred into the Library |
• | the SysEx is only transferred if it is compatible with the Library |
|
Library Window
|
Bank Window
|
• | the selected Patches are transferred to the library |
• | for a successful transfer, the SysEx must be the same type as the Bank |
• | the Patches are first added to selected Patches then empty Patches in the Bank |
|
|
Editor Window
|
• | the selected Patch is transferred into the editor |
• | for a successful transfer the Patch must be the same type as in the editor |
|
|
Set Window
|
• | the first selected Patch in the library is transferred to the Set |
• | there must be an identical SysEx type in the Set or the Patch is ignored |
|
|
Collection Window
|
• | the selected Patches are transferred to the Collection |
|
|
Library Window
|
• | the selected Patches are transferred to the destination library |
• | the SysEx is only transferred if it is compatible with the Library |
|
|
Patch Zone Window
|
• | the Patch or Bank is uploaded to the Patch Zone web site for inclusion in the Patch Zone collection |
|
Patch Zone Window
|
Bank Window
|
• | the first selected Patch is transferred to the bank |
• | for a successful transfer, the SysEx must be the same type as the Bank |
|
|
Editor Window
|
• | the first selected Patch is transferred into the editor |
• | for a successful transfer the Patch must be the same type as in the editor |
|
|
Set Window
|
• | the first selected Patch in the Patch Zone list is transferred to the Set |
• | there must be an identical SysEx type in the Set or the Patch is ignored |
|
|
Collection Window
|
• | the first selected Patch is transferred to the Collection |
|
|
Library Window
|
• | the first selected Patch is transferred to the library |
• | the SysEx is only transferred if it is compatible with the Library |
|
File Manager / Explorer
|
Set Window
|
• | if SysEx of the same type exists in the Set, it is replaced by the new file |
|
|
Collection Window
|
• | that element is added to the Collection |
• | MIDIX files are also added to the Collection |
|
|
Library Window
|
• | if the SysEx types match, the element is added to the library |
|
|
Background Window
|
• | the file is opened into its own window (Windows only) |
• | any MIDIX (.SMF) file is converted to a Midi Quest file and loaded in a SysEx Window |
|
|
Patch Zone Window
|
• | the Patch or Bank is uploaded to the Patch Zone web site for inclusion in the Patch Zone collection |
|
|
Studio Window
|
• | .syx files are analyzed to see if they contain SysEx for a loaded instrument module. If there is matching SysEx, a new window is created to store the SysEx and the data is copied in |
• | .mid files are analyzed to see if they contain SysEx for a loaded instrument module. If there is matching SysEx, a new window is created to store the SysEx and the data is copied in. |
• | .sqz files contain a Midi Quest instrument module. Dropping an .sqz file on the Studio window will install the instrument module and add it to the Studio. For the MacOS, if the instrument module is already loaded in the Studio, it should first to removed and Midi Quest quit and restarted before the updated module is installed. |
|
Right Click
|
|
• | right clicking in the Midi Quest frame window displays the MRU file list (Windows only) |
• | it also displays a list of desktop files saved in the Midi Quest Data directory (Windows only) |
|
|
|
|
|
|
|
|
|
|
|
|
|