All MCU based controllers using the Cubase Mackie Remote Device will have the same problem - the Nano will not autobank.
On the bright side though in Cubase 12 with Midi Remote implementation it does auto bank. I have my Icon Platform M+ in MCU mode (which is the same for all MCUs, including Nano) and its autobanking.
If you have Cubase 12 you may find my Icon Platform M+ midi remote script will work with the Nano for the first fader in it anyway. The script is on the develop branch in this repo GitHub - woodcockr/midiremote-userscripts at develop
It’s not complete nor released yet but the basic mixer functions are working so its probably suitable to test with the Nano.
can anyone help me run the script? i found all the ports and getting this:
C:\Users\ILAN>python C:\Users\ILAN\Desktop\mcupython-main\mcupython-main\hackiemackie.py
[13:37:14]: Auto-Bank Enabled
Traceback (most recent call last):
File “C:\Users\ILAN\Desktop\mcupython-main\mcupython-main\hackiemackie.py”, line 538, in
main(*sys.argv[1:])
File “C:\Users\ILAN\Desktop\mcupython-main\mcupython-main\hackiemackie.py”, line 297, in main
outport = mido.open_output(conf.HWOUTPUT)
File “C:\Users\ILAN\AppData\Local\Programs\Python\Python39\lib\site-packages\mido\backends\backend.py”, line 112, in open_output
return self.module.Output(name, **self._add_api(kwargs))
File “C:\Users\ILAN\AppData\Local\Programs\Python\Python39\lib\site-packages\mido\ports.py”, line 265, in init
BasePort.init(self, name, **kwargs)
File “C:\Users\ILAN\AppData\Local\Programs\Python\Python39\lib\site-packages\mido\ports.py”, line 86, in init
self._open(**kwargs)
File “C:\Users\ILAN\AppData\Local\Programs\Python\Python39\lib\site-packages\mido\backends\rtmidi.py”, line 194, in _open
self.name = _open_port(self._rt, self.name, client_name=client_name,
File “C:\Users\ILAN\AppData\Local\Programs\Python\Python39\lib\site-packages\mido\backends\rtmidi.py”, line 100, in _open_port
rt.open_port(port_id)
File “src_rtmidi.pyx”, line 586, in rtmidi._rtmidi.MidiBase.open_port
File “src_rtmidi.pyx”, line 220, in rtmidi._rtmidi._cb_error_func
File “src_rtmidi.pyx”, line 408, in rtmidi._rtmidi._default_error_handler
rtmidi._rtmidi.SystemError: MidiOutWinMM::openPort: error creating Windows MM MIDI output port.
Windows only supports multiclient MIDI (and Bluetooth MIDI) using the new WinRT MIDI API. This is supported by Cubase 12 and Nuendo 12, though it is an option you have to enable. It is not supported by earlier versions of Cubase and Nuendo.
Would this feature request make a Faderport (1 fader) automatically snap to ANY track I have selected in a session? Right now it only snaps to 1-8 then would have to change bank.
I know it is possible to code this, as the Faderport works perfectly in Reaper, and of course Studio One. Whether I’m on track 1 or track 250, the motorized fader immediately snaps to that track’s volume.
Would love to be able to get this to work in Cubendo.
I have decided to move on from mackie hacks, as the new Cubase Midi Remote Editor is an easier way to solve many of these things.
It’s unfortunately a little bit buggy for some things, but overall I’d advice running your controller in Midi mode, and utilizing the new midi remote editor. I think someone made a script for the Faderport 8 which is probably not too bad to adjust to work with a single fader.
OMG! I just found a Faderport (1 fader) script for Midi Remote and it makes it behave exactly as I was hoping! Had no idea the motorized faders would still work with Midi Remote.
Hello Shor. Please tell me it’s been so long, is there any news on autobanking together with the Behringer X Touch One? Have you tried to create a script in Cubase 12 and its Midi Remote?
Hi,
With C12 I did decide to jump ship with it and use exclusively the Midi Remote editor since, at the time, it seemed like the best route as I’d be able to replicate all the features except for the scrub wheel.
I did make a basic MIDI Remote that only had a single bank and worked as I wanted it to, but I have since then actually sold the X-Touch One and moved to using my own midi controller I programmed, so I could avoid having to do ‘hacks’.
That said, the X-Touch One will work with the mapping assistant in Cubase once Steinberg fixes some of the bugs with motorized faders and endless encoders.
Unfortunately since I no longer have one, I can’t really easily keep working on scripts for it, but technically speaking it shouldn’t be too hard to at the very least make a script (or even just using mapping assistant) to have it work as a single channel controller that follows track selections.