I use a MIDI to USB interface with my old CME UF7 keyboard (originally only compatible with Win XP) and I use Cubase 13 Pro (Win10). So far it seems to be working, using basic functions. When I right-click the first slider in a VST like Padshop, and pick Learn CC from the menu, and use a slider on my keyboard, then it works. But when I right-click the second slider and do the same thing, then when I move the slider on my keyboard it moves the second and the first sliders together in my VST. And if I do it with 3rd, then it moves 3rd, 2nd and 1st slider in the VST. In other words, I can’t control them individually. I tried “Forget CC”.
I also use another MIDI keyboard sometimes, which is Axiom 25 (old generation). The Axion has drivers installed, and it works using normal USB (no MIDI to USB interface) but it’s not connected. The new one has no drivers, other than MIDI to USB default Windows 10 drivers, that were installed automatically upon connection.
The settings look like this (UF7 connected, Axiom disconnected):
EDIT: The physical connection goes like this. MIDI-In male connector (on the interface) goes to MIDI-Out female slot on the keyboard, like the manual said. MIDI-Out connector has nothing to connect to, as the keyboard has only one MIDI slot.
EDIT2: The interface is this: OTraki Midi USB cable interface converter 5-pin In Out midi to USB adapter controller for keyboard, piano instrument to Mac computer, PC, Windows, laptop music studio (2 m).
EDIT3: I tried MIDI Monitor plugin in Cubase and no matter which slider I interact with, it says “Controller 7” on the list. Does it mean that there is no way to set up each individual slider to a different value?
Yeah if the keyboard outputs the same data for all the slider it has, there is no chance of fixing that inside cubase. Your only hope is to see if there is anything in the settings of your keyboard that allows you to set different CCs for your sliders.
Ah oh ok your midi keyboard is sending the same cc on different channels depending on which slider is moved.
If you want to use your software you need to select a channel in the define mapping menu. So that when Input is on Channel 2 (and all the other parameters you put in) → Set output to a different CC (for example CC11), when Input is on Channel 3 → output CC2 etc.
And ideally always set the channel in Output section to 1.
You can also do this in a limited way inside cubase with the Input transformer. But you can only use 4 input transformations on one track so you can use maximum 5 sliders of your keyboard. Also you have to enable the input transformer on every new track you create, as far as I know there is no setting to auto activate the Input Transformer on every track.
So the next step for me is to figure out how to make those changes stick. If I leave MIDI-OX running in the background, Cubase ignores any “Learn CC” assignments. And if I close MIDI-OX, then again it treats every volume slider the same.
EDIT: To recap what I want to achieve. I want Cubase to perceive every volume slider of my old midi keyboard differently. So that I can assign different VST parameters (like Resonance, Cutoff, etc.) to individual volume sliders.
As long as MIDI-OX is running, Cubase is not responding to any MIDI key, knob or slider.
I am not sure. I am new to MIDI-OX, and I don’t know how I make Cubase see those changes. I saved the changes to a file but Cubase does not pick up on the changes.
Again, see my first sentence.
While I appreciate his response, I could not make sense of it. I already provided screenshots of my Data Mapping settings.
I tried changing: “Set output to:” > “Channel” from “Match Input” to “1” and I see that it changes the channel of a slider when I test it, but what good will that do if I can’t even make Cubase acknowledge the changes.
Ok go to studio → studio setup → Midi Port Setup and see if Midi-OX programm is listed in the midi port list. If it is, check wether it is activated in All Midi Inputs.
I see that the midi keyboard is responding but I can’t hear anything when I play, and still - nothing when I pick Learn CC on a parameter (right click menu) and use a physical knob or a slider on the keyboard.
Now I can assign slider 1 and 2 to different parameters and they move individually. Those are the only 2 sliders for now, that are assigned in MIDI-OX.
So much work for such a simple fix I appreciate the replies, however.
I have to admit that ChatGPT played a crucial role in solving this. It just needs very specific data and sometimes screenshots to accompany the info.
And also, it’s good to revive an ancient piece of technology using a …“simple” fix, instead of constantly wasting money on new… compatible equipment.
So in its “third” mode we can actually assign ccs to faders.
Other than that, we can always assign our faders to the VST Quick Controls 1-8, and then have from inside our VST the parameters we want, assigned to these 8 quick controls. This will work even when we have the same CC number but with a different channel as is the case here.
But the question is - what happens when you turn the midi keyboard off? Will it forget it and you have to set it up again? Doesn’t sound like a productive use of time to keep setting things up if it just keeps forgetting it. Software solution sounds better to me.
I also checked my Wattage meter and the keyboard uses 5W - just to be turned on. Not the money I want to waste, just to have it remember my midi CC setup.
EDIT: I am no expert, but maybe the reason why the faders behave like this is because of the USB to MIDI interface. Something is probably “lost in translation” when using the device without the original drivers and without the USB (to USB) connection. Too bad they sold a device that they decided not to support after WinXP. If I knew it back then, I wouldn’t have bought it at retail price. Well, at least we got some awesome software to remedy that.
I still have the physical manual, and yes, I tried what you suggested. It makes no difference at all. The 3 different states of “FADER FUNC.” (upper LED, lower LED, no LED) - I tried all of them. It’s the same behavior for all 3.
So without remapping software like MIDI-OX (and a bridging software like loopMIDI), every time you use Learn CC to bind a VST parameter to a fader, then it works. When you bind another then it also affects first one. The third one also affects second AND the first one, and so on.
I appreciate the replies, however.