OK, sysex librarian worked fine, & I've successfully loaded, 88, 91, 88 again etc. Curiously, my advanced editor, when it's fired up informs me 'update needed - expected: 88, found: 91'. Logically (and according to the file dates!) 91 is more recent than 88, but the editor doesn't seem to think so. Anyway, there is little difference in the sensitivities of the two firmware versions. Out of interest, I have measured the raw values of my SS1 a couple of years ago (I think with the VK2 firmware), by sitting a block of steel on each pad and reading the max value from each corner with MIDI monitor. (I have four small plastic feet stuck to each corner of each pad to help operation, & sit the weight on these; I've fitted the same to the SS2),
I just tried the same thing with the SS2, both firmwares. I attach the three tables. One thing I'll say though, you've got the results for the SS2 very consistent across all the pads!
Your suggestion for using 'average' rather than 'maximum' is logical, & I tried it anyway, but of course it makes no difference to the raw data; similarly the 'sensitivity' slider does nothing for the raw output, but merely seems to limit the maximum passed through the editor software. The suggestion I think assumes I'm using the KMI editor, when in fact I use it only to set an 'INIT' patch on the SS2, then read the raw data into bidule, in which I've built my own controller group.
Since I'm not using the KMI editor, I obviously don't expect any support for my own software, and it looks like I'll have to try and moderate the hardware output through my own software, as you seem to have chosen to do. I have various threshold/comparison algorithms in my controller, but I think they'll need some serious modification to deal with this.
Should you issue another firmware update, I would certainly appreciate there being a version that manages to put out a few more values on the way from 0 to 127 and back!
back to the lab then....