There are several versions of DX and TX profiles. I'll attempt to outline the differences and compatibility here. DX7ORIG.XOR: This Profile is your basic DX-7 voice, with old DX-type Function data. The original DX-7 does not remember Function data for each voice, so this profile dosn't either. You can edit the Function data from the Patch Edit screen. However, it is not a reliable display, since it dosn't necessarily reflect the correct value until you've changed it (we could make a Profile that kludges TX-like Function storage for every patch, if so desired). Also, the "range" parameters go from 0-15 instead of 0-99, so that they will be compatible with TX function parameters. The original DX had no "request" message, so we've automated the Get Bank process by simulating button pushes on the DX. Make sure that SYS INFO is ON on your DX, or this profile will not work at all (at least not until XOR is updated to send initialization messages). The Get Patch process is not automated - you need to select a patch on the front panel in response to the "Initiate Bulk Dump" prompt. NOTE: the DX only sends System Exclusive on Channel 1. ALSO NOTE: Turn Memory Protect OFF if you wish to send a bank of patches to the DX. DX7NEWER.XOR: This Profile deals with newer version DX-7s (we hope, although we don't have one to test it with at this time). The newer DX-7's are able to accept TX function data for one patch. This Profile always sends one voice function data when it sends a voice. We think that the newer DX-7's also respond to request messages, but we're not positive. TX7.XOR: Use this Profile for either a TX-7, a TF-1 module (TX-216/816) or a DX-7 with an E! card. It uses TX-style function data (bank and single format), so that each voice has its own function data. TX Function data also includes the extra "Attenuation" parameter. This is a fairly prototypical XOR Profile, with very few surprises. NOTE for multiple DX/TX or TX-216/816 users: If there is any chance that you'll be using two or more DX/TX units on the same channel, you may want to connect them separately through your programmable MIDI switcher, and turn "Sw. to Send" ON in XOR's Instrument Setup screen for those instruments. This is the best way to address each instrument separately, while also keeping them on the same MIDI channel. A better System Exclusive implementation would include a Unit, or Device Number, separate from the Receive Channel(s), in which case you wouldn't need to switch when sending data. DX7II.XOR: This Profile handles the different areas of the DX-7II (FD or no FD). The DX-7 type voice parameters are joined with the DX-7II additional parameters (this includes the stuff which used to be call functions). The Profile also handles DX-7II Performances. TX802.XOR: This Profile is similar to the DX-7II Profile, except for the Per- formance data, which is completely different in the TX-802. COMPATIBILITY: Patch files are semi-compatible throughout the DX/TX line. All are saved in the same Library and single patch file format. However, there are incompatibilities between patches created with the DX-7II or TX-802 and all earlier DX/TX formats. The DX-7II "additional" data isn't compatible with the DX/TX "function" data. If you upgrade instruments at some point, you'll need to edit the "additional" data in your entire Library, at which time you may want to obtain a conversion program to automate this otherwise grueling task. Bank Files are compatible along the same lines. All older DX/TX Profiles use the .TX7 file format - 32 Voices followed by 32 TX-style Function data. The DX7II has its own bank format, with additional and Performance data, and the TX-802 has yet another bank format, with its own style of Performances. If you upgrade instruments, a simple name change (from .TX7 to .D72) will suffice for a partial conversion. Transplant->Bank can be used to copy additional data into each patch in the bank, thus completing the conversion. OTHER Profiles may be crafted for the DX-7 with E!, the DX-7II with E!, the DX-9 and DX-5 (don't hold your breath on that one). Until these exist, use one of the existing Profiles.