MQ Importing SysEx and Midi Quest Files MQ_yes MQLT_yes MQLib_yes

 

Midi Quest for the iPad supports importing SysEx from standard file formats such as .syx and .mid as well as from Windows and Mac versions of Midi Quest.

To import SysEx into Midi Quest from a file, transfer the file so that it is accessible from the iPad. This can be via email, gmail, iCloud, DropBox or virtually any other app which is capable of exporting files to another app in the iPad. The export process varies by app but typically involves tapping an "Export" button which displays a pop-up listing the apps capable of receiving the selected file. If Midi Quest is capable of importing the file, it's icon will appear in the list of available destinations

In the example below, a .syx file has been transferred to iCloud and selected. Tapping the Export button in the upper right displays a list apps capable of receiving the file. Tap the Midi Quest icon to import the file.

iCloud Export

This import method applies to all of the various file types that can be imported by Midi Quest.

 

Import SysEx from .SYX Files MQ_yes MQLT_yes MQLib_yes
Import SysEx from .MID Files MQ_yes MQLT_no MQLib_no

Midi Quest can extract SysEx from both .SYX and .MID files. In either case, the instrument module that supports the SysEx to be imported must already be installed of the import will fail.

Midi Quest performs the import by performing the following steps:

1. It analyzes each SysEx message and finds the instrument which supports that SysEx
2. If it is successful finding a module then it creates a new instrument of that type in the Studio and copies the SysEx into that instrument.

Any additional SysEx in the file belonging to the same module will also be copied to that newly created instrument. This design allows a single .syx or .mid file to contain multiple SysEx messages from multiple instruments. As long as the requisite instrument modules are installed, Midi Quest will create the appropriate instrument and import the SysEx into it.

If Midi Quest doesn't recognize a SysEx message in the file, it is ignored and the app moves on to the next message. If Midi Quest isn't successfully importing SysEx from a file, it may fail for a number of possible reasons including the following:

Variably sized SysEx - most SysEx is of a fixed length, however some can vary in length. Midi Quest can't import SysEx that isn't a consistent size.
Unsupported instrument - If Midi Quest doesn't have an instrument module for the SysEx, it won't be able to recognize or import it.
Roland SysEx - Roland has designed an extremely flexible SysEx transfer system, which Midi Quest is typically able to import. However, its flexibility means that the same SysEx information can be transmitted many different ways. Occasionally across firmware releases Roland changed the way the same SysEx information is transmitted. Where we are aware of the alternates, Midi Quest supports reading the SysEx in its multiple forms, however, we are also aware that there may be variants which we are not aware of. For these variants, Midi Quest is not able to import the SysEx.

 

Import Midi Quest .SQS Files MQ_yes MQLT_no MQLib_no

Midi Quest for iPad is able to import Windows and Macintosh Midi Quest Set (.SQS) files. Each Set file is added to the current Studio in the iPad version.

note: ensure the Set's instrument module is installed before importing the file.

 

Import Midi Quest .SQC Files MQ_yes MQLT_no MQLib_no

Midi Quest for iPad is conditionally able to import Windows and Macintosh Midi Quest Collection (.SQC) files. Importing a Collection file will cause the current Studio to be closed and replaced by the new Collection. In addition, the Collection should only contain Sets. Importing a Collection containing individual banks or patches may cause the import to fail.

note: ensure the the instrument modules necessary to support the Sets stored in the Collection are already installed in Midi Quest.

 

Import Midi Quest .SQX Files MQ_yes MQLT_no MQLib_no

If you currently own Midi Quest for Macintosh or Windows, you may now be saying to yourself "I've never seen an SQX file" and you would be correct. To Midi Quest for iPad, an SQX is any individual Midi Quest single bank or patch file. On Windows and Macintosh these files all have their own unique extensions. There are hundreds of them including: bnk, pat, pch, vce, bk1, FnB. For any individual bank or patch file that is to be transferred to the iPad, first make a copy of the file and change the file's extension to .SQX. Transfer the file to the iPad and export it to Midi Quest.

On import, Midi Quest will find the instrument module to which the bank or patch belongs, create a new instrument, and copy the SysEx into the new instrument. If there is no instrument module matching the SysEx being imported, the import is canceled.

 

Install Midi Quest .SQZ Files MQ_yes MQLT_no MQLib_no

An SQZ file is how Midi Quest instrument modules are distributed. This detail is usually unimportant as Midi Quest has integrated facilities to download and install instrument modules directly from Sound Quest servers. If, for some reason, Midi Quest is unable to reach the servers directly, instrument modules had be downloaded directly using an ftp application such as Filezilla (https://filezilla-project.org) and the following connection information:

url: ftp.soundquest.org
username: MidiQuesti12@soundquest.org
password: MidiQuesti12.Download

Run the ftp application, log into the site above and download the required instrument modules. Transfer the files to the iPad using your favorite communications app and export the file(s) to Midi Quest. When Midi Quest receives an .sqz file, it will automatically decompress and install the instrument module.

 

Install Midi Quest .SQB Files MQ_yes MQLT_no MQLib_no

.SQB files are extremely rare, having only been used in Psicraft's M-Audio Venom editor. The files contain a subset of a Midi Quest Set (.SQS) file and are imported in the same way as a Set.