Firmware V1.28 Test Version

[mgd]

I've been playing around a bit with feeding MIDI CC from my Keystep Pro into the Mapping and stumbled over two things:
- the Keystep Touch Stripe (Modwheel, CC#9) is automatically mapped to CC#1 (could select Velocity) by the NerdSEQ
- all 7 bit controllers (#9, #74-#78) are shifted to the left by 5 bits (1 -> 20, 2 -> 40, etc.)

Am I supposed to fix this via the mapping, i.e. CC#9 actually being on #9 and all values RSFT by 5 or DIV by 0x20/32 (no problem, it's easy enough) or is that something the NerdSEQ will eventually "correct"?

Kind regards,
Michael

The keystep and standard mod-wheel cc is #1. (as specified in the midi specs)

All values (if not notes) are suppose to be scaled to 12 bit aka 0-4095 and so also the midi cc values. Do the right shifts and you get the original value.
I think it is better and easier to work with scaled values as much as possible (except for notes), do for example max automator values, max CV in, max midi cc. etc is all 4095 and you can all replace them 1:1 as a source

Scaling all values to 12 bit does indeed make a lot of sense. I'll do RSFT when I need it
[I already did and it works like a charm - I love the mapping table ]

W/r to Keystep Pro Modwheel Stripe being CC#1 or CC#9:
If I read the documentation correctly it does send on CC#9. There's also the Arturia MIDI Control Center which allows to change the CC# of the Touch Stripe (aka the Modwheel; again if I understand correctly). However when I change that the NerdSEQ still reacts on CC#1 only. So there's obviously something I do not yet understand


It really is great fun to play with these mappings. They open up a vast range of options to play the NerdSEQ and to interact with it in a live situation.

Kind regards,
Michael