Oberheim Matrix 6/6R/1000
Single Patch Editor
This editor will work with the Oberheim Matrix 6, 6R, and 1000. These machines have slightly different sysex and capabilities: so if you are working with the Matrix 1000, you need to check the "Matrix 1000" box. If you are working with the 6 or 6R, you need to keep that box unchecked.
Communicating with Edisyn
Make sure that Memory Protect is off (see page 36 of the manual).
Restoring Patches 0...199 on the Matrix 1000
If you erased these patches, you can restore them from sysex files stored in the file resources/Matrix1000Banks.zip in Edisyn's repository.
About Patch Names
The Matrix 1000 and the Matrix 6 store patch names differently. The 1000 doesn't actually store a name, but just information about bank and number. If Edisyn sees this, it will attempt to replace this placeholder name with the original "classic" name. This will include the writeable patches less than 200, unless you uncheck "Use Classic Patch Names" in the Matrix 1000 menu.
Looking Up Patch Names by Classic Matrix 1000 Name
If you would like to load a patch from memory, you can look it up by patch name in the Matrix 1000 menu.
Suggestions
- If you add a lot of random noise (like >50%) to the Matrix 6/6R1000 via Randomization or Hill-Climbing, it will often fall silent. This is almost always due to randomization of either the Amplifier section or the Amplifier Envelope (Envelope 2). I suggest that you first edit the mutation parameters to remove these sections as mutation candidates.
Gotchas
- The 6/6R has no way to request the current patch or to upload to it. But updating the current working memory is important to many functions in Edisyn. Thus if you update the current patch on the 6/6R, Edisyn will actually overwrite patch 99, treating it as a "scratch patch". This means that you cannot rely on patch 99 holding data you've saved there -- Edisyn will scribble over it. On the Matrix 1000, which can read and write to the current patch, this trick is not used.
- The original ROM (1.1.1) for the Matrix 1000 can't handle real-time updates very fast: it clogs up quickly. If you have one of these machines, you should turn off Sends Real Time Changes in the MIDI menu. Alternatively you can upgrade your ROM to a better one. There are two options, 1.1.6 and 1.2.0. I suggest 1.2.0, which I think is somewhat better. If you are in Europe, you can buy the ROM (it's quite cheap) through Untergeek:
If you are in the USA, you can buy the ROM through Bob Grieb (the author):
Note that even with a new ROM, the Matrix 1000 still will be slightly pokey in keeping up with certain parameters. But it's far better than the original ROM.
- Simiarly, the original Matrix 6 firmware can't handle updates very rapidl
y. Bob Grieb has also made a firmware revision for the 6 and 6R:
- The patch editor allows you to give patches a name. This is backwards-compatible with the 6/6r. However, when you store a patch in the Matrix 1000, your name is not stored. Instead if you request the patch again, it'll come back with the name BNKb: nn, where b is the bank number, and nn is the two-digit patch number.
- The Matrix series does not indicate the bank or number of a patch when it arrives. On the Matrix 1000, this information is extracted from the patch name. On the Matrix 6/6R there's no way to glean the information, so you may just wind up at "Patch 0".
By
| Sean Luke
|
Date
| Matrix 100 Version: August 2017
Matrix 6/6R Revisions: February 2020
|