[clancy]

Hi lfo,
nice work! It is exciting to see the panel with new features and look.
The renamed labels are more clear, though lever 2&3 (modsource 19 & 20) can be assigned to any CC.
I also spend some time into the panel, only on graphic without colours yet. I attach a snapshot. If you like it we can put it together.

C.

Attachments:

You must be logged in to view attached files.

[clancy]

Hi Atom,

hope you are well.
It looks like the recent build do not display left-side labeled combo boxes properly, or i missed something while i was absent.

thx

[clancy]

Hi,

Congratultions on your new synth.
Are you using the ‘beta04’ panel?
If yes, is it running on a current CTRLR build?
I was to afraid to make an update after finishing that version.

C.

[clancy]

Hi,
I was doing some research. It looks like the micron uses
Sysex only for Patch saving/xchanging, so forget about sysex.
All editing has to be done with Nrpn-messages. If you look into atom’s mopho panel you will get an idea of what you have to do.
Hope that helps.

[clancy]

Here is a new version. This one can request and display the global parameter.

Attachments:

You must be logged in to view attached files.

[clancy]

Hi Pat,
Thank you for your positive feedback.
I guess Bomma is already working on a skinned version. He just has to ad two methods if he decide to implement bidirectionally this way. I did not change any modulator name.
At the moment i’m thinking of making the global parameters visible (on a extra panel), but the manual is not very helpfull, or uncomplete, or wrong. So this will take a while.

Thx

[clancy]

– Download removed, new version

Here is a new beta.Now bidirectionally.
I used the method posted in this thread:

Best way to assign values to modulator

So i want give thanks to Synthetech, msepsis & atom for that thread.

I know the plan is to use the new program-manager, but i´m sure the script will
be usefull when we get there. I just started to noodle around with LUA and get something full working (without programming knowledge) that i want to share.

• This reply was modified 10 years, 6 months ago by clancy.
• This reply was modified 10 years, 6 months ago by clancy.
• This reply was modified 10 years, 6 months ago by clancy.

[clancy]

Sorry, did not check the thread the last days.

02 04 = 2 + (4*16) = 66 = B (ASCII-Chart)
0E 04 = 14 + (4*16) = 78 = N (ASCII-Chart)
0B 04 = 11 + (4*16) = 75 = K (ASCII-Chart)
.
.
“BNK2: 00” (that´s the enterprising naming scheme for all patches)

The difference for VCF is that it is the only “unsigned” 7 bit parameter (for remote editing). In fact it is the only parameter in the panel that is bigger than +63.
In the sysex-dump it looks like this:

01 00 = 1
0F 00 = 15
00 01 = 16
0F 07 = 127

The “signed” 7 bit parameters (those where you did the forward expression) do look like this in the sysex-dump:

01 00 = 1
0F 03 = 63
01 0C = -63 (193)
02 0C = -62 (194)
0F 0F = -1 (255)

tomorrow i´ll check DCO detune, wich is the only “signed” 6 bit parameter.

THX

[clancy]

Maybe the manual was written by th same person that did the firmware.
If it´s easy enough for me i can try to fill the skeleton. In case it´s helpful i stick a single patch sysex.
Unfortunately the Patch data is unpacked to two nibbles per byte.

Attachments:

You must be logged in to view attached files.

[clancy]

Popup Window:

Identity response

Raw data
f0 7e 00 06 02 10 06 00 02 00 20 31 31 31 f7

SysEx Channel
0

Vendor
Oberheim (10)

Product family
0600

Model number
0200

Version number
20 31 31 31

Midi Monitor:

[23:55:16:000907]: RAW:[f0 7e 7f 06 02 00 20 08 63 0e 50 02 20 31 32 35 f7]
[23:55:16:000954]: RAW:[f7]
[23:55:16:000954]: RAW:[f0 7e 00 06 02 10 06 00 02 00 20 31 31 31 f7]

Looks good, doesn´t it? Let me know if(how) i can help.

THX

[clancy]

i wan´t to answer the question about panel completeness.

Basically the Matrix send/receive:

SINGLE PATCH DATA DUMBS (or a bank of 100)
and
GLOBAL PARAMETER DATA DUMBS

The Global Parameters can not be ‘remote’ edited, only via SysEx-Dumbs, so there is nothing done yet. It´s no problem to do this later on a extra Panel or Tab.

The SINGLE PATCH DATA DUMB contains 134 Data Bytes. Bytes 8-133 are in the panel, Bytes 0-7 not. Each of the first 8 Bytes are the lower 6 bits of its ASCII representation (Patch Name) and they are not displayed on the 3-Digits Display. They mainly exist to be compatible to the Matrix-6(r).

This is the Request Formula

F0H 10H 06H 04H (type) (number) F7H

(type)
=0 to request all patches in current bank and master parameters.
=1 to request a single patch from the current bank
=3 to request master parameters
=4 to request edit buffer
(number)
=0 when (type) = 0 or 3
=Number of patch requested when (type) = 1

• This reply was modified 10 years, 7 months ago by clancy.
• This reply was modified 10 years, 7 months ago by clancy.

[clancy]

maybe the new ‘Program Manager’ will be a good place for the Patch-List.

[clancy]

hi bomma72, we better skip the version that i uploaded as it generates problems from the very first start. It was just a 30 min. Drag&Drop action. Although it works good maybe i broke something.

I did not really had time to check the panel in-depth, to be honest, i think i don´t want to do this in a hurry, so this will take some days.

To avoid confusion, when you start with the panel, i would like to let you know that most of the abbreviations used in the panel where taken from the Matrix-6 Manual that can be found at the wolzow.mindworks.ee site you linked at the beginning of the thread.

Thank you for the link.

Attachments:

You must be logged in to view attached files.

[clancy]

AWESOME!

even a 10 ms “Send Snapshot” did work (after disabling midi for Env2>VCA2).
I re-arrange the UI a little bit to have a better view while deeper testing.

I have to do some research for that custom firmware, thank you for the tip and your work on the panel and the aditional Global Variables and …

Attachments:

You must be logged in to view attached files.

[clancy]

Hi, the Matrix is a old Synth with a buggy Firmware and a too slow CPU. Sending SysEx and Midi at the same time will cause bad Sound because it internally reorganise the Modulation Buses after receiving SysEx (whatever that means). Two Firmware Bugs are: the Synth will freeze when it receives Env2>VCA2 SysEx and, Env1 Sustain can not be changed via SysEx, only with dumps.

The “not so useful” UI at the start has to be adressed to me. By the time i put it together i was more focussed on the formulas then doing a design job because ‘Bomma72’ like to do the artwork (BTW, nice SEM-Style-Knobs!).

Tomorrow i will try out.

Atom, thank you for being so busy.

[clancy]

Hi atom, the latest nightly i was able to find is 1522 (maybe i searched the wrong place), so it worked good up to MM-Bus 5. You accidently put all the MM-Buses on the same path but this is corrected in a minute. Thank You.

[clancy]

Try it. May be you’ll be the first. I loaned mine to a friend until next week. But i compared the panel to a freeware standalone editor ( http://dqueffeulou.free.fr/softs/m1000osx.php ). With the new Formulas it does exactly the same.

• This reply was modified 10 years, 8 months ago by clancy.

[clancy]

Hey atom, that was educational. A good example for your “Expressions in Ctrlr” tutorial.

[clancy]

Thank you very much. I´m really curios about what you have done (will do). I think the BACKWARD has to be done by requesting the complete edit buffer and then assign the bytes to modulator values. Those byte numbers and the modulater names are listed in the csv file i attached, because the (vst compatible?) 8-character names are not always self explaining. But this is future-music, for now it would be cool to complete the FORWARD formula so we can start testing it on the device. Once again, cordial thanks!

[clancy]

Here is what i did. I had 2 big problems.

I don´t know how to handle those “7bit-signed” bytes, so i filled in the sysex formula and put their value color to red.

The Matrix-Modulation sysex command contains 3 values, i don´t know how to do this.

Beside of those problems i´m not shure of some combo box content.

I would be grateful if someone could help, ore takeover.

@jdieks, you´re right. That´s why Bomma72 wrote about that custom firmware, wich i don´t own as yet.

@opuswerk, cool.

Attachments:

You must be logged in to view attached files.

[Author]

Posts