Parsing Korg KARMA Sys-Ex #547
-
|
Greetings, Starting a new thread regarding the parsing of Korg Karma Sysex strings when switching programs / banks... NOT URGENT but for future reference and eventual panel functionality. So while it is possible to switch banks and program presets with a rather simple a straightforward external sysex from a panel such as : I've taken note that the on board controls returns a super long sysex string within a single F0 ... F7 message. Which seems to contain a bunch of internal settings which pertain to the preset. This is returned when using the on board bank buttons but not when switching bank / programs with the Ctrlr panel??? So I am wondering if it is possible to parse the single string into it components so as to "set" sliders within the Ctrlr panel? Side note, if interested: I have been cataloging, into a spreadsheet, ALL the sysex messages to control the synth and the KARMA functions and happy to post here or goto , KARMA-Lab Forums, where I've been posting updates as the spreadsheet progresses and hopefully Stephen will call out any errors I'm making... so far so good. Below is an example of the returned sysex from the keyboard when program / banks are switched using the on board controls Peace
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Here is what I think is probably correct parsing of the data. It is adapted from my M3R panel — so some small details may be incorrect. parse Korg Karma sysex_1_0.zip The data parseKorgData = function(--[[ CtrlrComponent --]] comp --[[ MouseEvent --]], event)
local offset = 6 -- ignore KORG Header
local nameSize = 16
local m = MemoryBlock()
m:loadFromHexString(sysexString)
console(string.format("Initial Dump Size=%d bytes", m:getSize()))
local numberofpatchesindump = m:getSize() -- this will be something different (like 128 etc)
local sizeOfLoop = m:getSize() - 1 - 4 - 7 --[[ always getSize()-1,-4 extra nul bytes,-7 header+eox--]]
local accrue = MemoryBlock()
for i = offset, sizeOfLoop, 8 do
local set = MemoryBlock(m:getRange(i, 8))
local res = convert827(set)
accrue:append(res)
end
for i = 0, accrue:getSize() - 1, numberofpatchesindump do
console(accrue:getRange(i, nameSize):toString()) -- extract all names
end
console(string.format("Actual Korg Data: %s\n%d bytes", accrue:toHexString(1), accrue:getSize()))
end
function convert827(m) -- take a set of 8 bytes (first byte contains) msbit data of each subsequent byte
local t = {}
assert(m:getSize() == 8, "size=" .. m:getSize())
local b = {1, 2, 4, 8, 16, 32, 64}
local msb = m:getByte(0) --
for i = 1, m:getSize() - 1 do -- start at the second byte
local mask = b[i]
local band = bit.rshift(bit.band(msb, mask), i - 1)
local addmsb = m:getByte(i) + (band * 128)
table.insert(t, addmsb)
end
local result = MemoryBlock()
result:createFromTable(t)
assert(result:getSize() == 7)
return result -- MEMORYBLOCK
end
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you, I will try this out in the morning… see if I am able to make sense of it. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure about this line: |
Beta Was this translation helpful? Give feedback.
-
|
Looks to be functioning properly as written in the zipped panel... Really excited to go down this path and learn way more than anticipated!!! |
Beta Was this translation helpful? Give feedback.
-
|
The next step would be to map each parameter in the manual to each byte in the message and update the panel. The first 16 bytes are the name in ASCII Sometimes there will be bitpacking of several values - say 8 modulators have on/off stored in a single byte, so it will be a challenge mapping everything out for 800+ values! I always build a lookup table that tells me how to break down the data. For example in the Korg M3R I have a lookup table (excerpt below): The t={
...
["CONTROL CHANGE1"] = {byte = 45, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE2"] = {byte = 56, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE3"] = {byte = 67, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE4"] = {byte = 78, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE5"] = {byte = 89, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE6"] = {byte = 100, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE7"] = {byte = 111, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["CONTROL CHANGE8"] = {byte = 122, mask = 4, rs = 2, label = "Ctrl. Chge", max = 1, min=0},
["DAMPER1"] = {byte = 45, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER2"] = {byte = 56, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER3"] = {byte = 67, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER4"] = {byte = 78, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER5"] = {byte = 89, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER6"] = {byte = 100, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER7"] = {byte = 111, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DAMPER8"] = {byte = 122, mask = 8, rs = 3, label = "Damper", max = 1, min=0},
["DETUNE1"] = {byte = 39, mask = 255, rs = 0, label = "Detune", max = 50, min = -50,add=0}, ...
}
-- Once you have your data from a dump, loop through the table and assign values
for k, a in pairs(t) do
local value = bit.rshift(bit.band(accrue:getByte(a.byte), a.mask), a.rs) + a.add
panel:getcomponent(k):setValue(signed8bitChar(value), true) -- set the modulator value to the byte extracted from the dump
end
--The signed8bitChar function converts bytes to negatives**
function signed8bitChar(val)
val=val < 128 and val or (val -256 )
return val
end
If you see a FF in accrue MemoryBlock data, I am guessing it means assign -1 to your modulator (at least, from memory this is the case on the M3R) |
Beta Was this translation helpful? Give feedback.
-
|
Sweetness !!! As always the pre-emptive answers to questions not yet posed are appreciated. I am not quite ready to implement this but having it out there (here) reminds me of all the interrelated aspects I hope take into account in an eventual build I can share... Currently in the depth of creating a complete SysEx message spreadsheet, to facilitate any future look up tables and dynamic assignments of sliders. |
Beta Was this translation helpful? Give feedback.
Here is what I think is probably correct parsing of the data. It is adapted from my M3R panel — so some small details may be incorrect.
parse Korg Karma sysex_1_0.zip
The data
sysexStringis the string above in your post.parseKorgData = function(--[[ CtrlrComponent --]] comp --[[ MouseEvent --]], event) local offset = 6 -- ignore KORG Header local nameSize = 16 local m = MemoryBlock() m:loadFromHexString(sysexString) console(string.format("Initial Dump Size=%d bytes", m:getSize())) local numberofpatchesindump = m:getSize() -- this will be something different (like 128 etc) local sizeOfLoop = m:getSize() - 1 - 4 - 7 --[[ always getSize()-1,-4 extra nul bytes,…