I’ve already posted this in the very long-winded Presonus Faderport script thread, but just in case it IS related to a bug from within Cubase 14, I felt it was worth its own post:
I am currently using the previously mentioned FaderPort script (which is seriously amazing by the way) and encountered an issue that breaks the script and places the FaderPort in a state that requires a factory reset to fix.
I have yet to figure out what aspect of the sessions causes this, but on most (but not all) sessions created in Cubase versions lower than 14, the result is that the FaderPort stops responding fully with most of the buttons showing as unmapped in the MIDI remote manager. This status does not change upon opening a new session, a blank session… it just carries forward unable to properly function.
The only mechanism I’ve found that brings the FaderPort back to normal operating status is to factory reset it and then update the firmware back.
Attempting to uninstall/reinstall the script makes no difference, I’ve confirmed I’ve loaded the newest version of the script with no change in behavior. Once a session with this issue is opened in Cubase 14, the FaderPort dies and needs a factory reset.
To work around this issue I’ve been creating new Cubase 14 sessions, and importing the tracks from the old sessions. So far this has kept the FaderPort from getting borked.