Question: I've noticed that when I use my normal key switches (using flex router) while playing that they are sometimes reflected in reaticulate and sometimes not.
Reaticulate only knows if a MIDI event corresponds to an articulation if it matches the output event configured for the program. In other words, if you have a program with an output event that sends G1, when you press G1, it assumes that you're triggering that program and the GUI reflects it.
But if you're using FlexRouter as an additional translation layer such that the key you're pressing is different than the one in the Reaticulate bank, it won't know that you're triggering it.
I've personally done away with FlexRouter in most cases, using Reaticulate as the sole translation layer for most patches.
Now, the manual keyswitch detection has some limitations: if you have a program with multiple note output events, right now it's the case that manually pressing
any of the notes in the program will make Reaticulate think you've activated it. This is probably too surprising (and probably wrong), so I plan to tweak the logic such that if a program has multiple notes in the output events, it will ignore manual triggering.
And the midi bank/program change lane (in the midi editor) never reflects the changes if entered via key switch. Is this normal?
It's normal. I'm not sure how feasible this kind of realtime transformation is. But I do plan to create an action to trawl through the notes in selected MIDI items and convert manual keyswitches to program changes. (
Tracked here.)