I have just upgraded to CB14 after trial period. Worked fine with Novation Launchkey MK4 49 before but now it does not recognise some of the scripts in Midi Remote particularly the Transport Controls. Keeps coming up “Undefined Value” Ant ideas?
Is there any chance you’re experiencing this from sessions created in a version of Cubase earlier than 14?
I’ve opened this thread here about this, but for the FaderPort script by CKB.
In my experimentation, this has only occurred when I am in Cubase 14, and open a session created in 13 or prior. In my case (and apparently a few others) the result is that most of the script appears as unmapped, and no amount of reinstalling the script helps. The only way I’ve found around it for the FaderPort was to factory reset it, and then update the firmware again.
My extremely wonky workaround for this is to no longer open any Cubase sessions from prior versions directly, and instead import them into a new Cubase 14 session.
I’m not sure if your LaunchKey script has all the same behavior
- Does it persist once it occurs even blank/template sessions?
- If factory reset/firmware updates are possible, does this fix the issue for you if it’s persistent?
- Were you opening Cubase 13 or prior sessions in Cubase 14?
I originally thought this was unique to my system, but the responses I’ve seen suggest this may actually be a bigger issue.
I found during the trial period that if I opened a new or cb14 projectt it worked ok. If I opened a previous version project with cb14 it was hit and miss.
Now I have upgraded the transport controls using the encoders don’t work nor do the QCs.
I will try a reset and see what happens. Thanks for your response.