Page 1 of 2

Oberheim Matrix 1000 Control/Editing

Posted: Sun Dec 23, 2007 7:32 am
by supermel74
Can the Matrix 1000 be realtime controlled/edited with a standard hardware midi controller like the Behringer BCR 2000 or can it only be edited via software?

Posted: Sun Dec 23, 2007 8:06 am
by uncle silas
I have a 6r and it doesn't take kindly to CC control at all. Especially with the envelope. It stutters and sometimes locks up for short periods.

I've heard that Sysex controllers will work more smoothly. I don't have one to test though...

I look at my 6r more like a preset synth than a real-time synth. It'll do some crazy s**t though.

Posted: Sun Dec 23, 2007 8:21 am
by xpander
you have a couple MIDI CCs you can assign into the modulation matrix, seen in the screen capture below of Unisyn and then Galaxy. it also responds to SYSEX control (that's how software editors work, of course)... but i still need to program a realtime example to see how practical it is. i have had much success with MIDI CC control in the mod. matrix.

Image

Image

Posted: Sun Dec 23, 2007 8:30 am
by supermel74
Either way, I guess 1000 presets would probably cover just about anything I could reasonably want. Thanks.

Re: Oberheim Matrix 1000 Control/Editing

Posted: Sun Dec 23, 2007 12:35 pm
by vcs3
supermel74 wrote:Can the Matrix 1000 be realtime controlled/edited with a standard hardware midi controller like the Behringer BCR 2000 or can it only be edited via software?
Yes it can.
And if you use this software http://www.mk2software.com/matrix/index.php is a piece of cake.

P.S.- I don't know the guy that make it! I'm just a costumer.

Posted: Sun Dec 23, 2007 8:41 pm
by Joey
I belive theres also an access programmer available for it, should go for cheap on ebay.

Posted: Sun Dec 23, 2007 10:36 pm
by Altitude
Joey wrote:I belive theres also an access programmer available for it, should go for cheap on ebay.
Um, they are rare as h**l and sell for more than twice that of a M1000. There is nothing that works well with the M1k/M6 as far as comprehensive realtime controls go since the processors cant handle large midi streams and choke. I spent days trying every possible combination of hardware and software to give my m1k some form of control surface and everything had the same results. The only thing that did work for any usable realtime control was using the assignable CCs as modulation sources. Anything sysex would only allow adjustment of parameters one at a time and with no notes playing. If you played a note and tried to tweak a parameter via sysex, it would freak out.

Posted: Sun Dec 23, 2007 10:40 pm
by Joey
Altitude wrote:
Joey wrote:I belive theres also an access programmer available for it, should go for cheap on ebay.
Um, they are rare as h**l and sell for more than twice that of a M1000. There is nothing that works well with the M1k/M6 as far as comprehensive realtime controls go since the processors cant handle large midi streams and choke. I spent days trying every possible combination of hardware and software to give my m1k some form of control surface and everything had the same results. The only thing that did work for any usable realtime control was using the assignable CCs as modulation sources. Anything sysex would only allow adjustment of parameters one at a time and with no notes playing. If you played a note and tried to tweak a parameter via sysex, it would freak out.
edit:

I didn't realize they were that rare...

Posted: Mon Dec 24, 2007 1:03 am
by soundsubs
I was able to make a semi usable M1000 editor for the Access Virus TI using sysex. Most parameters adjust fine without clogging the buss, but sometimes it chokes. its too bad that you cant thin the amount of sysex going outbound, or it might work. as i read on the internet, its possible that the sysex was incomplete, as in unfinished on the oberheim mfg plant.

i also bought the ob6000 for it. thats pretty great, but still has similar issues.

pm me if you want it.

Posted: Mon Dec 24, 2007 3:08 pm
by Altitude
soundsubs wrote:I was able to make a semi usable M1000 editor for the Access Virus TI using sysex. Most parameters adjust fine without clogging the buss, but sometimes it chokes. its too bad that you cant thin the amount of sysex going outbound, or it might work. as i read on the internet, its possible that the sysex was incomplete, as in unfinished on the oberheim mfg plant.

i also bought the ob6000 for it. thats pretty great, but still has similar issues.

pm me if you want it.
The sysex is about as simple as it gets (very short string, one variable per control) and I think the midi implementation is wonderful since you can control any parameter possible. The problem is the hardware cant deal with sysex messages and normal note data at the same time

Posted: Mon Dec 24, 2007 6:54 pm
by shaft9000
i adore the sound of this synth despite it being a turd to program.
just lovely pads, odd keys, strings & fx noises.
it's the only synth i've ever kept that is lousy to program (ROMplers included)

long attack EGs absolutely rule the universe
i can only imagine how delicious a Matrix12/Xpander must be....

Posted: Tue Dec 25, 2007 1:41 pm
by tunedLow
Altitude wrote: The sysex is about as simple as it gets (very short string, one variable per control)
I thought sysex was variable length?

Posted: Tue Dec 25, 2007 2:47 pm
by Altitude
tunedLow wrote:
Altitude wrote: The sysex is about as simple as it gets (very short string, one variable per control)
I thought sysex was variable length?
Sysex strings can be but on the m1000 they very short (i.e. F0 10 06 06 15 40 F7 is cutoff) with only one value that changes per prameter (the "15" defines the parameter the "40" its value). Patch dump strings will be much longer obviously.

a xmas present: Here is a Cubase Device Panel for the M1000
http://no-ho.com/m1kpanel.zip

This is not mine, it is made by Cykong, all credit goes to him

http://www.cykong.com/CubaseSX/SXpanels.htm

Posted: Tue Dec 25, 2007 9:29 pm
by xpander
Altitude wrote:
tunedLow wrote:
Altitude wrote: The sysex is about as simple as it gets (very short string, one variable per control)
I thought sysex was variable length?
Sysex strings can be but on the m1000 they very short (i.e. F0 10 06 06 15 40 F7 is cutoff) with only one value that changes per prameter (the "15" defines the parameter the "40" its value). Patch dump strings will be much longer obviously.

a xmas present: Here is a Cubase Device Panel for the M1000
http://no-ho.com/m1kpanel.zip

This is not mine, it is made by Cykong, all credit goes to him

http://www.cykong.com/CubaseSX/SXpanels.htm
thanks for this post... i'll slap together a M1000 template for the novation ReMOTE, too.

Posted: Wed Dec 26, 2007 1:50 am
by cornutt
Altitude wrote:The problem is the hardware cant deal with sysex messages and normal note data at the same time
Interesting... I haven't run into that program with my M1000. I've done some real-time parameter tweaking with mine and it seems to deal with it OK. The M6 is another matter... :?