Forum Replies Created
-
Posts
-
64bits Windows 7 here, and I confirm the bug is in getRange as removing it results in the values being where they’re expected
I got a similar issue, it’s what’s causing my sysex dump problem I mentionned in another thread. After
programData = midiMessage:getLuaData():getRange(5,51)
where midiMessage is a 57 bytes long midi message, programData displayed with
console (programData:toHexString(1))
is aproximately twice as big and got some seemingly random numbers as the exact same sysex data results in different numbers.
You’re right, looking at the text in the .panel file they’re set as CC, but they do only send sysex when the patch is loaded in the stable version (I just tried again to be sure) o_O Sorry for that, I guess the bug is actually in the stable version.
Everything should be sysex, there’s not a single CC in this panel.
With build 1193 OSC1 & 2’s Octaves & Waveforms, Detune, VCF”s Cutoff & Resonnance, and Assign Mode (at the bottom) all output [b0 01 xx]
Also is there some LUA changes to set a modulator’s value? The method I use to get values from the synth is broken, it’s a bit hard to describe how but for example requesting several sysex dumps of the same preset result in different values for the knobs while the sysex dump is exactly the same, knobs also tend to go to their lower value.
All of that works on stable version.
Anyway thanks for your fast answer and for making Ctrlr, it’s really a nice and usefull project!
This one http://ctrlr.org/wp-content/uploads/2012/12/Korg-DW-8000.panel
I’m using Windows version btw in case it matters
Update: I just figured that not all the sysex modulators are changed into CC, only some of them are.
