The raw data is just, raw. There are no sensitivity adjustments that can be performed on the raw data using the editor — those need to be handled on the user end if going the raw data route. The "real" data comes after passing through the standalone firmware functions (or through the editor in hosted mode).
So that answers one question - could a firmware update make a difference? - No! OK, thanks for that. Maybe I should investigate again the standalone functionality, but I couldn't get much sense out of this in the SS1, since I use it in a kind of hosted mode - to control software (bidule & mobius) on the laptop via USB.
If you're just triggering events, then do you actually need pressure values? Triggering generally just needs a high and low state (emphasis on the "generally").
True, but to trigger up to 44 events (& the KMI editor won't do that without scene/preset changing), I need to distinguish between the highest & lowest values from a pad, & only process the highest (since I'm not THAT accurate with my toes!). This has become more difficult with the SS2. Also the navpad functionality is still hobbled.
Also I'm using pairs (N/S, E/W) for continuous control (joystick-type operation), incremental operations and program changes.
For sure, I'm not using it as the makers intended, but since I'm an improvisor, I don't have a fixed set-list with a number of fixed song arrangements. The SS looked like a more flexible 'one-stop' solution, and partly prompted by the difficulties we all had with the initial Max/MSP editor, I embarked on what's turned out to be a long and convoluted, quite interesting, but also quite frustrating journey with it. Whether it ends here remains to be seen!
Thanks for the clarifications.