DX Manager MIDI Troubleshooter
At some time or another you are likely to have problems getting DX Manager to "talk" to your synth.
Does your MIDI device look like this ?
This is a non-branded, low cost, Chinese made, MIDI cable usually found on E-Bay or Amazon. Unfortunately such devices either won't work at all with DXM or will only handle short MIDI messages like Notes.
DXM exchanges much longer blocks of data (sysex) with your synth which these devices can't handle due to various hardware problems - see this thread for more detail.
Note also that these devices rely on the so-called Class Compliant MIDI software driver which is part of Windows. Unfortunately the driver is not actually compliant with the official MIDI specification in that it limits the size of sysex messages to 255 bytes. Many of the DX/TX synths send sysex much longer than 255 bytes so DXM uses larger buffers to manage incoming sysex.
In summary, avoid cheap MIDI cable devices and spend a little more to get a reliable, branded, device that will have its own fully compliant driver.
Check that your MIDI devices are correctly installed.
"I can select MIDI devices when DX Manager starts but then get an error message: DX Manager is getting no response from your synth.."
Assuming your synth is turned on and your MIDI devices are working OK, there are two possible reasons why DX Manager can't communicate with your synth:
Possible Cause 1: Your MIDI cables are incorrectly patched.
Check that the MIDI cable connected to the MIDI Output socket on your PC is connected to the MIDI In on your synth and vica versa.
Possible Cause 2: Your DX's internal settings are preventing communication
There are two ways this can happen : either your DX's internal memory protection is switched on or it's internal settings for receiving/transmitting patch data (sysex or system exclusive messages) are incorrect.
Each time you switch off your DX, memory protection is automatically switched ON to prevent accidental overwriting of patches in it's internal memory.
So before you can send new patches to your DX you must switch the memory protection off :
On the MKIDX7 - Press the green internal memory protect button on the front panel. If the LCD display shows MEMORY PROTECT INTERNAL ON, switch the setting to OFF by pressing the NO button.
On the MKIIDX7 - press the Edit button then Button 14 - if the LCD shows MEMORY PROTECT INT ON, switch it OFF by pressing the NO button.
The DX7 uses device numbers to "tag" outgoing sysex messages and to filter incoming messages. Device numbers are used to identify the source of sysex messages in much the same way that channel numbers are used to associate key note and other channel information with a particular instrument.
The device number of any sysex message must match the internal device number setting of your DX for incoming sysex messages. The procedure for checking device numbers varies depending on which synth model you are using:
As MIDI was only a couple of years old when the MKI DX7 was launched it has only a rudimentary MIDI specification. There are two specific limitations that can affect communication : the MKI cannot recognise requests for sysex information, and it only ever uses Device Number 1 when transmitting sysex data.
These limitations mean that DX Manager cannot automatically initialise a MKI DX7 - you must set your synth up manually.
To check the MIDI settings on your MKI do the following :
If the screen shows SYSINFO UNAVAIL press the + (On) Data Entry Button.
MKII DX7 and all other DXxx
The MKII DX7 has a much more comprehensive MIDI specification than the MKI: specifically it recognises external sysex requests and can send/receive sysex data using any of 16 device ids. Other DX7 compatibles from the TX7 on also recognise sysex requests, but vary slightly in their midi specifications.
The following guidance applies specifically to the MKII DX7.
If you selected a synth type other than the MkI DX7 in DX Manager's initialisation dialog, DXM tries to detect your synth by sending a request for a patch dump - 32 internal voices - using each of the 16 possible device numbers in turn. If DX Manager receives the requested sysex within the timeout period then it uses this device number setting for all sysex exchanges until the next time you initialise.
If no sysex is received for any of the device IDs and you get the ".. no response from your synth " message then check your settings as follows:
"I've tried all the above but still can't get DXM to work with my synth "
Most MIDI problems fall into one of the two categories above or are caused by faulty MIDI hardware setups.
However if you are certain your hardware setup is OK and you still cannot complete DX Manager's initialisation procedure:
If either MIDI input or output messages don't appear in the MIDI Manager window then check your MIDI devices are correctly installed as described above.
If both MIDI input and output are working OK but you still can't send or receive sysex messages, then the most likely cause is a problem with the software drivers for your MIDI device or the device itself.
In particular some early drivers for USB and Firewire devices can corrupt sysex data and you may receive a shorter message than DX Manager expects. If this happens check you have the latest drivers for your device.
Still Not Working ?