Thank you for replying. I did follow all of the information on the M-Audio site, but that is now outdated. Note their screen shot of the Cubase Midi Screen:
Note that the “remote devices” is “Legacy” and while it seems I can add “Mackie Control” my thought is that this will stop working soon. All signs point to Cubase going to their “midi-remote” scripts. Or am I just misunderstanding?
I followed the documentation on the m-audio site but the midi remote does not recognise the trigger pads even though I can see the midi signal going into Cubase 13 when I hit them.
Hi, I just recieved an Oxygen Pro 49 today. Bought it, because M-audio promises automatic recognition of the daw (you have to set it in the Oxygen, I know). In fact they promise plug and play. But when i e.g. push the fast forward button a note sounds. No knob or fader works. At least not as it should. Of course I read al the manuals. Also of the editor app, Etc. etc. The info on the m-audio website sucks too. Yes, they direct you to the Midi Remote functions in Cubase and advice you to make your own setup…! Yes, can do. With any other, cheaper midi controller then, that does not promise heaven and delivers hell.
I am very unhappy with the Pro 49 and am in the mindset of getting rid of it and switching to a more compatible controller. Working with the 49 is frustrating as many of the functions do not work as labeled…or work at all.. too many to list. Basically it is non intuitive. A waste of money and my time as far as I am concerned.
Fast forward 2 years: after using the Oxygen Pro 61 daily in Cubase, I’ve got a much deeper grasp on it now!
In hindsight, even for mixing, I’ve found that using the MIDI Remote system is actually much better than relying on the default Mackie Control protocol.
For anyone setting this up, there are basically two main script approaches:
The Basic / Simple Approach:
You map a single bank from the hardware in MIDI Remote. It keeps the surface clean, simple, and very easy to manage.
The Extended 4-Bank Approach:
You utilize all 4 hardware banks of the Oxygen Pro. While this gives you a massive control surface in Cubase (36 faders, 64 pads, 32 buttons, 32 knobs…), in my opinion, it’s quite tedious to configure and leaves you with a huge, cluttered GUI on screen—definitely not the prettiest thing to look at!
A quick word of advice on configuration:
Before even touching Cubase, you must spend time in the M-Audio Preset Editor. Be prepared to set aside half a day and a few cups of coffee! You have to edit controls one by one, set up MIDI CCs, define how buttons/encoders react, assign colors, etc.
My best tip: take a pencil and a piece of paper first. Think carefully about your personal workflow and what you actually want out of your keyboard. It’s definitely not a plug-and-play experience, but rather an ongoing construction project that you refine over time.
Personally, keeping it simple with MIDI Remote gave me the smoothest workflow in the long run. Hope this updated feedback helps anyone still trying to tame their Oxygen Pro!
I have owned the oxygen pro 61 for many years and know the hardware well.
I might write a custom MIDI Remote script using the MIDI Remote API to hook into the sysex states of the Oxygen Pro 49/61, which would basically allow the LEDs (buttons, pads) to work with cubase properly, among some other things. But I will need to give it some thought on how to make the script easy to use so that the Preset Editor will not be needed.
Automatic Detection[1] you don’t even need to change DAW Preset
Mixer Bank control of 8 channels via faders, mixer buttons, and knobs
LED feedback for the mixer buttons in each control mode
Customizable[2] - if you can see it in the surface, you can remap it
For Oxygen Pro 61 and will probably work for 49 users if the firmware matches
Work in progress / Planned:
Pad colors dynamically controlled by the script. Not decided how to best use it
“DAW Pad” mode switch when you hold [SHIFT] and tap on pads 9, 10, or 11
[SHIFT] button to swap states of certain controls on the hardware
Focus QC for simple VST control using the knobs
Advanced VST control? By instantly changing PRESET on the Oxygen Pro
Technical Info & Limitations
I have the Oxygen Pro load up the Ableton DAW Preset as part of automatic integration. Using the Cubase DAW Preset is possible, but would be significantly more limited (and cause some issues with mapping as the knobs of the Cubase DAW preset is designed for MCU standard), so after a lot of testing I settled on the Ableton DAW Preset as every Oxygen Pro 61/49 should include this so long as the firmware was updated by around 2022/2023.
Another reason I chose the Ableton DAW Preset is because it is the only way to avoid the hardware banks (Banks 1/2/3/4) on the Oxygen Pro. Not even the Preset Editor allows you to disable them, and I don’t want hardware banks present as they are not controllable by my script in any way and just cause synchronization problems with the hardware’s control and overall negatively affect user experience (IMO).
However, use of the Ableton DAW Preset comes with the caveat that “PRESET” Presets do not appear to send any message from Fader 9 (firmware bug?) - I am investigating some workarounds for this in case people want to use a PRESET Preset over Port 1 while simultaneously using my script.
Also, the ‘Mixer Buttons’ (row of buttons below the faders) are hardcoded to act as toggle buttons as a direct result of the stupid way M-Audio decided to treat them for the Ableton DAW Preset. Luckily, the Pads are also available so you can map any trigger actions/key commands to those instead.
@Nioufman I noticed you like to have page mappings on the Clip buttons (far right of the pads), do you use that to swap between DAW and VST control?
I personally like to use mine for virtual instrument control, especially electric organ with the faders mapped to drawbars, etc., but not so much the mixer channels.
I can’t quite decide if my script should handle DAW (mixer) controls with only Focus QC provided for VST control, or if I should also provide more advanced instrument control as part of the script.
only tested on Windows 11 in Cubase 15. I cannot test on a Mac. ↩︎
Some buttons are a little awkward to remap due to technical limitations. ↩︎