Jump to content
Mark Morgon-Shaw

Trying To Set Up New M-Audio Oxygen PRO controller

Recommended Posts

On 3/6/2021 at 4:20 AM, Poetica said:

Slightly off topic but has anyone used this with Reason on a Mac?

More than "slightly off topic," it's off forum. 😄

This forum is dedicated to Cakewalk, a DAW that runs exclusively on Windows. I suggest you will get better answers if you ask on a forum dedicated to Reason, and/or the hardware in question, both of which are more likely to have people using it on Mac/OSX.

Good luck, I hope you get it sorted.

  • Great Idea 1

Share this post


Link to post
Share on other sites

Extremely annoying.

 

I was about to update my old midi keyboards for the M Audio Oxygen Pro 61. Why is there no straightforward support for Sonar or Cakewalk CBB ?   

One of the reasons I was looking for ward to the change to a modern midi controller was not having to scratch my head for hours trying to set the thing up to work in Cakewalk. 

I was one of the masses that subscribed to Cakewalk from the early days right through to Sonar Platinum.  Would it really be such a big deal for M Audio to add support for Cakewalk CBB ?. 

Share this post


Link to post
Share on other sites

For anyone puzzling over whether an Oxygen Pro will work with Cakewalk, or wondering how to set it up as a controller in Cakewalk, I want to share a few resources and tidbits that helped me out with mine (49-key). In short, it's a great keyboard/controller with extensive customization possibilities. I have it controlling transport and track volume/panning with no problem, and I've set up custom mappings for a bunch of buttons to do exactly what I want. Almost all controls are set up using Cakewalk's ACT plugin.  I still don't fully understand what I've done, and am sure I've only scratched the surface.

If you want to learn the M-Audio preset editor software (highly recommended for tuning any button/slider/rotary to your liking), M-Audio hides the manual for this on their website. Looking up Oxygen Pro won't reveal the preset editor manual. However, if you go to the following page and search for "Keyboard Controllers" > "Hammer 88 Pro", you'll see the Preset Editor manual in the results.  As far as I can tell, it's the exact same editor offered to Oxygen Pro owners.

https://m-audio.com/support/documents-search

The below 13-min video was helpful to understand how the preset editor works at a high level. Also, the guy tells you how to find the software in the first place, which is not obvious (gotta enable advanced options in the M-Audio Software Manger, wtf):

M-Audio Preset Editor overview (Youtube)

On the Cakewalk side, this video has aged extremely well in terms of succinctly demonstrating how ACT controller setup works:

ACT controller setup in Cakewalk/Sonar (Youtube)

This part may be obvious to some/most, but Cakewalk does not process MIDI data unless you have a project open. I beat my head against a wall for a short time trying to MIDI-learn controls in the ACT plugin without a project open. Further, if you wanna map your 8 sliders and rotaries using ACT, you should have 8 or more tracks in your open project. Knowing that in advance would have saved me some time.

Finally, the below forum post was so incredibly informative about the quirks of setting up an ACT controller in Cakewalk. There are some great details in there that don't seem to be well documented anywhere else. If you're feeling fuzzy about ACT, read this post in full. It's fantastic.

http://forum.cakewalk.com/I-have-Axiom61-Should-I-get-a-new-to-use-ACT-m2168824.aspx#2174288

The Oxygen Pro has a couple modes - DAW and Preset. Each of these modes can serve as a completely separate controller in Cakewalk if you want to multiply your knobs and buttons (knowing of course that you'd have to switch between Oxygen modes to use them all). Out of caution, I used the M-Audio Preset Editor to make sure I wasn't repeating MIDI CC values between the two modes. I'm not sure if that's totally necessary, since the modes' commands are sent over different MIDI inputs. Just part of my ongoing learning!

Also good to know, according to the Oxygen Pro manual and experience, DAW mode commands (both Mackie/HUI and CC) are sent over the MIDIIN3 input. Preset mode commands are sent over the "Oxygen Pro 49" input (the first one). So that may help with your controller setup if you want to use both DAW and Preset mode to control Cakewalk. For my setup, I decided to reserve DAW mode controls to Cakewalk only (not follow to plugins) and switch over to preset mode when I want to control plugins (and not Cakewalk). That division of labor seems to work OK.

While I'm mostly using ACT to configure the Oxygen Pro, I'm also using Mackie Control for a few things, including the encoder knob that I couldn't quite figure out with MIDI/ACT. The bottom line is, with the M-Audio Preset Editor, you can define, per individual slider/rotary/button, whether you want its message to be sent as MIDI CC or Mackie/HUI. That's pretty awesome.

Anyway, after struggling a bit with my own Oxygen Pro setup in Cakewalk, I wanted to share this info. I hope it helps someone in a similar situation!

 

Share this post


Link to post
Share on other sites

I bought my M-Audio Oxygen Pro 49 a couple days ago and almost went insane trying to get it to work with Cakewalk. This thread in particular was very helpful in getting me on the right track; I've spent a lot of time trying different options and making notes on what worked and what didn't.

For anyone else confused about it, I posted detailed instructions below. 

One important note that might be helpful: the problem some guys here are having with the pan knobs (2% or 98%) is solved by setting the DAW mode on the keyboard to MPC or Ableton or Reason.  Setting the DAW type to anything else (PT or Studio1 or Reaper or FL  etc.) will cause this issue.

Also, as others here have mentioned, when setting the ACT on CbB you must have a project open; make sure the project has a decent number of tracks because you can only assign a control to a track if there's an active track open. I started with a small project with only 7 tracks and couldn't assign a fader to track 8 until I opened a larger project.

And, as mentioned above, the Oxygen Pro uses MIDI inputs 1 and 3 (Oxygen Pro 49 and MIDIIN3) for presets and DAW, respectively. If you leave MIDIIN2 and MIDIIN4 checked as MIDI devices, problems can develop so only enable 1 and 3.

Here's what I did to get it working:

1. Plug the USB connector into the Oxy Pro and your computer (don’t start Cakewalk yet) and turn the power switch on.

2. Set the OS

  - press Shift and Global and the display will show “GLOBE” with “G CHAN” underneath.

  - Rotate the Encoder knob until you see “PC” displayed; press the Encoder to select.

  - Rotate the Encoder again until you see “Win”, press the Encoder again.

  - Press the Back button

3. Set DAW mode

  - Press and hold the DAW button until the display shows “DAW”

  - rotate the Encoder until you see MPC (or Ableton, or Reason)

  - press the Encoder to select

4. Set up Cakewalk

  - Start up CbB

  - Open a project (pick any project, ideally one with 8 or more tracks)

  - Click Edit – Preferences

  - Click MIDI – Devices

  - Inputs: Check Oxygen Pro xx and MIDIIN3; Do not check MIDIIN2 or MIDIIN4

  - Outputs: Check Oxygen Pro xx and MIDIIN3; again, don’t check MIDIIN2 or MIDIIN4

  - Click Apply

  - Click Control Surfaces; You should have at least one controller named ACT MIDI Controller; set the In Port to MIDIIN3

  - Click “Add New Controller” (yellowish icon) and select “Mackie Control” as the Controller/Surface; set the input port also to MIDIIN3

  - Click Apply and Close; At this point you should be able to get MIDI notes out of the Oxy Pro. The next step is to map the transport buttons using the ACT feature in Cakewalk.

5. Map buttons

  - From the menu click Utilities – ACT MIDI Controller -1

  - The ACT map will pop up

  - From the Presets field, select M-Audio Oxygen Pro 49 (Preset 10)

  - Each control may be assigned using MIDI learn. For examply, to set up the Stop button, click on the empty box below where it says C32 Stop; you should see “MIDI learn...”

  - On the Oxy Pro keyboard, press the Stop button and the MIDI learn message will disappear.

  - Repeat for each button you want to assign.

  - Close the ACT window

 

Share this post


Link to post
Share on other sites
Posted (edited)

Mike Z and 6foot5..... THANK YOU SO MUCH!  I'm totally new to midi-commands, and this is exactly the kind of step-by-step handholding that I needed.  I was debating between controllers and hoping to find one that would work with CBB, and having your posts on this thread gave me confidence to go with the Oxy Pro 49.   Followed the steps above and things certainly seem to be responding.  Thanks again!

Edited by The_Working_Man

Share this post


Link to post
Share on other sites
On 4/24/2021 at 8:19 PM, The_Working_Man said:

Mike Z and 6foot5..... THANK YOU SO MUCH!  I'm totally new to midi-commands, and this is exactly the kind of step-by-step handholding that I needed.  I was debating between controllers and hoping to find one that would work with CBB, and having your posts on this thread gave me confidence to go with the Oxy Pro 49.   Followed the steps above and things certainly seem to be responding.  Thanks again!

Glad you got yours working. It's a great keyboard and I was frustrated that I couldn't find step-by-step instructions like this. I tried it with Cubase and it worked immediately but CbB was a little more complicated.

Share this post


Link to post
Share on other sites

if this can help i had the same issues with my 49 pro and using the preset for bitwig seems to work, although when i arm te first track i cannot disarm it. any ideas how to fix it?

 

Share this post


Link to post
Share on other sites
11 hours ago, Marco Tavoliere said:

if this can help i had the same issues with my 49 pro and using the preset for bitwig seems to work, although when i arm te first track i cannot disarm it. any ideas how to fix it?

 

If you mean setting the DAW type on the keyboard to Bitwig, I believe the only fix is to change it to MPC or Reason or Ableton. Any other DAW types I tried had various odd issues (especially when panning).

Share this post


Link to post
Share on other sites

The controller compatibility with Cakewalk is an ages old question mark. I don't understand why it is so complicated after so many years?

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...