Page 1 of 1

Found bug in sysex request

PostPosted: Fri Nov 14, 2008 5:57 pm
by elrules
I am doing some testing with my app. Trying to retrieve all the input settings I have found what maybe a bug.

Third zone settings from input 15 (Tom3R) to 31 (Aux7R) are not sent when requested

Here is the log my app show when I request all the config for Crash:
Request sent: Lenght: 6
F0 70 0 3 8 F7
Sysex received: Lenght: 26
F0 70 0 3 8 3 1 9 1 1 4 0 8 4 0 0 0 1 4 0 2 6 6 0 0 F7
Pad 8

Request sent: Lenght: 6
F0 70 0 3 9 F7
Sysex received: Lenght: 26
F0 70 0 3 9 3 1 9 1 1 4 0 8 4 0 0 0 1 4 0 2 6 A 0 0 F7
Pad 9

Request sent: Lenght: 6
F0 70 0 4 9 F7
Sysex received: Lenght: 10
F0 70 0 4 9 7 A 1 2 F7
3zone 9


And for input Tom3 I get this (the rest of remaining inputs behave the same):
Request sent: Lenght: 6
F0 70 0 3 E F7
Sysex received: Lenght: 26
F0 70 0 3 E 2 9 9 1 1 4 0 8 4 0 0 0 1 4 0 2 6 A 0 0 F7
Pad 14

Request sent: Lenght: 6
F0 70 0 3 F F7
Sysex received: Lenght: 26
F0 70 0 3 F 2 9 9 1 1 4 0 3 4 0 0 0 1 4 0 2 6 A 0 0 F7
Pad 15

Request sent: Lenght: 6
F0 70 0 4 F F7

(nothing is received for the "thirdzone" request)

Re: Found bug in sysex request

PostPosted: Fri Nov 14, 2008 6:48 pm
by dmitri
From megadrum_layout.pdf:

F0 70 03 04 00 02 0E 01 04 F7 – pad configuration data where:
F0 and F7 - Sysex envelope bytes (mark start and stop of a sysex message)
70 – MegaDrum Sysex ID. Signifies that it is a MegaDrum Sysex.
03 – MegaDrum Chain ID.
04 – MegaDrum Sysex type. 04 means a config sysex for 3rd zone
00 - 3rd zone number between 00 and 0e (32 inputs version) or between
00 and 09 (22 inputs version). 00 corresponds to HiHat, 01 – Snare and so on.
02 0E 01 04 – data

Hint: There is only one "3rd zone setting" per each Head/Rim or Bow/Edge pair. Obviously the Kick input is excluded.

Re: Found bug in sysex request

PostPosted: Fri Nov 14, 2008 7:35 pm
by elrules
Ahhhhh ok, i thought 3rd zone had the same input number than the rim of the corresponding pad...
I will correct it now ;)
thanks