Im just trying to do some basic stuff that has been missing from Mackie control for decades
eg
Double click bank left and right creates home and end functions on mixconsole. Specifically it selects either track 1 in current visible channels or last channel - 8 (for bank control which is easy to do in Live tracklen()-8)
Im using a basic legacy remote because the API for remote editor is missing some crucial items and tbh most of these are muscle memory and do not need a UI. These are gestural extensions.
BUT
even though the bank has chased to the correct position and is selecting the first channel, this information has not updated on the control surface (BCF2000)
If I select a channel it jumps back to the last position of the fader banks and the corresponding track in it.
If I manually move banks to the position, it works fine.
Am I missing something?
How can it be this hard? Spent hours on trying to track it down but I give up
Also not to confident of getting an answer here as the most of the last handfuls of posts have no replies…
Ill try in other words
1, I use a midi note on msg in legacy/remote to select the first channel in the mix console by selecting the first visible track
2. The track, as per the mixconsole pic becomes selected and the mixer bank moves to the correct location eg presume it was near the other end of the channels and it is now at the front. It is visually indicating everything is as expected.
3. However, the hardware does not update and move the faders etc
hth
The feedback to the controller is already by mackie control
Im intercepting the hardware msg in BMT and adding gestures as an extension. As well I tried it with a return/out midi port but even if I select the track via mouse after using the same as a PLE, it has the same issue and thinks its still in the last bank position
In other words, its the same as the ui doing the controlling and it then sends the output to the MCU from the main Mackie control. This GR is really just controlling Cubase
Ok I stripped it all back and I think the deduction from it all is that Cubase does not respond to the UI>Mackie
Start with a plain vanilla or any project.
Connect mackie control directly to Cubase ie midi ports
When control surface is banked, movement is sighted in mixconsole as expected
When user clicks and selects a channel in the mixconsole, the bank, the bank moves as expected and channel is selected but the control surface does not update to reflect the new choices. ie on the mackie display, it still shows the existing bank track names not the currently indicated one.
hth
Mackie Control Settings
Smart Switch - Short
Autoselect on
Relay OFF
I’ll give this a try when I’m in my studio with my Mackie.
But that might take me awhile as it’s kind of in the middle of a construction zone right now. So if someone else reading can check this out sooner, that would be great.
Thanks for the offer…yeah Im in constant state of prototype but I get it…I really need to commit Its just so difficult when such basic things dont seem to be working and they are so crucial to efficient muscle memory when working = huge improvement in creativity and lessening of fatigue…especially for quick turnaround jobs
To be clear, what current process or function is making the controller update properly? In other words, how do you know the controller can update from the DAW at all? You said in your first post that “this works fine and does the job” but it also sounded like it didn’t do the job to update the controller. Is that right?
Before we go any further, post a screenshot of your BOME routing matrix so we can confirm the routing, like this:
In my example, I have that green connection from the Midi Fighter Twister to Virtual 5, and then in order for my controller to update, I had to make an additional connection from Virtual 5 (at the bottom left) and route it back to the Midi Fighter Twister.
My apologies if you know this already but I just want to start from the beginning so we’re not doing any guessing.
Lastly, consider doing the Mackie Control setup for everything but those two buttons. Then use the new MIDI remote manager to program only those two buttons as bank buttons but leave the rest of the controller as a Mackie Controller, if you feel that the new remote manager is lacking otherwise.
I did this for my StudioLive 32SC mixer. The parts that work better as Mackie, I left as Mackie, and then since it’s all MIDI anyway, I just programmed the other stuff in the new MIDI remote manager so it’s like a hybrid (best of both worlds).
In other words, the graphic indication looks like its doing the job…but Cubase is not sending out the info back to the BCF…its sending out data but it is to the previous bank position.
In other words, I removed all BOME and just used BCF in and out…plain vanilla so its easier to track down…and put simply, if I click on a track not in the mixer bank, the mixer bank moves to include the newly selected track but it does not send the new position info to the BCF if that makes sense.
If I use the BANK<> buttons on BCF, the banks move as expected, if I use the UI, it does not.
Yeah, the split in the clause is the BUT on its own line
Thats the exact problem…forget where the buttons come from…try and get the controller to do a simple home or end (like I said this took the best part of 5 minutes in Live) eg Select the first track in the console mix and try and get the bank to follow…it graphically shows its there and that where the problem is…you cant use the BCF then because it has not been refreshed (ie if you use the UI or a PLE)
Thats the whole point of gesturing and the remote editor is pretty much useless unless you program it/API and Im not going back to the verbosity of Java…Python maybe but never Java again…makes me vomit when Im meant to be making music.
I just cant understand that its 2024 and gestural behaviour still isnt helping us. Simple example Bank <> button
Single Click go 1 channel
Click and hold > trigger time = 8 channels <>
Double click go to home/end
Select channel buttons
Single click = select channel
Press and hold = jump to 1st track in folder group eg Vox/Guitars etc
and so on…(where the 8 selects represent 8 folder groups
Thats how I do it in Live and its so frustrating that its such a kludge in Cubase which is my more favoured app
I finally got back into my studio and can confirm this behavior. When a new Channel is selected in the MixConsole the graphic indicator for the Fader Bank moves, but the Bank itself doesn’t seem to change. If I move a Fader on the Controller the Fader that moves in the MixConsole corresponds to the initial Bank & not the relocated Bank.
This is using Cubase 14 & the OP is for 12, so this has been around for awhile. I never noticed it as I apparently always use the Bank Shift buttons on the Controller.
Thanks @raino
Its only become apparent to me because with a lot more experience, simplifying workflows becomes so much more obvious…
I def dont want to upgrade atm as there is basically nothing that benefits me in 13 or 14…i already use Live for the more modular/modulation based and i simply use Kore, reaktor or pure data if im really toing to drill in. If there were substantial workflow or remote editor was finished i might think about it but the waste of tume sorting issues from 10>12…no thanks …will older versions get the bugfix ?
Unfortunately no, although very rarely there have been “final” updates to previous versions, and even then, it’s ususally just a “point” update to the N-1 most recent release.
There are many cries on the forum for Steinberg to forego feature additions in favour of fixes to long-standing issues, but the market dictates that shiny new stuff gets priority over utility and stability.
I figured out the reason why there are no issues with Live (it seems) is that everything slaves to the session box and the updates to the controller originate from there hences its always in sync
There is simply no data going back out in Cubase except for
627823 - MIDI IN [BCF2000_To]: 90 33 00
627823 - MIDI IN [BCF2000_To]: 90 4A 00
627823 - MIDI IN [BCF2000_To]: 90 4B 00
when selecting a new channel
90 4A 00 = read off
90 4B 00 = cycle
I cant even find 90 33 00 in the Mackie map?
Its just so difficult when such basic things dont seem to be working and they are so crucial to efficient muscle memory when working = huge improvement in creativity and lessening of fatigue…especially for quick turnaround jobs