Dexed as a DX7 editor
Pascal Gauthier edited this page Mar 19, 2018
·
1 revision
You can use this plugin to edit your real DX7 patchs. Since midi sysex send/receive are quirky for the majority of VST hosts, any sysex messages (editor messages) must be send or received with the external dexed midi interface. This is configurable in the "PARM" panel. By setting a DX7 in / DX7 out midi interface, dexed will listen to specific program/cartridge changes from your DX7 and send controller/program/cartridge you edit.
- Before you use this interface, your DX7 must be configured to send or receive sysex messages. Do this by hitting [FUNCTION] and [8] button
- Check the midi channel. By reading some of DX7 literature, most DX7 are supposed to support only 1 channel. Unless you are running a cluster of DX7, you should keep this to 1.
- Press [8] again and you should see: "SYS INFO AVAIL" or "SYS INFO UNAVAIL". Keep it to "SYS INFO AVAIL" to be able to receive sysex messages. This step is not required on a TX7.
- You need to remove MEMORY PROTECT on the internal or cartridge memory to be able to receive a dexed 32 voice bulk dump. This is done by using the [MEMORY PROTECT] button and then by pushing [NO].
- If the midi out port is configured, any parameter change will be sent to your DX7.
- You can send any program/cartridge in the "CART" window by using the context (right-click) menu.
- The midi in port must be configured.
- Receive a program by using [MEMORY SELECT] then the program you want to transmit ([1] to [32]).
- Receive a cartridge by pressing [FUNCTION] then 3 times on [8] you should see " MIDI TRANSMIT ? ". If you hit yes, dexed should receive the complete cartridge.
- If the data sent is corrupted (wrong checksum, DX7 crash), it might be the midi interface implementation. Default Windows USB midi driver are known to send corrupt sysex data. If it is the case, use a third party device (like the midiman uno) that have his own USB driver.
- If you are unable to open the interface (error message after the using the [PARM] dialog), it might be because the midi driver doesn't support multiple clients (common on Windows). Be sure that there are no other applications that are using the same midi interface.