OBERHEIM SYNTH group photo

Yahoo Groups archive

OBERHEIM SYNTH

Index last updated: 2026-04-28 23:39 UTC

Message

Re: [oberheim] Re: Matrix-1000 Original RAM sysex

2011-01-21 by wolzow

Hi,

First, there is no Send All sysex command in M-1000 MIDI spec. The 27K file is a set of 100 (ie. 1 bank) individual Single Patch Data sysex commands: single patch = 275 bytes transmitted. You have to set the active bank first, the following sysex commands assume this bank. It's not a problem of M-1000, MIDI specification simply is limited to patch numbers 0..127 only, if a device allows more, it has to use banks.

Pls see the correct sysex docs (there are numerous errors in the printed manual) here:

http://www.wolzow.com/analog/m1k-midi-spec.htm

BTW, there's a note: "A gap of at least ten msec should be allowed between patches when sending
multiple patches to the M-1000."



On Fri, Jan 21, 2011 at 9:00 PM, cyllall <cyllall@...> wrote:

Hi,
The manual says the Matrix-1000 doesn't need to be in any special mode to receive a patch dump,... it should switch banks automatically?

Anyway, I dumped patches 200-299 from my Matrix and the sysex file was @27KB, the same size as the original RAM file in the files section here. I take it then that 100-199 is missing from that file?

Cheers



--- In oberheim@yahoogroups.com, Paul Cunningham wrote:
>
> the sounds on the matrix-1000 are organized into banks of 100... before you load up the 100-199 bank, change your bank to bank 1 and turn on bank hold, and they should load into the correct location. -pc
>
> On Jan 21, 2011, at 11:55 AM, "cyllall" wrote:
>
> > Hi,
> > I've sent the sysex file to my M-1000 for the original RAM patches, but only 000-100 are there, 101-199 are missing. Am I doing something wrong, do I have to adjust the timing of the packets?. I used MIDIOX.I recently re-initialised the M-1000 after changing the battery.
> > Thanks
> > Martin
> >
> >
>


Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.