@SignalsMusic , @Crincy, @bjoluc . This thread has so many posts now that I think the requests for SetFollowVisibility have become somewhat submerged. So I’ve started another thread devoted specifically to this function. I’m hoping that users anxious to see it implemented will post there so the Midi Remote team will have more awareness of us.
1 Like
Hello! I just implemented v1.10.1 for my xtouch and extender. Everything works great except for the fact that the scribble strip colors only show up on the xtouch, not the extender (which are always all white). Any thoughts as to how to fix this? Thanks in advance!
You probably need to update the firmware on your extender
1 Like
Just wanted to offer a huge THANK YOU for creating these remote scripts! I’ve been using the X-Touch script for a while.
I thought my SSL UF1 was going to be a white elephant until I tried the UF1 script - BANG! Now the UF1 is a useful tool. The script has a few oddities, but hopefully you will be able to develop it over time.
Much appreciated.
Let me echo my appreciation for all this work. Is there a “tip jar” we can contribute to on Patreon, paypal or whatever?
I installed C14 last night and the X-Touched worked immediately with having to do anything (it was working on C13, so that carried over.)
I don’t have the extension module, so I can’t speak to any issues with that. However, I did notice one thing. If I have a volume envelope with a atraight line, say rising at a 45 degree angle, the X-touch fader goes bonkers, jiggling around. It moves consistent with the envelope, but it is as if what used to be 10 or 20 incremental steps is now 500 steps.
It seems a lot different from C13 but I am not certain. I will try to test that same thing under C13. It isn’t a huge problem, just noisy.
==================
On edit, I have tested both C13 and C14. There seems to be a bit more chatter on C14, but it is hard to tell because there are other strange behaviors when I use the X-touch buttons to shift the channel strip assignments. In particular, when I do that shift, there is less chatter, but a second fader (assigned to a FX reverb track in this case) also starts following that envelope, even though there is no envelope for that track. This phantom envelope thing only occurs when I shift the X-track channel by one or more. And it seems to happen about the same on C13 and C14.
I should probably install the latest version of the script. I’m probably 9 months behind.
Hi another strange behaviour I notice on my C14 is that it doesn’t remember the xtouch midi remote… each time I start the Mac, then again I have to reinstall the script and reassign it to midi channels… BTW then I got 2 midi remote Xtouch (both Main and Extender) one connected and the second not connected so I could remove it… but… each time I restart the Mac I have to do all the sequence again… it doesn’t happen with NI Kontrol MK3… any ideas?
Cheers, Eriberto
I would be happy to start a new thread for this if you prefer. I have some strange behaviors from my X-Touch. I am running Cubase 14 (but same results on C13) with Windows 10. I believe I am using the latest script (1.10.1)
You can see a video that demonstrates the problems here:
In this case, I created an empty project and added 4 audio tracks (A, B, C, D). There is no audio recorded, just fader envelopes. In the first part of the video, the faders move as expected, except that they have a fluttering, chattering quality. I thought they used to move more smoothly. I don’t think it is a hardware issue because all the faders act that way.
In the second part of the video, I shifted the tracks one fader to the left, leaving B, C, and D active on the X-Touch. In that case, the faders are all mixed up.
Any ideas about these issues?
It looks like you have integrated the XTouch twice, once as a MIDI remote with the fancy script and once as a legacy remote control Mackie Control. Is that possible?
If so, all you have to do is to remove the MackieControl as legacy control device and it will work smoother. But still, a bit fluttery is normal, depending on the moving speed and the ramp.
You are 100% right on all counts. When you say "remove the MackieControl as legacy control device ", I didn’t see any way to “remove” the Mackie Control per se, but I set the MIDI input and out each to “Not Connected”. Is that what you meant?
It still chatters a little, but the goofy stuff from the second half of the video is all fixed now.
Thanks a million !
Great, you’re welcome!
Disabling the midi input works too, but you can remove the legacy Mackie Control here:
(sorry, German Cubase
)Cheeers!
I don’t know how I could have missed that. It is right there.
The faders are definitely smoother – certainly not silent, but it doesn’t really matter in the digital realm. Clearly the X-touch was receiving two streams of commands to move those faders, and they didn’t always sync. In other words, if one of the instances was slightly behind, then the fader might have received: two steps forward, one step backward, two steps forward, etc.
Please any help here? Sorry is really time wasting… adding some screenshot
Hi another strange behaviour I notice on my C14 is that it doesn’t remember the xtouch midi remote… each time I start the Mac, then again I have to reinstall the script and reassign it to midi channels… BTW then I got 2 midi remote Xtouch (both Main and Extender) one connected and the second not connected so I could remove it… but… each time I restart the Mac I have to do all the sequence again… it doesn’t happen with NI Kontrol MK3… any ideas?
Cheers Eriberto
Hello,
Since your scripts works for the X-Touch and also the extender, is there any chance that it also works for the X-Touch Compact, or is that a completely different kettle of fish?
Hi problem solved I post here because on my opinion there’s something for Bjoluc.
It seems that the problem is related to the x-touch extender interface name, I’m on a Mac, in the script the extender interface name is x-touch-ext BUT in my MIDI AUDIO CONFIG appears as X_TOUCH_INT and is not editable, because if I change the name ad the device the resulting name is DEVICE+INTERFACE and so are more problem to solve.
At the end I have to set the Device name as the Interface Name anche modify the script changing the extender name according to what I said before.
Probably, and this is why I think a Bjoluc help is needed, the script try each time to assign the default midi channels, but not finding the right name dimiss the surface letting adding you the one with the correct channels, BUT and this is I think the problem, the process has to be done each time, because first of all the script search for its names.
Maybe I’m wrong but this solves the problem.
NOT SOLVED WHY I SEE 2 XTOUCH…
Cheers, Eriberto
Does anyone of you have problems with the zoom and scrub toggle buttons in Cubase 14 or is it just me? They won’t toggle, but only flash when pressed, but the mode doesn’t change and so doesn’t the led state.
Also reported here: Zoom & Scrub Mode don't work · Issue #53 · bjoluc/cubase-mcu-midiremote · GitHub
I’ve had a similar issue a couple of times with C13 and C14. In each case, going to midi remote manager, disabling then re-enabling the script seems to solve it. Before discovering that trick, I noticed that projects I saved when the issue was present retained it when I re-opened them. However, projects saved without the issue present worked fine. It may be worth starting an empty project as a test to see if it still happens or can be fixed with disabling/re-enabling.
Zoom and Scrub Toggle still won’t work for me in C14. 
I tried everything (removing all of my customization, changing MIDI ports to RT and DirectSound, disabling and enabling scripts, new or older projects, and the problem also persists in C13).
I’d be really happy if someone could point me at resolving this.
That’s really weird. It’s probably not much help, but there’s one other thing I’ve noticed: When everything’s working normally, if you have a drop-down menu open (For example, you’ve just pressed ‘File’), then the issue you describe will occur, but as soon as you close the menu, operation is normal again. This makes me wonder if Cubase thinks a menu is open. I know that’s not much help. Perhaps @bjoluc can shine a light on things. Best of luck, Paul.
1 Like
Hi all, and speccially thanks for @bjoluc for Making Cubase Great Again 
Been using this script perfectly in C12 for a long time.
Now with C14 it works ok but each time I open a project I have to add the Surface in Midi Remote Script.
On C12 i noticed that if I opened first a project with the Script working , the new project works also ok. But this is not the case with C14. I open a project that was saved with the Script working but each time I restart C14 I need to Add the Script again.
Anyone else?
Cheers,
Weird. I was using C13, upgraded to C14 with no script problems. Does this imply it would only happen going straight from C12 to C14 I wonder?