IT IS THE EXPECTED PORT NAMES okay by sheer blind luck I edited expected port names to the exact name that shows in midi devices and IT WORKS now saves and auto loads my qcon lite in both cubase 14 and 13.050 whoo hoo
1 Like
This is the best way to go 
Hi MC - thank you for taking the time to reply. So, I used your script on my PC and I had no issues. After bricking my motherboard, I took the plunge and bought a Macbook pro with an M4pro chip. I set about rebuilding my music environment (painful experience). When I came to adding my keyboard I used the included Steinberg script. However, I noticed that when I started Cubase the next time the keyboard was no longer mapped and I had to got through the usual process. I downloaded your script and attempted to follow the instructions. For some reason, I could get the script to recognise the keyboard but none of the transport controls worked. So, I went back to standard Steinberg script. However, Cubase does not remember the keyboard (even if I save a new template) when I restart Cubase, which is very annoyingâŚ
Do you have any ideas or is this a cubase bug? best, David
Hi again, please tag me (or hit the reply button) in replies to me, I just accidentally found your reply, I didnât get any notification.
I have a Mac here and everything runs smoothly as before. I would need more info, and itâs better to talk about it in the dedicated thread for my script.
Steinberg doesnât offer a script for the Keylab MK2. Which script are you referring to?
Great!
By the way, I see youâre using the control room. Would you perhaps wish for any sort of functionality concerning the control room inside my script? Let me know if so, in the dedicated wiki of the script.
1 Like
I will M.C
Just let me know where that is! 
Cheers.
1 Like
HI everybody,
Same issue in cubase 14.0.10 and windows with Bjoluc script for my setup âxtouchextendersâ
Cubase leave blank the midiremote at each restart !
Absolutely nut form SteinbergâŚMidiremote is presented as a revolutionâŚno way.
Disapointed fan user.
kind regards from France.
Hi everybody,
I have the same issue than many of you.
When re opening cubade, the xtouch/midi remote controlers disappearedâŚbut :
At home, windows 10/cubase 14.0.10, if I completely QUIT cubase, the issue is here and when reopen cubase, I have to setup newly my midi remoteâŚ
If I only CLOSE cubase project and cubase let the selection projects windows opened. When I select a project in the list, at opening, all devices on midi remote are properly recalled .!!!
There is something that cubase dump some temp files ( I could imagine ) related to midi remote when completely closed, but cubase keep some temp files if you just shut down âprojectâ .
Hope Steinberg could listen it quick, in fact when you close computer for upgrade or any other case. Cubase lost midi remote controlers set up before!
Kind regards from France.
I tried to go back to âbjorn BJOLUCâ script 1.5 version :
with cubase 13, everything is recalled perfectly
with cubase 14, the lcd scribbles show track names but no operational functions available and the âcubase midi remote panelâ is empty, I have to re setup the devices to use them at each restart of cubase ( when closed completely before )âŚ
Thereâs obviously something that change in "managing the midi remote in the cubase 14 version ! in cubase 13 everything is still OK.
Hope somebody could find the solutionâŚkind regards. Happy christmas to all.
I canât be of help unfortunately, however, which Cubase 13 version do you have? Iâm asking because somehow I think that CB 13.0.51 and CB 14 are probably identical when it comes to MIDI Remotes. SO, if youâre on CB 13.0.51 and it works as expected, my assumption is wrong, and this can be more worryingâŚ
Hi,
I work with cubase 13.0.10.
With cubase 13.0.10, everything works fine but with v14.xxx, the midi remote panel is empty at each full cubase restart and I have to setup anew the devices in midi remote with script.
At this time, no solution, I have to go back to use cubase 13 which recall perfectly the 3 devices with Bjornâs script.
Awaiting for any good idea ,âŚkind regards.
Good to know that itâs not 0.51.
Iâve seen the github discussion, the proposed solution was one that came from me, and worked for the user who kindly mentioned the solution in github. The problem at your side is that youâre having different port name prefix for the second extender (or main, I donât know). The way @bjoluc structured his script expects that the extendersâ ports are of a very specific format (the format used is X-Touch-Ext followed by a number reflecting the number of the extender). If you can change your port names to comply with this, it will work (this usually implies registry changes, and is not advised).
Without such exotic changes, I could help you get out of this, but I think that the best approach is that the developer gets to supply a more generic approach if possible. This is because even if we work this out together, and then the developer offers a new update, youâll most likely want to install it, and then get into the workarounds I suggested. This is not good.
And then, of course, if Steinberg admits the whole case as a bug, and fixes it, it would be the ideal.
1 Like
I appreciate yâallâs commitment and itâs great that youâre helping each other out. Please bear with me as Iâm in the last few months of my Masterâs Thesis and donât have enough spare time to reply to the flood of messages reaching me. As to the port name problem at hand, let me quote the relevant docs section:
Note Most extender devices will let you choose an extender number (1,2,3,âŚ) which will affect the MIDI port names assigned to them. If you have only one extender, make sure it is configured as extender 1. For multiple extenders, assign extender numbers from left to right. Some extenders (e.g., Behringer X-Touch Extender) do not give you this choice. If you use more than one of these extenders and have the ability to freely assign your port names (for instance using MIDI over ethernet), assign the port names according to the following pattern:
- Extender 1: âX-Touch-Extâ (default extender port name)
- Extender 2: âX-Touch-Ext2â (default extender port name + â2â)
- Extender 3: âX-Touch-Ext3â (default extender port name + â3â)
- âŚ
No need to change registry entries â just connect the left extender via USB (so it gets âX-Touch-Extâ) and the right one via Ethernet and assign the port name âX-Touch-Ext2â in rtpMIDI.
Good luck with the final stretch!
1 Like
Hi.
Thanks for all the effort you make, Bjorn.
Maybe, I am wrong butâŚwhy it works well with v13 rather than v14 when the 2 extenders+main use the same 3 names in each case ?
The first extender, in the left, is called xtouch-ext, the main xtouch called xtouch in the center, andâŚas I said before, the 3rd device ( the second extender ) is called desktopxxxx cause it runs in http mode because cubase doesnât accept 2 devices with the same nameâŚxtouch ext cannot set up different name in usb mode, they always named xtouch-extâŚ
I repeat that the Bjornâs script work fine in cubase 13 with 1extender and 1main in usb mode and the third device in http.
I cannot understand why it worthâs to change something in case when everything work fine with cubase 13âŚ
As I said, with cubase v14, if I just close project and let open the project selection cubase window, the remote panel recall correctly the 3 devicesâŚno need to change anything inside the script or http translator.
I understand I have to stay with cubase 13 and not take benefits from the v14.
Bjorn did a fabulous work and his involvement is very serious and appreciable.
Apologize for my bad english.
I am more a musician than a geek coder. Lol.
Kind regards.
1 Like
Geek coder here 
, no need to apologize! The names in the script are just for port auto detection, i.e., you donât even have to manually select the ports in the first place. It always works with manual port assignments too, but Cubase 14 doesnât seem to remember these in some cases. Thanks for the kind words @limageurpublic â and for the wishes @m.c!
2 Likes
Is it fixed for any user? Too me it looks like there is no automatic test robots used in cubase production. Regression like this should be very easy to fetch with automatic testing.
Same problem here, I have to setup my Arturia Minilab as midi remote every start of Cubase. It used to work fine in versions before 13.0.51