This issue has cropped up on this topic before.
IIRC, there are three potential solutions:
You also have the Mackie control enabled in Cubase (Under Legacy controllers), which conflicts with the more modern Midi Remote Script that this script uses.
You have the multiple instances of the X-Touch in Midi Remote Manager. Delete one of them.
The X-Touch is receiving midi information from VST instruments because the wrong checkbox is ticked under Control Room>Midi Devices (I think - I don’t have Cubase to hand as I write this).
Go to Bjoluc’s Github page for this script and read the Readme carefully. It details all of these, and you should be able to get it working if you follow the instructions to the letter.
You’re using the wrong method to import it. You don’t need a .midiremote file. Go to Bjoluc’s original Github page for this script and follow the instructions given in the ReadMe Section.
The solutions to both recent problems are found in Bjoluc’s Github page, in a ReadMe that’s quite comprehensive. They are also found in several places in this topic, but the topic has gotten long now, with 382 posts, so users understandably can’t be bothered to search through it all.
Yes, using the Legacy Mackie Control would work for users who just want to make music and don’t want to spend time delving into the ins and outs of their computers, but the difference between Bjoluc’s script and Mackie Control is night and day. I’m not particularly computer literate, but it’s really been well worth the effort to follow the instructions carefully and read the posts here. Especially now that Steinberg have fixed all the significant bugs in Midi Remote. It works like a charm now with the latest versions of C13 and 14.
Yes, I got the script up and working fine, and while it generally expands on the MCU feature set in awesome ways (track colors, better display info) it still lacks in certain areas for multi-controller setups that are deal breakers in my production workflow.
Add on top of that the fact that the API itself is still in progress, buggy, and prone to disconnections and other issues and the net result is that midi remote is just not workable for me in a pro enviornment.
But the bigger point is this - even if the script gets into a state that’s perfectly workable now, Cubase (and the midi remote API) will keep getting updates, which means the script will probably keep breaking and needing fixes to keep up. I just don’t think the tech community within pro audio is large enough to always step in to fix these things in a timely manner, so if reliability and stability are to be had it really has to be dealt with by paid, full time devs at Steinberg or at the control device manufacturer level.
Tries removing scrpt. tries cubase 2 tries cubase 1 on anotjer windows (dual boot) and tried it on mij laptop witj cubase 11 and 14// transport works, but the fadere keep moving even without usb cable attached is there a factory reset maybe?
Out of interest, what areas do you mean? I’m using it with X-touch + extender + Nektar cs12 + Softube Channel MkIII + 2 stream decks. No problems since 14.0.20 came out, but that was quite recent so maybe I’m heading for a big crash! No need to reply if you’re busy. I’m just curious.
Usually switching it on and off is enough. I’ve never had to do a factory reset. If the faders are moving without any usb cable attached, that points to a problem with your X-touch, rather than the script. A factory reset may be possible - you’ll just have to do some googling.
That’s good to hear. I’m stuck on the last release of 13 for awhile forward as I’m dependent on the old score editors feature set, and on that at least using midi remote causes much more overall instability, as well as frequent disconnects of the midi remote devices. Anyway I outline the issues here:
The bigger issues are primarily with auto select and visibility configs. Visibility configs weren’t possible at all until a few months ago, which made the script a non-starter, and while the new implementation gets me closer it’s not quite good enough.
The inability to disable auto select also causes a bunch of small problems, biggest of which seems to be Cubase freaks out if I try and grab more than 1 fader at a time to draw automation on.
I’d be curious if the Softube implementation overcame any of that, but I read they have a track limitation with their MCU script so that’s a non starter too.
@GPnicolett , thanks for that. I don’t think the Softube implementation is very thorough - I’ve turned it off on my Console 1 Channel. My biggest problem has been with (often expensive) third party VST plugins causing memory leaks and crashes. I honestly dont know how you pros cope. The main reason I’ve gone with the Nektar CS12 is it’s built in integration with the stock plugins which are reliable and resource light on the whole.
It’s quite rare I try drawing automation with multiple tracks, but I can see how that would be a deal breaker. I get the impression Nektar have managed to develop a good relationship with Steinberg’s MR team and have spurred them into fixing the more egregious bugs. Hopefully Softube will do the same and sort out auto-select disablement. If they do, we’ll all benefit. All the best.
Ps. I don’t think there’s any difference in Midi Remote between C14 and C13. Steinberg seem to update both at the same time.
Hi there.
I still got the problem that everytime i open an existing project, i have to choose the Midi Remote Device and configure it. After that, erverything is working fine.
Is there a solution for that ?
Blockquote
Hi there.
I still got the problem that everytime i open an existing project, i have to choose the Midi Remote Device and configure it. After that, erverything is working fine.
Is there a solution for that ?
Greetings
Oliver
me too, really annoying… any help appreciated… cheers Eriberto
is there a factory reset maybe?