Oxygen 8 Midi Keyboard Driver Windows 10

[Sourabh Doherty]

ihave a copy of cubase sx3 that came with cubase 5 that i got from ebay,the seller kindly threw that in,he had upgraded from that to cubase 5.

i have midi output coming out fine,only thing is the midi light on the focusrite saffire usb 6 shows no light,not a flicker but i get sound wih no noticeable latencey.

i also just installed a helix phonic 12 mk2 firewire mixing desk,that has installed ok now it seems,just totally bamboozalled by all the ways of routingoptions and attaching external hardware to it by creating buses.

Going to be a long learning curve.

The room where i have my setup is now an absolute maze of various wires and cables,i only have a couple of plug points in that room so i have a couple of extension boards crammed with various plugs for drum machine,pc,monitor,mixing desk,kaos pad,midi keyboard bass amp and god knows what else,i forget at the moment.

Def needs a good tidying up.

The midisportx2 midi interface(usb connected to the pc)?

I disconnected a while back after not getting anywhere with the sync problem,have to reinstall the drivers for it,as everytime it becomes disconnected it asks me to re-install the drivers.

right,will disconnect the midi keyboard later as that is what is connected to midi in of soundcard,going to factory rest the drum machine as you said,i was using it for years with cubase vst so its been used to getting midi time code from that.

tried sending midi data to cubase from the drum machine last night,i think the manual tells you how to dump sysex(?) but when i tried to do that, the drum machine should do it in a minute or so usually but last night it just went on forever and nothing was received by cubase.

yeah i already tried that but no midi was recorded,later on i will restore drum machine to factory settings and plug it straight into midi in from drum machines midi out,i hope its not something to do with the midi ports on my soundcard,but,as i can see activity something in the transport bar indicating its receiving when i play the keyboard but something is blocking it from sending midi into cubase,i put in some midi notes manually last night(on the correct notes corresponding to sounds on the drum machine)and no sound and no activity from transport bar or the channel the midi notes were programmed into.

The drum machine is set to send/receive on midi channel 10 by default,double checked on its LED that it is on channel 10,that is the channel i have set in cubase to receive on midi channel 10.

Will let you know later either tonight are at weekend,have a few other things going on tonight and at the weekend so it might be a later update than earlier. Will update on how it goes when i get the time.In a rush at the mo so sorry about the short reply,

thanks once more for your time trying to help get this matter sorted out.

Also,i now have my mates Roland SH-32 synth sitting there doing nothing at the moment and wondered if you knew how i would connect it in a midi chain,the Korg ER-1 has a midi thru port as well as in and out.just not sure how to set up the chain and finally get the SH-=32 working.

Anyone using M-Audio Oxygen Pro Mini 32? ive read only works with Pro Tools and Studio >

Honestly its given me head ache. Not to fused about the keys, more so needed for work flow for pitch/Mod Wheel then to fine tune after with automation, simple pads and buttons. Something maybe with presets and doesn't break easy, Nektar Impact do list cakewalk

Also looking at

I'm having similar issues. I've gotten only so far. First I watched the Creative Sauce video titled Cakewalk Hardware Control. It at least generically explains what needs to be set up in Preferences, the controller hardware, and how to add a control surface definition in Cakewalk. Mike says the hardware needs to be set to Mackie MCU mode. He doesn't explain how to do that for the Oxygen Pro Mini specifically, but he advises that if the controller has Cubase mode, that may be a good starting point. Here's what I did:

2) Set the Pro Mini to Cubase mode: a) toggle the DAW/Preset button so it is lighted, b) press and hold it until DAW appears in the Pro Mini display, c) use the Encoder knob directly below the display to scroll to CUBASE, and then press down the Encoder knob to set the Pro Mini to CUBASE mode.

4) Go to Edit >> Preferences. Select MIDI >> Devices. Select the checkboxes in the Input Drivers and Output Drivers section for "Oxygen Pro Mini" and for "MIDIIN3 (Oxygen Pro Mini)" and "MIDIOUT3 (Oxygen Pro Mini)". Click Apply.

5) Go to MIDI >> Control Surfaces. Click the star button at the top right (next to the red X). In the popup window, click the Controller/Surface dropdown and select Mackie Control, and select MIDIIN3 (Oxygen Pro Mini) from the dropdowns for Input Port and Output Port. Click OK.

6) While still in MIDI>> Control Surfaces, again click the star button; this time, in the popup window, select ACT Control Surface and select Oxygen Pro Mini as the Input Port and Output Port for this. Click OK. Click Apply and exit the Preferences window.

With the above settings in Preferences, if I load a VST instrument like a piano, the Oxygen Pro Mini keyboard will play the notes, velocity of key strike works, Pitch Bend and Mod wheels work. I was also able to assign a couple of knobs on the Pro Mini to knob controls in the VST. To do that, I clicked the ACT learn mode button at the top right of the VST window, then right click the knob I wanted to control (a popup appears for that) and I click Learn in the popup, then twist the physical knob on the Pro Mini, and, seeing that the parameter is changing in the VST window, click the ACT learn mode button in the VST again.

I had to use my mouse to arm the VST track, but then I was able to start recording by pressing the Pro Mini's record button, stop recording with the Pro Mini, and all the transport controls on the Pro Mini worked as expected.

Nice, BUT - I can't disarm that track for recording using the mouse or otherwise. If I delete the track, I can add a new VST instrument track, arm it using the mouse, and do the same thing, but the new track also cannot be disarmed. I see to the left of the track controls there is a thin green bar which says that Mackie Control is active when I hover on it, but nowhere does it say that ACT is also active. I think my remaining issues may be related to Mackie Control and ACT Control being defined/selected in Preferences.

Jeremy - note that the OP and I are talking about the Oxygen Pro Mini. It's also class compliant, but it's not the same as the Oxygen 61. The M-Audio instructions for setting up the Pro Mini (in any DAW) are not the same as the Oxygen 61. On the Pro Mini, there's NO option to specify PC or Mac in the Global settings like there is on the Oxygen 61, for example.

I did my homework, on both the M-Audio and CbB support pages/forums. There is nothing currently published on either web presence that results in a good, working integration of the M-Audio Pro Mini with Cakewalk. That doesn't mean it isn't possible. I'm pretty close, using the steps I captured above.

The reason I posted the method I used and the functions that are/aren't working is I'm hoping there are actual Oxygen Pro Mini users on the CbB forums who can help us quickly get to a good, repeatable working Cakewalk DAW setup, step-by-step, for Oxygen Pro Mini.

Ok, I have the Oxygen Pro Mini controls working acceptably in Cakewalk now, as a result of further testing and changes to my initial setup outlined above. Main change: I did not define an ACT controller, only the "Mackie Control" included with Cakewalk. I still notice a few anomalies, and I've only done this on an AMD Ryzen 7 4000 series laptop running Win 10, connected via USB. But I did achieve a repeatable setup process, throwing out all prior controller and midi device settings in the current version of Cakewalk by Bandlabs, and resetting the Pro Mini between setup iterations.

If this all works, if you have the Instrument's popup window open, and if you click the DAW/Preset button on the Pro Mini so that it is now not lighted, press and hold that button to bring up the Preset display on the Pro Mini. Turn the Encoder knob, below the display, till you reach Preset 9. Click the Encoder knob down to select this user preset. Once you have this, you should be able to assign some controls in the VST Instrument's control window to physical controls on the Oxygen Pro Mini. When you have these as you like them, remember to save the Preset with the name "Preset 9" in Cakewalk.

i needed more functions, even though my full keys are touch sensitive and i have sustain peddle i had no mod or pitch wheel or knobs which come in handy for automation with synth work and sound design. So i ended up getting a the New MIII Novation launchkey 25 USB with pads, pitch wheel and knobs etc

Like anything USB it acts as a storage device so to speak and with Novation, you need to update to the Novation USB drivers which gives you two midi inputs LKMK3 MIDI and MIDIIN2 (LKMK3 MIDI) and two midi outputs the same but different names. Do not ask me why not just one midi in and out i can not get anyone to tell me, i guess maybe a new protocol given its called MIII. However i add both inputs and outputs to see which one works the best but what i have noticed is MIDIIN2 (LKMK3 MIDI) works better with ACT MIDI Controller.

I added MIDIIN2 (LKMK3 MIDI) as a ACT midi Controller input output and did not setup a Mackie, there is no point its not a Mackie controller and ACT as more functions. You can see i have full control Synthmaster with the 8 Rotary knobs on Novation launchkey 25, i have full pitch, mod and play record etc which is all i need and created my own template preset, i got there in the end but it was worth it. I got 400 of plugins free with it and only paid 90 for the MIII Novation launchkey 25 so i am happy

3a8082e126