Softube mkIII faders quit automatically recognizing a session in Cubase 13 pro after doing most recent (Dec. 17th) Softube update. Version 2.5.97. It also deleted the Softube fader device from my MIDI Devices list in Cubase 13 Pro.
I have Cubase/Nuendo remote integration enabled in the console 1 mkIII fader settings window
Before the update, Softube faders recognized the Cubase session when I opened it and immediately showed tracks on the Console 1 fader LED screens. I was able to use all basic functions and faders followed session commands. Now the fader screens stay completely blank when I open a session.
First step to trouble shoot:
I updated my Softube mkIII fader firmware to the latest version: 12.2.3
I went to Cubase Studio Setup, then the MIDI Remote tab and added a new surface controller device in the MIDI Remote section.
Now, when I open Cubase, the Console 1 faders still don’t automatically recognize the session. I have to add a Console One insert to each track of the session.
My goal is to get Console 1 to automatically recognize Cubase sessions and map to the faders/buttons, as it did before the update. Any thoughts, anyone?
Err seeing as how it stopped working after the latest Softube update, and Cubase 13 hasn’t changed at all in 7 months, have you asked Softube about it yet?
I have the same issue with Cubase 14 pro and Softube Console 1 Fader plus Channel Hardware. Since the Update of Dec 17th, both devices won’t get recognized by Cubase in a reliable manner any more!
(One thing that seems to help is, unplugging / plugging back the USB connection to the console 1 system. Then Cubase often gets both devices back into the MIDI Remote tab and all functions (of Fader) are there as expected).
Hey mk1. Glad to know it’s not just me. Thanks for the suggestion. Yes, I tried plugging/unplugging, but that didn’t work for me. I’m wondering if the MIDI Manager script somehow got corrupted, but I don’t want to change too much, til I get Softube’s input. I’ll let everyone know what they have to say.
Yeah MIDI Remotes are kinda iffy in 14, although I think I saw this in 13 as well.
I regularly have two entries in the MIDI Remote manager. I’ll finish working on a project, save it, call it a day. Pick up the next day, and when I turn on Cubase, it adds my Novation Launchkey as a NEW controller. My project has two entries for it in the MIDI Remote section. The original one just sitting there disconnected, and the new one. Most of the time when it does this, it no longer lights up the pads and buttons. I have to go in, completely delete both controller entries, and re-add it from scratch, and then it works perfectly until the next time I open it heh. Doesn’t happen all the time but roughly 90% of the time I open a project now. As soon as I reopen that project, there’s a new controller added and it’s not lighting up until I wipe it out and re-add it.
@ Monotremata. Thanks for that info. I’m still in 13 Pro. My MIDI Manger shows 2 sections available at the top. “MIDI Controllers” and “Scripts”.
I’m seeing the 2 entries in the MIDI Controller section. One enabled and one disabled. The “Script” section shows only 1 entry, but it’s has 2 instances (in the “Instances” column). I think you’re telling me you delete the entries the MIDI Controller section, but not in the Script section? Have I got that right? Thanks…
Yeah that is exactly what I see too. I delete both controllers and just add it again from scratch. The weird part is, the Launchkey works, but without the pads lighting up I have no idea what track is selected, what’s armed/soloed/etc, and that’s no fun. Sometimes I can just disable the script and re-enable it and it kicks in, but most of the time I have to just delete the controller and re-add it again.
I cant figure it out. Sometimes everything is just fine, but eventually I’ll open a project and there it goes with the double instances again.
I would add, this midi controller behaviour you describe is not unique to the Softube. I have a Korg Keystage which started showing the same behaviours, no update to the Keystage… Two instances showing as you describe.
Delete and then hitting ‘refresh scripts’ from the top right hand side works the most reliably for me to get the midi connection back after it mysteriously drops. C14 on M1Max Mac.
Interesting, AlanP… So, the problem manifests with various versions of Cubase and with a number of different controllers. Still hard to know where the problem lies…
Just to note, I’ve been in touch with Softube support, who have tried to help, but haven’t been able to resolve this issue. I really liked the Softube mkIII faders for my workflow, but sent them back. When they worked, they were just what I was looking for, but I’m wasn’t willing to constantly address this problem.
I do find it to be more on Softube than Cubase, as the faders worked flawlessly right out of the box. So they could talk to Cubase just fine then. But after the Dec. 17th Softube update (where midi implementation was added) they didn’t. I do hope Softube comes up with a fix, as I’d buy the faders again, if I knew they would work properly.