Parsing SysEx from Eventide Factor series
Does anyone know how to interpret the SysEx data of the program dumps from Eventide Factor pedals? Pitch, Time and Space. I want to set knobs in Max to the current values of the pedals, but I can't find a method in the SysEx string which changes in multiple places at the same time. I can't even find the value of a single knob. Unfortunately, the "Programmer's reference manual" does not help.
Alternatively, I would query the values of each button individually, but I can't do that at all. Can only request the program dump, but not interpret it.
Does anyone have experience with this, or an example?
I have this paper but don’t understand it.
For example:
knob values in hex, 0 to 7FE0, reading from bottom left knob (Xknob, D-Mod) to top left knob (Mix/Intensity)
What is "0 to 7FE0" which may mean something like "0 to 127 224" in decimal?
I’ve read that they use nibbles instead of single values and I see the length of the SysEx string changing at different settings of a single knob. Maybe this "0 to 7FE0" thing adds and removes bytes. I just can’t see a pattern.
It has been a while since I have dealt with sysex messages but E0 and F7 have particular uses in building up midi messages to denote the start and end of a message. See the text in the same PDF
Standard Non-Real Time
0xF0 0x7E <channel number> <sub-ID#1> <sub-ID#2> ..... 0xF7
the 0xF0 and 0xF7 are standard MIDI for start of system exclusive, and end of system exclusive. Note that 0xF0 (for example) is a hexadecimal representation of the decimal value 240, while 0xF7 (sometimes known as EOX) is decimal 247.
<channel number> must be either 0x7F or equal to the unit’s configured SYSEX ID (0 in update mode).
<sub-ID#1> <sub-ID#2> give more information about the message type.
looking at it again and also looking at my time factor, some of the knobs transmit a wide range of values - beyond 127. these must be described by the combination of the two sysex values 7F and E0.
Do you have the program dump of the TimeFactor in Max and can you see the relevant bytes while you turn one knob?
I turned the Mix knob on the device slowly, requested a program dump at every changed value and watched the SysEx dump live in a message box. I could not tell how I would be able to parse that knob value. Do you see more?
I do not have a program dump of the time factor. I don't think it Is possible to see the bytes while turning one knob. The pedal can be setup to send MIDI control messages when knobs are turned so that one can theoretically control other devices. The MIDI CC coming out is between 0 and 127. I think the bytes you are after are only relevant to the internal saving and transmitting of preset information.
Ok, then we are not talking about the same thing. Thank you anyway!
In case anybody here has analytic SysEx-eyes, here are four preset dumps. All knobs on the hardware are at zero, just one knob has different values:
Do you see the system, the method?
Here are the message boxes of that patch:
28 = <<EVENTIDE> 0x1C (decimal 28)
112 = <H4000> 0x70 (decimal 112).
15 = device id
79 = <message_code> in this case SYSEXC_TJ_PROGRAM_DUMP 0x4f
what follows is described as <lots-o-bytes>
if one removes the header and F7 (dec 247)
and convert "data" to ascii
you get something as it is described on last page of that pdf file.
now have fun trying to understand the values, nibbles etc
SOLVED!
Hahaaa!
First breakthrough:
Source Audio told me to convert the dump to ASCII.
Thank you very much for that, now I can see the nibbles.
Second breakthrough:
I discovered, that [sprintf] can directly convert nibbles like 7fe0 to decimal. Actually the PitchFactor sends knob values 0-32736 and the same MIDI value is not always the same nibble.
Okay, it took me a few patch variations, a few hours and a few cups of coffee, but it ended up being easier than expected:
Sweet, thanks for sharing.
Coffee is healthy !
Glad you worked it out, sweetest cake is allways self baked one