Curiously I just updated my Mac to Monterey, and now it doesn’t manage to figure out the correct bank.
I think I have to revisit my script and see if it needs some adjusting post Monterey in how midi messages to and from the virtual ports in Mac work now… maybe…
Anyway, I really hope this is something Cubase 12 will fix without any hacky scripts. This post did get quite a lot of votes, so hopefully it is something Steinberg paid attention to.
the script doesn’t open also my cmd gave some error after typing install pip … now nothing is happening in my cmd after typing those commands and says this
‘pip’ is not recognized as an internal or external command,
operable program or batch file.
did everything you told but my platform nano doesn’t work if it’s not selected in the Mackie control in-studio setup so what’s the benefit ?? I’m still having those 8 track poop bank
now everything is working fine but I have to open the script all the time, is there any possibility that we close the script box and use everything the way it was working while staying open with the script?
Just wanted to say thanks a lot for this! Works for the SSL UF8 on Mac for me.
1 Like
Excellent! Just a question, which version of Mac OS are you running?
I noticed that Mac OS Monterey (and maybe Big Sur as well) seems to behave slightly different, and I may need to do a re-write of the script potentially, as I wrote it when using Catalina.
Seeing as Cubase 12 is happening relatively soonish, and this post has a lot of votes, I am hoping this will be something we can just let Cubase handle if they pay attention to this topic.
1 Like
I’m on Big Sur. I have noticed some issues though - I’m using it on a 600 track scoring template, so it definitely takes a few seconds (~4) to re-bank when I select a track. And the bank keys on the controller don’t consistently change the bank - it seems to just get stuck on the current bank until I select another track in Cubase. Hopefully Cubase 12 comes out soon and they fix this like Logic has. I’m leaning towards returning the UF8 and just getting an Artist Mix since the Avid iPad app is pretty flawless and Eucon seems like a much better protocol than MCU.
Yeah unfortunately it’ll take longer the more jumps it has to make, as there’s no clear way to determine how far to jump without jumping to a bank and checking if it’s the right one, so it is literally skipping through everything and testing if it landed on the right one.
If Steinberg does an implementation of this it’d be instant, as they know which bank you are at all the time.
The latter problem you experience where bank keys don’t work, well that’s by design.
When I made this I wanted banking to be disabled on my mackie controller, and have it controlled by track selection in Cubase and via my Console 1 instead. So it only follows, it wont work banking on its own.
Technically I could make that work, but it was not a priority, as I didn’t have a use for it myself. I did this just to solve my own problem, but shared the script as it was in case anyone else had a use for it.
not working in WIN11 ,but thanks that. Voted
I got inspired to go back in with coding, now that i was having some issues with the current script using the Mac OS IAC midi devices, as they apparently have some new behaviour since Big Sur or Monterey.
New version of this is on the way now. I am re-writing the midi loop now in a way where it should have significantly better performance, and no need for a sleep timer (probably, but initial tests seem to indicate there’s no need anymore now).
I migrated the script to work in python 3 now.
It’s still under construction, but I am refining the logic, and right now I am keeping track of which direction to bank if you use track selectors on the mackie controller, and I’m considering options for figuring out a faster algorithm for auto-banking, which really shouldn’t be too bad.
Ideally I want to omit the need to work with a max number of skips to attempt, and have it automatically work it out.
At this point I should add that I am mainly targeting a single fader controller (I am using the Behringer X-Touch One), and as I don’t have a mackie controller with 8 faders, I don’t have any way to test how the following things will behave on those.
A thing I’m working on is setting a nicer track name on the display, as well as opening up for using 2 rows of the LCD to display longer names.
This thread opened up for some ideas regarding this: Creative thinking needed (?), retrieve track names from Cubase to MIDI or OSC - #22 by Shor
Basically making use of the MCU commands to go into eq, channel strip, aux send modes you will get a longer track name, so I am thinking about making use of this to read out track names. It’s a bit tricky to figure out how to do this in the best way.
I already made some functions for conveniently setting names making use of both rows, but I need to work out how to override the original mackie behaviour in a way where it all works without glitches.
Rough idea right now is to figure out if a track change is performed, and then switch modes to get a long name, and then switch back to the ‘normal’ mode again.
The names will come after working out a better way to autobank, and I am hopefully going to be done with that this coming week.
Unfortunately this is really an ‘as is’ solution, but I’m thinking this version will be significantly easier to work with and setup. I’m hoping there wont be more configuration than naming your midi devices.
1 Like
I keep following this thread and your new inventions, because it’s really cool and extremely useful. And yes, you are a great fellow, many like me use your script - it’s excellent. Just a week ago, I came across the fact that the script really stopped working on Windows 11 (possibly after the next last update), but it simply stopped opening. We will wait for your new (updated) script, perhaps it will also work already on the new Windows 11.
2 Likes
Thanks 
I’m curious, what actually stopped working?
Maybe python 2 problems since it is now deprecated…
Anyway, I’ve been struggling to make time on my end, but trying to get a few minutes of coding and testing in on the mornings now on the next version of this, and it’ll happen.
For anyone interested in potentially trying it when it’s “done enough” I can infor that you’ll likely need to update to python 3.10 or later, and it’ll still need mido as well as rtmidi modules to run.
I can’t really say any estimate on when I’ll be done, as my coding time is very limited. The auto-banking logic is a bit tricky, so I’ve been working on making it a bit more abstract so it’ll be less keeping track of numbers and weird sysex (hopefully).
On the old one I locked away banking from the controller, but I am considering allowing for that now, but maybe with an option. The problem there is that changing banks manually would trigger it to start searching for the bank with a track in it, so to override that I’m thinking that banking to previous bank might just default to selecting the last track in the bank, and banking to next bank could select the first track in the bank.
Similar logic is already implemented now when track switching. If you track switch to the next track and you are currently on the last track, it automatically sends a next bank, and selects the first track in the bank. - Prev track when on the first track in a bank will send prev bank, and select the last track in the bank.
Makes sense to me at least.
I also added a debug mode now, mainly for development use, which lets you use one more (or many more) midi devices to also send mackie commands. I’ll leave that in probably, as that means that you can, if you want to, map mackie controls to any other midi device if you want. Not sure if there’s any real use for this, but I used it now on my keystep just so I can send mackie controls that my single fader control doesn’t have. Such as changing to EQ mode, Insert mode etc… not actually sure how useful that is on a single fader controller yet, but it was neat seeing my plugins on the LCD. I do intend to figure out some way to use this to get a longer track name though, and then using that to set a nicer name on my controller. This might have to be an option you can use or not use though, as I suspect these hacks might make user experience annoying on an 8 fader controller.
Hello.
Does cubase 12 support auto banking?
It doesn’t.
I guess the forum votes didn’t make much of a difference.
Glad I didn’t abandon this project haha
Hi,
Does anyone know how I can set up my x-touch in Cubase 12?
I’m clueless… sorry.
I use my X-Touch One with Cubase, albeit with my hack in this thread…but it’s easy to set it up.
Hold down the encoder (so it clicks) as you power it on, turn it so Mackie Cubase (can’t recall the short name) is selected, and click the encoder again.
Then set it up as a Mackie controller in Cubase under controllers (can’t recall exact names off hand) and set midi in/out to be your X-Touch.
I use a Console 1 Fader (without Console 1 controller) with C11 and C12 Pro, faders follow you where ever you go- I totally forget which bank I’m in- a little white led indicates the active track, there is bank switching too- using Console1.VST3 software. Mute, Solo- 3 Transport/ programmable keys- 10 touch motorized faders, led on the console next to each fader (a little limited ie. red and Orange look alike) match track Colors; Volume- built in Drive (like pre gain) + Character (tone). Also came with American class A plugin.
Not wanting to bank switch drove me to it, I have other controllers with knobs, faders, generic, Mackie and HUI control- . New MIDI Controller feature in C12 needs some work- to include 3rd party VST parameters control beyond 8 QC limit- Console 1 Fader is still working as expected.
I got a Console 1 with the both the regular and fader versions, and it’s amazing.
My initial script for auto-banking mackie controllers work together with it, so mackie controller banked if needed when selecting tracks on C1 or in Cubase.
Next version I’m working on now should work with it as well, so that’s what I intend to use personally.
I don’t want to jump the gun on this, seeing as my time to spend programming this new version of the auto-banking has been more limited than I had anticipated, but I think I might be close to have an initial version of a reworked script for this.
I have coded a smarter logic for figuring out how to bank, and determining when we are in the correct bank.
No more sleep timer config, no more max jump settings. I have a way to traverse through all banks now until track is found, and if a non valid track (such as group track, chord track, midi track) is selected, it’ll scan up and down the bank list once, and then no more until another track is selected.
Right now I am cleaning up code, and need to refactor some parts to make it neater, but it looks like I have about 3-4h tonight for some coding work, so I am hoping I have a test ready version.
Does anyone want to give a hand in trying a new version of this when the intial version is done?
I run this on Mac OS Monterrey and current version uses Python 3.10. Some earlier version of Python 3 might work, but I can’t guarantee it.
I don’t have a way to try this in windows really… possibly I could see if it just runs in Win 10, but no way to test Win 11.
To run it, you might need to have a little bit of know how to at least install python and modules, as well as potentially needing to know how to set up a virtual midi device.
Setup needed by a user just setting up which midi ports DAW uses, as well as which midi ports your hardware uses. Running the program once without doing a config will prompt an error, but will also list available ports on your system, so that’s what you’d need to edit in one of the files (the file is just called midiconfig.py and should be straight forward).
Ideally I want to make this a bit more beginner friendly to use, but at least this feels way way simpler to set up than the initial version.
Hi! I’m ready to check and test it as soon as it’s ready for you. I work on Windows 11, I also have Windows 10 on my laptop.
The controller is still the same as your Behringer X-Touch One. If there is a step-by-step instruction like last time, I can do it.
Using loopMIDI, everything worked out as this program is available on both Windows and Mac.