Cool to know about a non-NRPN approach to smoothing things on the horizon. Being relatively naive to this before now, I’ve been learning about NRPN from Novation Support and also Thomas with XOR, as I’ve been working on sequencing my Novation Summit a bit from the NERDSEQ.
From what I’m learning, it’s actually not that complicated, as it’s just CC numbers and values. Once the particular parameter number is chosen, you set the MSB and LSB for the value (on CC6 and CC38; e.g. once you get to 0:127 for 128, you then go to 1:0 for 129 and count by 128), and as it is 128x128 it allows 16384 values. With NERDSEQ, Thomas has set it up such that you don’t have to do the complex counting by 128, but you just choose a value from 0 to 3FFF (hex for 16383), so it’s not much to set up it seems from a user perspective, especially if implemented this way. From what Thomas (XOR) says, one normal CC uses 3 bytes, versus one NRPN using 12 bytes, so I’m not sure how much this would strain the resources of the ES-9 or not.
In terms of devices using NRPN, I believe my old UC-33 is able to do this, and from my review of the Faderfox, it can as well. Maybe there are some constraints, I don’t understand this well enough yet and haven’t messed around directly. Seems like it would work with the NERDSEQ, though I don’t know at what point things might choke up due to the increased load.
Anyway, not trying to beat a dead horse here, but rather to try and share what’s been somewhat demystified for myself. Not sure if this is obvious to most of you or not already.