MIDI Communication Errors (Common Errors)
These errors are all generated while attempting to either transmit or receive System Exclusive information. Before attempting to deal with the particular error, you should verify this information:
| 1. | Communications channels for data and instrument match. |
| 2. | SysEx communication is ENABLED for the instrument. |
(It is possible to shut off SysEx on many instruments)
| 3. | Check that the Patch Bay is properly mapped to the instrument. |
....When first starting with the program we strongly suggest bypassing the Patch bay
| 4. | The Patch Bay is NOT routing SysEx output from the computer back to the computer |
| 5. | All requirements & warnings in Fast Tips have been met. |
| 6. | Connect the instrument DIRECTLY to the computer. |
(ie. No merge boxes, mappers, Patch bays, etc. are connected)
| 7. | Retry the communication. |
If after checking all of these possibilities an error is still being generated, it will be necessary to check out the particular error. The "Possible Causes" listed below will not include those already covered!
ERROR! SysEx Missing Bytes!
This is probably the most common error and can result from a number of different problems including those unique to a particular computer.
Note: If you get this error after pressing the OK button while the number of bytes received in the MIDI I/O Window is 0, it is not a true SysEx Missing Bytes error. The error should pop up by itself after the program has requested data from the instrument and the instrument has transmitted data back to the computer.
On Windows systems, this problem can be caused by one of a number of possibilities:
| 1. | You are using old MIDI drivers for your interface which do not receive SysEx properly. Contact your MIDI card manufacturer to ensure that your drivers are up to date. (Particularly for Sound Blaster, Voyetra, MidiMan, and CMS cards.) |
| 2. | You have two Windows MIDI interface drivers installed in your which are both attempting to access the same MIDI interface. This is guaranteed to cause problems. Remove one of the drivers from the list and reboot your system. For example, you may have installed both the Music Quest MIDI drivers and the Roland MPU401 drivers for your Music Quest MIDI interface. This should not be done and you should remove the Roland drivers which are inferior. |
| 3. | Most 386SX systems do not run fast enough to receive large SysEx dumps in Windows 386 mode. Run Windows in Standard (Win /s) and this should cure your problems. An additional suggestion along the same vein is that on some PC systems we have seen improved interface performance on interrupts other than 2/9. Try setting up your interface on interrupts 5 or 7 and see if this improves performance. |
| 4. | A less common cause of this problem on PC systems is that there are two pieces of hardware attempting to use the same piece of hardware. The most common example of this is an MPU interface and a bus mouse both attempting to use interrupt 2 (the default for both pieces of hardware). You must change the interrupt on one of the two pieces (preferably the mouse). |
| 5. | A second cause of this problem is occasionally that the data inside your instrument is corrupt (damaged) and so it is not transmitted correctly. The computer will see this as an incorrect transmission. To test this problem, perform a complete memory reset on your instrument if this is possible and try the dump again. Alternately, attempt to download different types of data from the instrument to determine which data is corrupt. For instance, you may be able to save all of your Patches individually even though the Bank will not download as a whole. |
ERROR! No EOF transmission found!
This error is a result of the program receiving a MIDI dump which is larger than expected. This error usually occurs when the program requires the dump to be manually transmitted from the instrument and the wrong type of data is transmitted.
The error may also result from ROM upgrades made to an instrument. In this case the data transmitted may not match the format for which the program was tested. This usually requires a ROM upgrade to the instrument.
Finally, this error is also displayed when program has not received any data and "Finish" is selected in the MIDI I/O Window.
ERROR! Incorrect Company ID!
This error results from incorrect data being transmitted to the program. Check your system to ensure the correct data is sent.
Available in:
Midi Quest Pro |
|
Midi Quest |
|
Midi Quest Essentials |
|
Midi Quest one |
|
See also: Common Errors