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. 

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

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.

Ok, going to necro a thread :P
 
I'm having the same issue.  All the latest drivers installed, fresh copy of X3.  The keyboard will be displayed under midi devices, and I'm able to play vst's with no issue.  I can use my faders and knobs - but the layout isn't the way I like, so I am able to midi learn and re-assign without issue, but this is of course not optimal.  I have the preset on the keyboard set to 10.
 
None of the transport controls work, and in the controllers section of preferences, I can add the Oxygen, as it's available in the list.  What I cannot do, is apply the changes after I select the oxygen in the list.  It removes the in/out, but leaves a blank controller, and in the main interface window, it shows no controller assigned.  I've tried selecting both an ACT and a generic surface.
 
I restarted the program, and this time received an unexpected error with the midi devices, and it disabled keyboard functionality, but DID show up as the active controller in the main interface bar at the top of the screen.  I can't tell you if it was actually working, because when I attempted to load the same VST's I was using earlier, I got a blue screen of death and called it a night.

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.

Definitely is.  If I could get to the point of being able to have it assign anything I'd be happy, but right now it's not connecting to a device, even though it's listed.  I'll troubleshoot tonight.  At least I can get notes in, but I'd like to be able to have better control over the sound with the keyboard directly.

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).

A midi keyboard gives you the ability to change multiple sliders/knobs at the same time though, you can't do what with a mouse/keyboard for live recording, can you?

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.

Here's a link to one of my videos that shows ACT set up from scratch. 
 
https://www.youtube.com/watch?v=ObsW0t5FnzM&list=PL37CEDDDD4DC74064
 
I don't have an Oxygen but my ZED-R16 has transport controls. I set those up using the generic surface. You can use both ACT and the generic surface with the same device at the same time. That's how my ZED is set up.
 
The important thing to know when setting up an ACT surface is the difference between "MIDI learn" and "ACT learn" which is all explained in the video.
 
Basically MIDI learn is used to assign a physical controller such as a fader or switch to a cell in the ACT dialogue box. Act learn then assigns a function to that cell. The end result is moving the assigned control adjusts the assigned function.
 
//