I got Novation Launchpad Mini MK3 with a bunch of buttons assigned to it in Midi-Remote.
So, I just updated the Launchpad’s harware, opened Cubase, everything says it is connected and the midi-meter in Cubase receives messages from it, but Midi-Remote just doesn’t respond at all!
Can anyone help me out? I assume, the port might be wrong, but there’s no option to choose any other port and in the midi-script editor it says it is connected as well.
The hardware update probably changed the MIDI message layout. Please export your script to a “.midiremote”-file and upload it here. I can have a look on the bound midi messages.
After that, please close Cubase, (install and) open MIDIOx. Start recording your screen. Hit the LK-pads from upper left to lower right (western reading direction). Upload your screen-recording here as well.
I have imported your script. Can you confirm that still the upper left pad sends CC 57 on Channel 2?
Please clear the MIDIOx screen and only press the upper left pad, and post another screenshot.
I see two mapping pages: “Default” (is empty) and “SHS” which has Cubase functions mapped. When activating the page “SHS” I see mapped Key-Commands to Visibility-Agent related things, and a bunch of mappings labeled “Missing”, hmm.
The problem is that neither Default nor my custom SHS page responds. I mean, in midi-remote I can’t even assign any new button because it doesn’t get highlighted =/
But when I import my previous script, the issue comes back. At least I can reprogram the controller now, as it’s mostly buttons. But, still, it’d be very frustrating if a more complicated controller with lots of pages and knobs went down =/
Nope =/
By the way, is there an option to get to the same window where I can choose my MIDI ports using already existing script? I wanted to double check my selected ports, but this window appears only when I add a new MIDI Controller Surface.
Your script worked! Thank you so much, man! So, basically whenever it happens again, I should open the script with a text editor and just manually rewrite the ports, right?
No, the hardware remains unchanged, it works fine with other DAWs. The problem was that Cubase automatically just switched the ports and there was no option to change it back, I guess.
