Page 1 of 1
Sysex guide interpretation?
Posted: Sat Apr 17, 2010 9:10 am
by newtonlkh
I hope to find ways to be able to enter sysex like M3 instead of recording them and extract it from event edit.
Is there any guide available, to teach how to read a file like M50_MIDI.TXT? Currently have no idea what it's talking about. I hope to be able to, get the sysex i need, from so sort of computer program, instead of recording it... the txt file read like this...
*2
mmm = 0 : COMBI PLAY
1 : COMBI EDIT
2 : PROG PLAY
3 : PROG EDIT
4 : SEQUENCER
6 : GLOBAL
7 : MEDIA
*3 OBJECT BANK
PROGRAM
b = 0 - 4 : Bank A - E
COMBINATION
b = 0 - 3 : Bank A - D
DRUM KIT
b = 0 : Bank INT
64 : Bank USER
[ TABLE 1 ] PROGRAM PARAMETERS
No. : No. in the PROGRAM DUMP DATA.
PARA No. : Mode, Parameter ID, SUB ID [Hex] for PARAMETER CHANGE.
The messages with Mode = 2(PROG PLAY) can be recognized even when Mode = 3(PROG EDIT).
with Mode = 3(PROG EDIT) can be recognized only when Mode = 3(PROG EDIT).
+-----------+---------------------+-------------------------+-----------------------------+---------+
| No. (bit)| PARAMETER | DATA(Hex) : VALUE | DESCRIPTION | PARA No.|
+-----------+---------------------+-------------------------+-----------------------------+---------+
| 00 | PROGRAM NAME (Head) | | | |
| : | : | 20~~7F | | ----- |
| 23 | PROGRAM NAME (Tail) | |
p.s. Hope every parameter will be fed back to the respective controls, and all knobs are endless, faders motorized, instead of parameters jumping arround when you change program/control mode....... (the endless knobs of kontrol 49 is too disappointing...)
Posted: Tue Apr 27, 2010 1:04 pm
by orpheus2006
All M50 SysEx messages have the following common format:
- Header
- Function
- Data
- End Byte
Using hex-values, the header always consists of:
F0 42 3x 00 01 05 where x is the MIDI channel
The next hex-value is the function. The following functions are defined for the M50:
12 MODE REQUEST
42 MODE DATA (= result of MODE REQUEST)
4E MODE CHANGE
41 PARAMETER CHANGE
53 DRUM KIT PARAMETER CHANGE
54 ARPEGGIO PATTERN PARAMETER CHANGE
72 PARAMETER DUMP REQUEST
73 PARAMETER DUMP (= result of DUMP request)
74 OBJECT CURRENT DUMP REQUEST
75 OBJECT CURRENT DUMP (= result of DUMP request)
76 STORE OBJECT BANK REQUEST
77 OBJECT WRITE REQUEST
24 RESULT REPORT
The number of bytes for the data is specific to each function and described in the M50_MIDI.TXT. Actually the excerpt you posted describes the meaning of some data values, e.g. if you look at function MODE CHANGE you will find variable mmm that defines the Mode.
Finally, the last byte of a SysEx message is always F7.
Example: change MODE to "Sequencer":
F0 42 30 00 01 05 <- Header (assuming 0 is the global channel)
4E <- function "MODE CHANGE"
00 00 00 04 <- mmm=4 SEQ (my guess is that you need to pass 4 bytes, but please test with MIDI-OX or similar tool)
F7 <- SysEx end
so the complete SysEx message for this example is
F0 42 30 00 01 05 4E 00 00 00 04 F7
Hope that helps.
Posted: Wed Apr 28, 2010 7:39 am
by newtonlkh
very clearly explained
thanks a lot!!!
I think we can program Novation SL Zero 's faders to control non-CC controls in M50 using sysex?
So sad Kontrol 49 cannot...
How about that behringer fader thing?
Posted: Thu Apr 29, 2010 9:21 am
by orpheus2006
newtonlkh wrote:How about that behringer fader thing?
AFAIK it doesn't support sysex messages. BTW you can download the user manual from their web-page.
Posted: Fri Apr 30, 2010 5:24 pm
by newtonlkh
I read the manual and cant find info on sysex, but i've heard somewhere (forgotten where) that it does.
but it's to risky experimenting....
Posted: Sun May 02, 2010 1:16 pm
by Crystal Mech
Thanks for your reply orpheus2006 - This is a v.useful post. I wish there was more information on sysex, especially how to edit sysex.
1 thing I was wondering, there are alot of M50 controls that if you automate in realtime & record in the sequencer, they automatically show up as sysex in Event Edit, but how are you supposed to know which sysex is which? (Eg if you record several sysex msgs on the 1st beat of 1st bar, they all show up as just a sysex msg in the M50 event editor). I really need to know how to edit sysex events..
Posted: Sun May 02, 2010 2:33 pm
by newtonlkh
in event edit... i think there is no way you can know which is which.
but you can use midi ox to examine each control, to see what sysex it transmits when you change things.
maybe you need to put the sysex in event edit in different time, and play the sequence to midi ox, so that it comes in order, and you examine which one match which of your action recorded...
i am sorry for my bad english, i hope you understand what i mean...
Posted: Sun May 02, 2010 2:45 pm
by Crystal Mech
I understand perfectly, thanks
I haven't used midiOX for a while, need to reinstall it - It looks kool, even let's u edit sysex!
I was wondering if Korg published an even more complete list than what orpheus2006 posted? The manual doesn't say much more than u can record & see sysex msgs in event edit, which isn't too helpful.
Posted: Tue May 04, 2010 5:08 pm
by newtonlkh
http://www.korg.com/uploads/Support/M50 ... 610000.zip
This is the complete sysex guide. It can be found in the download section of korg.com, the last item of "Documents"
Good luck experimenting!
Posted: Tue May 04, 2010 5:42 pm
by Crystal Mech
Cheers! I just had a look at the Korg site & found it listed there too, as stated. Will have some fun doin some crazy automations.. x)