Hi,
No matter what I try I cant get Cubase 13 to remember my Midi remote configuration. It’s about a Icon QCon pro G2 controller. I faithful followed the setup instructions by Bjoluc when I installed his script for the Icon QCon Pro G2 controller. No complains about that script at all. But for some reason Cubase doesn’t remember the settings. Not while I switch between projects/songs. Then every things is ok. But as soon as I shut down Cubase the configuration is gone! Next time I start up Cubase: Nothing. Suggestions? Anybody?
1 Like
Hi, do you mean custom assignments over the basic script or do you mean cubase deletes the script on start?
Did you install the script in the ‘public’ folder by any chance?
I have encountered the same problem with a script for my Novation 49SL MKIII. I did have 2 versions of the script, only 1 of them worked. Now that it finally works I have 3 versions of it in my setup up - 1 active and 2 inactive no matter how many times I delete the 2 inactive. I also had problems with my Arturia controller which wouldn’t save between each time. That started working once I changed some settings for the controller.
so I think Cubase rejects it when the scripts are not 100% “correct”. I have no idea about your product, but I had the exact same issues.
Hi Thomas,
Thanks for responding. It looks like Cubase deletes the script on start. Ones I’ve started Cubase there’s nothing the see on the Icon controller. Only when I started a project the controller come’s to life. And it works great. In the midi remote screen I see all the functions responding as should. I can assign the function keys and after switching to another project they’re still there. But after closing and re-opening Cubase they’re all gone. And I installed the script in the Local folder.
Best,
Willem
Midi remote does nothing if there’s no active session, that’s normal.
Thomas,
I solved it! In the set-up instructions of bjoluc it says to delete the Mackie Control device in Studio Setup. Which I faithfully did. But just now I ignored that and switch the Mackie Control device on. And guess what? It all works as it should. I’ll notify this “solution” in the forum topic as well. So if others experience the same problem, they know what the do or could try.
Well then it probably works under the old Mackie Control protocol, not with bjoluc’s script.
Which script did you use?
Hi Thomas,
I am so confused now! Probably because I know nothing of this matter. Quite frankly I don’t want to know 
. But I tell you what I see in the Midi remote folder. Maybe it’ll give you some more insight in this abacadabra. So there is firstly the Midi remote folder containing the Driver scripts and User settings. The Driver scripts folder has the Local folder with an icon (vendor) folder than the qcon-pro-g2 folder with the icon_qcon-pro-g2.js script. Now the User settings holds three json files. There’s the blockeddrivers the icon_qcon-pro-g26648…globalmappings.json and the Mackie_Qcon Pro G2_D5EC…globalmappings.json. What a story but as I write it down it starts to make sense to me. Thanks for supporting me. Take care.
Best,
Willem
Can you post screenshots of your MIDI Remote manager, and your MIDI Port Setup? (you can access both fro studio setup)?