Hi - Windows 10 with all updates on PC with no other issues.
Midas M32 console.
Cubase 12, initial release.
To use M32 faders as midi remote for 32 channels of fader/mute/pan
Console configured to send and receive midi program change, & fader positions.
Console midi via USB or Midi in/out ports (Tried both)
Create new Cubase project, and add audio channels (I used 4 in this test - have also tried 32)
Create new midi remote panel (for the M32)
Add a few faders (I used faders 1 to 4) by moving each fader
-Assign each fader to Mixer channel VOLUME parameter for that channel (ie; 1, 2, 3, 4 etc)
Complete the assignments and exit the midi remote window.
Faders are ‘stuck’. Moving any fader results in it fighting you, and snapping back to it’s original position when you let it go.
Disabling MIDI receive on the console, allows control of the cubase mixer channels, however the faders are in the wrong position when the project is opened, and as soon as you move one of the physical faders the Cubase channel fader snaps to the position of the Physical fader. Of course no faders are controlled by Cubase in this configuration so rewinds etc do not position the physical faders to where they should be when you stop.
Hope this helps - happy to add any further information if it’s needed.
What exactly does this mean, please? Does it send Program Change for the Touch Fader and then other MIDI Message (Controller or the Pitch Bend?) as the position? How did you learn the MIDI Message to the Manager?
The console has a tab in the setup screen that has check boxes - For ‘send’ midi, and ‘Receive’ midi.
I’m not with the console right now, but from memory they are something like
This gives me the capability to tell the copnsole to (for example) send fader positions over midi, but not receive them, and vis versa.
Of course - to be a control surface, the console needs to send AND receive this data as it’s the only way to know where to put the faders (from Cubase), and send fader positions when they are changed (to Cubase)
I’d assume an X32 would be identical, however you know what assumptions do! .
Thanks, and you may be right, however (as I discussed in that thread), I’m not sure the short term, or even the long term proposed solution will do the trick.
What is frustrating is that when the console is configured as a controls surface (where it can allocate the 8 master faders to emulate a Mackie HUi or whatever), the faders work perfectly with Cubase. It’s just the lure of having 32 available so I could use the desk for mixing is strong! I’m really looking forward to it.
Here’s the remote config window on the console.
In the ‘Midi Receive’ and ‘Midi Transmit’ sections, if I enable Fader POS CC in both, the faders lock up. If I disable Fader pos CC in ‘Midi receive’, the faders control Cubase ok, but Cubase doesn’t control the fader positions.