M-Audio Oxygen and Sonar X3

Hello
 
I have an USB-Masterkeyboard M-Audio Oxygen 61 and Cakewalk Sonar X3 (Standard).
The Keyboard has Fader, Trigger and specially Transport-Buttons.
 
But they don't Work in Sonar.
 
In VST-Instruments i can rightclick on an Fader and "Midi Learn", then touch an Fader on my Keyboard and the function are learned.
In Sonar i can't find any like that. In the Option in "Controller" i can't find the Oxygen.
 
I'm a little new with this technic and i hope, someone can explain what to do (maybe he has the same Keyboard).
(You can answer in german, if you wish)
 
Thanks
 
Andreas
 

Hey, I'd be thrilled as all get out just to get X3 to accept MIDI notes from my Oxygen 49, much less transport controls, knobs, and faders.
 
The fact that Sonar X3 can't just detect a USB device that has the drivers pre-installed and go from there (like, say, Live) is far beyond annoying.
 
 

Andreas, The setup works fine for me here.  Follow the youtube referenced in post #3 above.  Only change might be to use P.10 instead of P.05 on your Oxygen.
 
Glen

CJaysMusic

The fact that Sonar X3 can't just detect a USB device that has the drivers pre-installed and go from there (like, say, Live) is far beyond annoying.

It does. You are leaving something out as it works on everyone eases PC and Sonar.
 
Cj

Apparently I have been, but that's the point.  USB was designed as a true plug-and-play interface. Plug in the device, Windows sees the device, apps use the device, done.  
 
It has been exactly that simple to get my Oxygen 49 working in Live 7.03 and in Reason 4.  Sonar X3...not really.  I seem to have gotten it working (somewhat, at least), but only after digging through multiple sub-menus, poking around with multiple options and buttons, reading through two sets of documentation and running a slew of Google searches. FAR more convoluted than it needs to be.
 
Hopefully, the benefits that X3 provides will outweigh the initial aggravation of its lack of simplicity.  

Maybe i make some mistakes.. I have postet an Video where you can see, what i do, maybe you see whats wrong. Its recorded without sound, because i dont wanna comment in english ^^
 
But something other happens:
Today i wanna make an new sound. And i have the Sonar-Instrument RGC Audio in use. I dont assign faders with that VST, but they all work on different positions.. Not really helpfull positions, but they work. So, that i don't do that, sonar must be do so.. So the keyboard is assigned.. But not to the Channel-Fader ^^
I think it will take some time, till i understand that thing with that fader :(
 
Another question, you maybe help:
I have make an track with the RGCaudio like i say. So i have an track with an bass.
No I want to mak an lead-sound with the same sound in rgcaudio. But i want it in another track, so i can move the Midi-Datas where i need them (copy/paste), because i dont need them all the time :)
So i want to make another track, who has the rgcaudio VST, but not the track.
When i choose "clone track" and make an record, they will recorded in the first (bass) channel too, and i can't move it.
 
What... Oh no.. Now I want to try out something (cloning without cloning notes), and now all my tracks are gone.. They still playing, but I cant find them O.o
The window is still open, but empty.. If i "drag" above there comes an "Video-Track".. When i drag down, comes another empty window.. .Uhaaaaa... Help me... !!
 
And maybe the controller Story in this video:
EDIT: Damn, cannot post an link.. Argh.. Very Helpfull.. Maybe you can find it when you search at youtube to the text:
Try to choose my oxygen 61 in Sonar X3 as an controller. 

chuckebaby
another person here, that has no probs with the oxygen and sonar x3.
you need the drivers from m audio though.
that's how mine works.
 
works flawlessly , ACT is your friend, that you tube video posted earlier is perfectly correct even though its sonar 8

Charlie . . . this is good to hear, since I was thinking of purchasing the M-Audio Oxygen 88 . . . knowing that it can work in Sonar is reassuring news, because the M-Audio site only mentions support for those other DAWs.

I have an M-Audio Keystation 61es, and have never had issues with this, but it is also significantly larger than my needs are (I am a "reformed guitarist" now, so only think in two octaves ). abb's point about ACT controller is sound... I purchased a Roland A-300 PRO a few months ago which has an "ACT" button on it. This works like a dream for me (first time EVER I can control SONAR with an external device).
 
I use the MIDI controller to get notes into SONAR, so the 66 was a bit "overkill" for me, but I have not had any issues using it. I have not used an Oxygen, but the "ACT controller" is the way to go. The Keystation is nothing but a set of keys... so controlling any DAW is a bit moot with it.

For me, the first true "ACT controller" was the A-300 PRO. And even though I have that ability now, I still "think" to control SONAR with the mouse/keyboard. Perhaps I have been successfully "trained" this way, but I do not assume that controlling SONAR via a keyboard will be effective (except for simple transport operations).

Correct. It adds a lot of dynamics to what you can do for certain. The Keystation is more "just a set of keys" but I used an M-Audio Ozone for years that I never could get the knobs to work "quite right" on, which frustrated me each and every time I tried to set it up. Then they began randomly drifting as the keyboard aged which made it moot. Setting up ACT is a definite nicety (now that I can truly use it), and SONAR has several keyboard templates already mapped when setting one up.
 
FastBikerBoy has a few videos which walk through an ACT setup from scratch as well.

I do appreciate all of the help, but the issue is that the keyboard isn't being picked up as a controller, so I can't get to the step that allows me to configure the ACT settings/assignments.  Same thing is true if I try to use a generic surface, it allows one to be added, but upon clicking apply when selecting the device for in/out, it blanks out the fields.
 
Here's a video that shows the problem, I think it might be the OP who posted this.

 
There seems to be an issue with Sonar X3 running in 64 bit.  The odd thing, is if I try to run it in 32 bit, it shows it as a controller, but rejects it if I try to run the prefs->devices saying there's an unexpected error (followed by a 50/50 chance of a BSOD in a minute, "bad header pool".
 
 

I don't have it, but I've had no issues at least getting any VST's to work, both 32 and 64 bit.  Rapture works fine.  I should mention that when I say fine, I mean will make noise.  None of the controls are functional unless I midi-learn for things like rapture - beyond pitch bend, modulation, volume, pan.  In CSC, the knobs do work, but I still have no communication as far as transport tools go, or being able to assign sliders into the background functions in the main interface.  It appears that something is just blocking it from accepting it as a valid control device, because the midi data is being accessed by VST's.  If there was a way to force the config (by manually editing an .ini file) I'm pretty sure it'd be fine if it didn't perform the check when started up - if there's a command line parameter to skip that.
 
Lots of reasons for BSODs, but usually it's something low level.  A bad pool header usually has to do with memory allocation, but can certainly be caused by bad driver communication.  I've removed and reinstalled both the basic Microsoft drivers and the M-Audio drivers, no change.

yup, yup, nope
communication's stable, that's not the issue.  resolved the issue in 32 bit mode now, but i still can't get the 64 bit to accept it as a controller, so I can't even get to the point of assigning controls.