Selected Drum Model seems to be a data structure within the message -16*4byte ints - but I am not sure what the data is meant to represent . . .
00 20 3c 02 00 52 04 01 0B 4E 45 57 20 4B 49 54 00 30 12 00
Well, first you need to convert the blue part to 8 bits as it is coded in 7 bits. Most machines work with 8 bits (or 16,32,..) but for the MIDI spec all values larger than 7 bits are status byte, so you can't use them. The trick is to convert to 7 bits and back to 8 by using an extra byte that has the 8th bit value for the 7 following bytes.
I think bitwise operators are working on the lemur so that should be ok, so a function script could handle that.
But the problem I see here is the length of the data, I'm not even sure that the Lemur receives or can handle such big sysex message. Remember you figured out that the largest array size is 255 bytes. Are you receiving multiple arrays ?
And how do you get the data, is there some parameter request function ? As it doesn't seem documented on that pdf. Or do you have to trigger some function on the MD ?
i send, what they call, a kit request. it´s a sysey string where i also send the number of the kit i want to have the data from. once i´ve send the request the machinedrum responds with an array of roughly 30 values in an array.
there´s actually an other option called kit sysex dump.
after 0x52 it requests Kit Data Bytes to be sent, any idea what that could be? maybe that´s how we could query single values?
Don't know what they mean by after, but 0x52 seems to be the Kit Message, declared in the header.
Users browsing this forum: Baidu [Spider] and 4 guests