I am sorry, I found it here in this part of this conversation 
@mat I just released an enableAutoSelect option in v1.2.0. Thanks for the feedback (writing this word in a Cubase forum inevitably triggers unintended associations 
)!
Hi there, I want to assign the MIDI Tracks button so that when it is pressed I can only see the MIDI Tracks. Also for INPUTS e.o. Is this possible and which command do I have to use to accomplish this. Hope some one has got the answer for me? With kind regards, Ron Weber from The Netherlands.
Hi there! I am all of a sudden having an issue where the scribble strips are no longer always showing the track name or the information above the line (on the scribble strip)
Also, when I shut down Cubase 15, the X-Touch and extender do not clear.
I updated the firmware on the X-Touch from 1.22 to 1.25 (same situation on both versions) and re-added the .js script. Also, when I disable the script and re-enable MC in Cubase, everything works fine. Any ideas?
Hi Ron,
i am trying to solve the same thing and looking for solutions. I trying to see some commands in script list from Bjoluc
Hi. These buttons are already assigned in the Remote Control for the Channel Visibility Configurations menu, which is located at the top of the Mixer window (F3). Set up the display of different tracks in Mixer and add Visibility for different buttons. In Remote Control, there are MIDI TRACKS-1, INPUTS-2, AUDIO Tracks-3, and so on. These buttons are also configurable in the main window.
Thank for the script.
I’m using it with a X-Touch extender on Nuendo 14.
I got two issues with it:
- some of the faders are fighting back, the motors block the movement.
There is no automation on the tracks and it changes what channels are affected by it.
What could that be?
It works fine in standart mc mode.
- and I think this is more of a Nuendo issue. The controller needs to be setup for every projekt. If i enter a new project the controller is not there and I have to ad it again manually.
I’ve just had exactly the same fault on C14, after years of everything working fine.
Some of the tracks have names on, others don’t. When you exit the project, the X-touch and extender do not clear. This happens on an empty project, as well as saved ones.
I’ve tried:
- Deleting the json and .js scripts, the re-installing a freshly downloaded .js script
- Running Cubase 13, which is still installed. Same fault.
- Numerous combinations of switching off and on again
- Restoring my PC to an earlier time (Windows 11)
- Uninstalling C14 and re-installing a slightly earlier version 14.0.10
- Unplugging everything except the X-Touch
Nothing works
Did you solve it?
I have seen similar things. It all seems so random. I can come back later in the day and it all works again.
(This is WIndows 10, Cubase 15)
I tried all of the same
I have tried all of the same things you have but no solution. I have gone back to the the MC solution until there is a fix. Very frustrating.
@tonesearch I’ve made some progress. The problem is caused by a Windows update. I suspect it’s an ‘improvement’ to the new Windows Midi Service that Microsoft have been rolling out. Here’s what worked for me:
- Use System Restore to restore the PC to the earliest possible time (For me it was 9 days ago).
- Goto Settings>Windows Update and pause updates for a couple of weeks.
- Go to Settings>Windows Update>Update History and uninstall recent updates, one at a time, starting with the most recent one.
- Test Cubase after each uninstall. If the issue still exists, keep uninstalling updates as long as Windows will let you.
- If Windows runs out of updates you can uninstall, do a Shift-Restart on your PC. Go to Troubleshooting, then Uninstall Updates there. Select ‘Uninstall the latest Feature Update’.
Unfortunately, I can’t tell you which update caused the problem because I thought that the new Windows Midi Service itself was the issue, and I was uninstalling everything until Windows started using the old legacy midi driver. But it never did, and by the time I got to step 5, I happened to launch Cubase again and it was all working - with the new Windows Midi Service.
I realise this solution won’t have anyone celebrating. Either something’s wrong with the updated Windows Midi Service, or it’s working fine but has broken Bjoluc’s script, and I think Bjoluc has long given up on any further development.
Still, if anyone finds out exactly which update broke it, please post it here. We can then contact Peter Brown who’s in charge of the new Midi Service and he might be able to find a solution.
All the best, Paul
This is excellent, Paul! I am out of town but will try to replicate your steps when I get home and report on my findings. Thank you!
Mike
Hi Paul!
I followed your steps and after a few restarts, the script is working again. The thought of no new windows updates is a bit disturbing and I hope it gets straightened out. Are you going to contact Peter Brown?
Thanks again!
Mike
Did you, or anyone else with the problem, happen to notice if the Midi Remote surface had of its own accord decided to connect to different midi ports?
If for example midi from Cubase to Remote device was altered it would result in some of the behaviours reported.
I ask because I am seeing this occur under some conditions with the Icon Platform M+ midi remote with the new Windows MIDI services active - this with the restart of midi services in order for loopmidi to work (which I note they now have a fix in release candidate form available, real one still a month or two away according to the info on github).
Hi Mike, that’s great news! I can’t really contact Pete yet, as I don’t know exactly which updates are responsible. However, I suspect it’s the same issue encountered by users of VirtualDJ:
I’ve set my PC to pause updates for 5 weeks, and I’m hoping MS will have sorted out the problem by then, so we can continue with new Windows updates. If not, I’ve saved system images and restore points galore!
It’s possible, and could account for the sporadic missing track names etc. If Windows Midi Services is really doing that, then we can expect a fix to be released fairly quickly, as companies like Nektar and Softube have products that rely on Cubase’s Remote Midi and will make some noise about it.
However it’s also possible that Bjoluc’s script worked perfectly with the slow legacy midi service but is tripped up by the speed of the new one. Pete discusses this on his blog. If that’s the case, we’ll need someone good at scripting to modify Bjoluc’s script to cope.
My hunch is that the new WMS will be fixed sufficiently that everything starts working again, but I’ve always been an incurable optimist!
And all this time, Microsoft was telling me it is a bad thing to be on Win10 because they aren’t “enhancing” that software. I guess it was pretty clever of me to not switch to Win 11.
On the GitHub page, I saw that users of the script started making demands about what else should be added and how it should be used. So I wouldn’t be surprised if the programmer, who is providing everything for free, eventually loses interest in continuing to develop the script.
At the top of the thread, I see 2,800 clicks to the GitHub page, but only 66 clicks for “buying me a coffee.” I find that pretty inappropriate. That’s how life is- wanting to get everything for free and then being ungrateful - at some point, that becomes a problem…
Well I think most of us on this thread have made it clear how grateful we are and have bought Bjoluc at least one coffee. 82 users on this thread and 66 coffees bought isn’t too bad.
As a programmer, the law of diminishing returns sets in and you naturally move on to more exciting projects.
bjoluc’s script is really well written and robust. When Steinberg implemented Mixer Visibility into the Midi Remote API, the script handled it straight away with no modifications needed.
if the new Windows Midi Services have broken it, I don’t think it will need much modification to work again. Bjoluc was always going to move on. Someone else will take it forward.
Nonetheless, I still suspect WMS is at fault rather than this script.
All the best, Paul