Possible Bug - Remote Script Corrupted when opening pre C14 sessions

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.

Same here. Strange behaviour for strange times

Same here

Hallo everybody
I’ve installed Cubase 14 on a new PC. My Faderport 16 worked fine but suddenly it dosen’t wrok anymore. I have opened Projects that was saved in Cubase 12/13; is that the problem? What do I do from here - any solution?

While my issue has been with the FaderPort 2018, the only way I’ve found to fix it is to factory reset the device, and then reload the newest firmware.

For me, the issue seems to persist if the session was saved from Cubase 14, meaning I can’t open those sessions with the FaderPort on without the issue recurring.

The only work-around I’ve found to get to work on these older sessions is to open a Cubase 14 template, or a Cubase 14 blank session, and then import the tracks from the older version.

Thanks for input. Has Steinberg announced anything about this?

If they have, I haven’t seen it yet. But we’re not the only people seeing something odd happen with older sessions and MIDI remote devices.

Is this issue being fixed in the next update? I’m wasting hours every day, struggling with this, and if it isn’t fixed soon, I need to find another software!