OBERHEIM SYNTH group photo

Yahoo Groups archive

OBERHEIM SYNTH

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

Thread

Matrix 1000 loading sysex syx

Matrix 1000 loading sysex syx

2013-12-03 by <rajahpatel@...>

hi,

i'm having trouble loading patches into the 001- 199 memory locations. I have ensured memory protect is off and i have double checked this by copying patches from the ROM to the RAM locations. I am sending sysex via a Edirol UM 550 usb interface and a very slow rate but they are not copying across.

Is there anything else i should be doing?

Re: [oberheim] Matrix 1000 loading sysex syx

2013-12-03 by Narfman96 - Narfland Studio

Hi Rajah,
Is the midi channel correct for the patches and the M1000? Online web patches are almost always channel 1. The only other problem I've had is the opto-isolator failed in my Matrix. This also caused it to go silent because it would not accept any midi or sysex. 
Fran
Show quoted textHide quoted text
On Tuesday, December 3, 2013 9:06 AM, "rajahpatel@..." <rajahpatel@...> wrote:
  
  
>hi,
>i'm having trouble loading patches into the 001- 199 memory locations. I have ensured memory protect is off and i have double checked this by copying patches from the ROM to the RAM locations.  I am sending sysex via a Edirol UM 550 usb interface and a very slow rate but they are not copying across.
>
>
>Is there anything else i should be doing?  
> 
>
>

Re: [oberheim] Matrix 1000 loading sysex syx

2013-12-04 by <rajahpatel@...>

Hi, the midi channel is correct. I doubt it can be the opto isolator problem as it is reading midi note/controller data. However, it doesn't respond to my mackie c4 which is sending sysex. I think the next step would be to use a different midi interface unless anyone has any other suggestions ?

Re: [oberheim] Matrix 1000 loading sysex syx

2013-12-04 by Daniel Forró

What do you mean by "very slow rate"? MIDI has fixed speed, and SysEx  
data must use the same speed as other MIDI data.

The only problem connected with speed, when we send data for example  
from MIDI sequencer and can set fast or slow tempo, can be when  
there's more blocks in data file (each of them with it's own SysEx  
header) and these blocks are sent without pause between them... Then  
some more sensitive instruments with small MIDI input buffer or not so  
powerful CPU can have trouble.

Are you sure data file you want to send is OK, and MIDI channel  
encoded in SysEx header (= Device Number) is set also on the  
instrument as receiving channel for SysEx?

Daniel Forro
Show quoted textHide quoted text
On 3 Dec, 2013, at 8:28 PM, <rajahpatel@  wrote:
> i'm having trouble loading patches into the 001- 199 memory  
> locations. I have ensured memory protect is off and i have double  
> checked this by copying patches from the ROM to the RAM locations.   
> I am sending sysex via a Edirol UM 550 usb interface and a very slow  
> rate but they are not copying across.
>
> Is there anything else i should be doing?

Re: [oberheim] Matrix 1000 loading sysex syx

2013-12-04 by <rajahpatel@...>

hi

by 'slow rate' i am altering the 'transmit speed' in Sysex librarian.


I have now managed to get my Mackie C4 Pro to talk to my oberheim Matrix 1000 with sysex messages so there is no problem with the port. I have spent the best part of a day coming up with a way to route and merge midi so i can use the C4 Pro to control the oberheim. I'll set all this aside and have another go with sending patch data later today.

Many thanks for the suggestions and i will check the device ids and sysex headers

Regards

R

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.