You are correct about that. I do remember some params which could not be edited.
Darn Oberheim for that, but they made up for it on the Xpander.
If anyone wants the editor I made for the Peavey PC1600, I still have it on my website, but it requires a
midi patchbay to do some filtering, so you don't get a midi loop.
I set it up so when you press any of the 16 buttons, on the PC1600, it would call up the appropriate patch on the PC1600 to edit a specific page on the M6 (ie, one button was for the Filter, one for the DCO's, etc).
However, one could easily make some edits so the patch bay wasn't needed.
On 2/15/06,
J
<
rakker16mm@...
> wrote:
I am not absolutely sure but my recollection is that
the device name for the M6 and M1000 are different.
There is one other issue that crops up on certain
peramiters. That some parameters can only be changed
by sending the entire patch. It's pretty hard to get a
knob and button box to do that if it wasn't
specifically built for that purpose. On the other hand
any thing is an improvement over the front panel.
James
--- Tony C <
tony@...
> wrote:
> The sysex spec for the M1k & Matrix 6 are identical.
> The voice architecure is identical as well.
>
> I made an editor for the 6R using the PC1600 which I
> was able to use on the
> M1k, but you couldn't se the parameters being edited
> on the M1k, as you can
> on the 6/6R.
>
> The M1k has no provisions for storing the patchnames
> from a patch that comes
> from the 6R though.
>
> I don't remember if the Device ID for the 6R is the
> same as the Matrix 1000.
> That could be one possible problem why your control
> freak doesn't work on
> the M6.
> You could check that on the Control freak, and if it
> is not the same as the
> one for the 6, just edit it. I'ts only 1 byte
>
>
> On 2/15/06, skylab001 <
skylab001@...
> wrote:
> >
> > Now that I've got my 6R up and running, I would
> like to program my control
> > freak for it so
> > that I can control it with knobs. It has a matrix
> 1000 setup already but
> > that doesn't work
> > so far with the M6. Can somebody help me out with
> the sysex strings I need
> > for parameter
> > changes. So far I've got the general:
> >
> > F0H beginning of sysex
> > 10H Oberehim code
> > 06H For the M6R device ID
> > <opcode>
> > <data bytes>
> > F7H
> >
> > But if somebody could fill me in with an example
> of say the VCF control
> > string, I could
> > probably figure the rest out. I need to figure out
> what the opcodes and
> > the data bytes are
> > for each parameter. I have found this text on the
> internet which I have
> > been trying to
> > reference but can't quite figure it out without
> seeing a full string or a
> > couple full strings.:
> >
> >
> >
> >
> > Statistics: 134 Bytes/Single Patch
> > = 268 nybbles transmitted + 5 bytes
> Header + 1 byte Checksum + 1
> > byte EOX
> > = 275 total transmitted bytes/Single
> Patch
> >
> >
> > Byte Parameter # Bits Description
> >
> > 0 - 7 6 each Patch Name
> > Each character is
> represented by the lower 6
> > bits of it's ASCII
> > representation.
> >
> > 8 48 2 Keyboard Mode
> > 0 = Reassign
> > 1 = Rotate
> > 2 = Unison
> > 3 = Reassign w/ Rob
> >
> > 9 00 6 DCO 1 Initial Frequency
> > LSB = 1 Semitone
> >
> > 10 05 6 DCO 1 Initial Waveshape
> > 0 = Sawtooth
> > 31 = Triangle
> >
> > 11 03 6 DCO 1 Initial Pulse Width
> >
> > 12 07 2 DCO 1 Fixed Modulations
> > Bit 0 = Lever 1
> > Bit 1 = Vibrato
> >
> > 13 06 2 DCO 1 Waveform Enable
> > Bit 0 = Pulse
> > Bit 1 = Wave
> >
> > 14 10 6 DCO 2 Initial Frequency
> > LSB = 1 Semitone
> >
> > 15 15 6 DCO 2 Initial Waveshape
> > 0 = Sawtooth
> > 31 = Triangle
> >
> > 16 13 6 DCO 2 Initial Pulse Width
> >
> > 17 17 2 DCO 2 Fixed Modulations
> > Bit 0 = Lever 1
> > Bit 1 = Vibrato
> >
> > 18 16 3 DCO 1 Waveform Enable
> > Bit 0 = Pulse
> > Bit 1 = Wave
> > Bit 2 = Noise
> >
> > 19 12 6 (signed) DCO 2
> > Detune
> >
> >
> > Byte Parameter # Bits Description
> >
> > 20 20 6 Mix
> >
> > 21 08 2 DCO 1 Fixed Modulations
> > Bit 0 = Portamento
> > Bit 1 = Not used
> >
> > 22 09 1 DCO 1 Click
> >
> > 23 18 2 DCO 2 Fixed Modulations
> > Bit 0 = Portamento
> > Bit 1 = Keyboard Tracking
> Enable
> >
> > 24 19 1 DCO 2 Click
> >
> > 25 02 2 DCO Sync Mode
> >
> > 26 21 7 VCF Initial Frequency
> > LSB = 1 Semitone
> >
> > 27 24 6 VCF Initial Resonance
> >
> > 28 25 2 VCF Fixed Modulations
> > Bit 0 = Lever 1
> > Bit 1 = Vibrato
> >
> > 29 26 2 VCF Keyboard Modulation
> > Bit 0 = Portamento
> > Bit 1 = Keyboard
> >
> > 30 30 6 VCF FM Initial Amount
> >
> > 31 27 6 VCA 1 (Exponential)
> Initial Amount
> >
> > 32 44 6 Portamento Initial Rate
> >
> > 33 46 2 Lag Mode
> > 0 = Constant Speed
> > 1 = Constant Time
> > 2 = Exponential
> > 3 = Exponential
> >
> > 34 47 1 Legato Portamento Enable
> >
> > 35 80 6 LFO 1 Initial Speed
> >
> > 36 86 2 LFO 1 Trigger
> > 0 = No Trigger
> > 1 = Single Trigger
> > 2 = Multi Trigger
> > 3 = External Trigger
> >
> > 37 87 1 LFO 1 Lag Enable
> > 38 82 3 LFO 1 Waveshape (see
> Table 1)
> > 39 83 5 LFO 1 Retrigger point
> > 40 88 5 LFO 1 Sampled Source
> Number
> > 41 84 6 LFO 1 Initial Amplitude
> >
> >
> > this is only a partial list,
> >
> > anyways,
> >
> > Thanks
> > Brian
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oberheim/
<*> To unsubscribe from this group, send an email to:
oberheim-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/