Using the BC Manager, I switched the Preset < > and Function (Store/Learn/Edit/Exit) buttons to CC controllers.
The up side is that I can now use the Preset buttons to cycle through the Cubase Generic Remote Profiles I built for tons of amp sims and plugins (no longer limited to 32, BTW). The Function buttons can be assigned to anything I want, giving me 4 more buttons.
I'll add that the Preset display remains on P-1 when I use the buttons, as it should. It's not changing presets on the BCR, only transmitting CC info to the Generic Remote config in Cubase.
Th down side is that I have to do a quick load of the sysex file to the BCR at the start of every session, because it won't store it permanently.
I never had this problem until I repurposed the Preset buttons, which automatically repurposed the Function buttons. I initialized all the buttons and knobs when I built this latest file, in order to ensure there was nothing corrupt in the file I was creating. Wondering if I might have overlooked something, although a detailed study of all parameters isn't indicating I did.
Is there a little code we could add to the sysex file to make it non-volatile, the way the factory defaults and any other loads I've done are? Bear in mind that I'm not referring to a single preset, which I would store, if I still had a store button. This is a global setup for the BCR, which should not require any action, once loaded.
It's almost as if this sysex file is fomatted as a preset, rather than a full setup.
Thanks in advance.