MainStage + M-Audio Oxygen 61

Hi there!
I have a pretty stable live setup with Logic Pro contolled by Oxygen 61 via DirectLink. I use eight pre-mapped Oxygen buttons to select Logic channel strips (patches) and sliders to change volume on them. To select and control the next 8 patches I change the bank in Oxygen.
For some reasons I decided to migrate to MainStage. I made a concert with two sets of eight patches. I would like to select the patches withing each set using eight buttons of my Oxygen. But these buttons only transmit Program Change to all the patches in concert in the row. For example if I select with the mouse click the second set before perfomance and then want to select the first patch in the second set and press the first button, it jupms over to the first set and selects the first patch in the first set. I messed around with the buttons trying to assign them properly, but I failed.
Help me please, because I have only a month left to my gig! )
Thanks, Max

OK, I haven't tried this, but here's an idea that should in theory work:
Program your Oxygen so that the eight buttons you want to use don't send patch change messages directly, but regular MIDI CCs.
Assign these buttons to eight corresponding screen controls in MainStage (Layout mode)
Specify a unique program change number for each patch in your concert (in the Patch Inspector).
This is the important bit: Create the mappings for your buttons at the set level: Select one of your sets and map each button to the exact patch number within that set, that you want to select with the respective button. (map to "Actions" -> "Jump to Patch"). Since these set-level mappings will only take effect as long as you are playing a patch within that set, you can set up independent mappings to completely separate patch numbers within each set.

Similar Messages

  • Mainstage with M-Audio Oxygen 49

    I've been having a lot of drop-outs using Mainstage with my oxygen 49. I'm running OSX 10.5.5 on a 2007 Macbook with a 2.16 GHz Intel processor and 4 GB of RAM. The only thing I can think of is that my computer somehow can't handle it, but it seems to me that it should be more than powerful enough to run Mainstage successfully. The reason I think it might be my computer is because most of the drop outs happen when there's more going on. For instance, when a piano player I know plays my keyboard she gets drop outs like crazy but she's using the sustain pedal and hitting a lot of notes. I'm a guitar player NOT a piano player so when I play the keyboard I'm usually using a synth pad and just holding down chords or playing a one note at a time riff with a synth lead patch. Any thoughts?

    Hmm that does sound strange.
    I have a fairly similar setup, and use both an Axiom 25 (connected to the laptop via USB) and a Roland A-33 (connected to the Axiom 25 via MIDI IN) at the same time, and haven't noticed any dropouts. (and for context, I am a piano player, so we're not talking index finger hen pecking here)
    I use a MBP (2.16Ghz) with 2GB RAM, and my CPU utilization with 2 FM8 patches running concurrently is around 40%.
    In order for a 'apples to apples' comparison, which patch(es) are you using?

  • MainStage 2 and Oxygen 49 "snapshot" problem

    Hello,
    I have an M-Audio Oxygen 49 controller, and prior to upgrading to MainStage 2, I would frequently use the "snapshot" function on my controller to send all current hardware slider states to the screen controls. Now, every time I use snapshot, it switches to the very first patch in my list, regardless of what patch I am on. So, if I switch from say, patch 3 to patch 4 (using different buttons on my controller) then hit the snapshot buttons, it switches back to patch #1. It's very annoying, any ideas on how to fox this????
    Thanks!!

    Because the Oxygen 49 probably sends a program change message to MainStage. Because you probably can't disable that on the Oxygen 49, you can only disable listening to program change in MainStage: select the concert level and in the inspector you can disable program change listening.

  • Hi. I have the Apple connector kit...and actually played my M-Audio Oxygen 25-keyboard thru  my iPad2--without a powered hub.  But that was two month ago.   Now...I can't get it to play.   I can hear the notes...but faintly.  And I have pushed ALL the pos

    Hi. I have the Apple connector kit...and actually played Garageband via my M-Audio Oxygen 25-keyboard thru  my iPad2--without a powered hub. 
    But that was two month ago.
      Now...I can't get it to play--with volume.   I can hear the notes...but faintly.  And I have pushed ALL possible volume controls up (Keyboard & iPad). 
      I know the keyboard is triggering, because I tested it on a MacBook: got full volume, just like before.
      But just can't get full volume from the iPad2.  I got a 4-port USB hub...and tried interfacing it between the keyboard and the connector kit/iPad2.  But still no volume.  It's almost like a switch is off in the iPad???
      Any help would be appreciated.  Dan

    hello again,
    i didn't really dare to delete the blue home folders before, just in case everything went wrong, but now i think i have so little space that i can't afford to lose 2.25gb!
    one thing that slightly worries me is the fact that the 'proper' library folder (in the home icon) is 2.09gb, whereas the 'wrong' one (from the blue folder forenamesurname) is 2.24gb - this is the one i would be deleting. just seems odd to delete a larger file than the one i presume i'm using.
    "Move everything you want to keep out of the blue folders, and then place both of the folders on your desktop. If everything works properly after a few days, delete both folders. If you are asked for your administrator password at any point or if either folder is copied instead of moved when dragged, don't delete that folder."
    by 'everything you want to keep', does this include the library folder? 'cause there doesn't seem to be much else, and i'm not sure if deleting the library folder would ruin all my preferences.
    i've put both of the folders on the desktop, it didn't ask for the admin password or try to copy them, so i guess that's good news. what kind of things should i be looking out for to act differently?
    are the folders not in use now that they are on the desktop?
    also if i put them in the trash will they have no effect? i.e. the same as permanently deleting them, so i could put them in the trash as a test.
    cheers, stephen.

  • Disk too slow error when using M-Audio Oxygen 49 keyboard

    I bought the M-Audio Oxygen 49 keyboard. And when I plug it into my MacBook Pro to do some playing, the project will record for maybe a minute but then I get a 'disk too slow' error and the recording stops. This happens every single time, no matter if there's 30 tracks or 1 track on the recording. I know that it is the keyboard causing the error because I am currently working on a 59 track piece that has effects on almost every track and my setup doesn't even blink. (well it'll pinwheel for a second when I hit record sometimes, but the CPU and disk meters don't ever get near red-line levels).
    What on earth is causing this stupid keyboard to cause this problem, and how do I fix it? It's clearly the keyboard. When I unplug it and record a live track on a project that just gave me the 'disk too slow' error, everything works just fine!
    Grr...
    Any help is appreciated, thanks!
    Edit: I have the MBP plugged via firewire into an Echo Audiofire and then into a WD hard dtive (at 7200 RPM). The keyboard is USB into the MBP.
    Message was edited by: Zombie Flanders
    Message was edited by: Zombie Flanders

    hi
    i spoke with Apple pro application support staff who confirmed that the Tascam 1884 patch for 10.4.10 is the cause of the problem. The apple boot drive can reliably record 1 channel of audio under normal circumstances. Apple staff described the situation as "unfortunate" and recommended to wait for Tascam to release 10.4.10 compatible drivers.
    For anyone interested in the technical background, the Tascam 10.4.10 patch DOWNGRADES the audioFW component (messing with kernel headers etc.). This compromises the OS's ability to correctly communicate with FW devices.
    I had tried recording to a firewire 800 drive, but all FW IO is affected by the 10.4.10 Tascam patch: Logic simply didn't record anything to disk when I tried this, and the machine became unresponseive. I do not recommend anyone attempt recording to a FW drive with the Tascam drivers installed.
    I have recorded circa 400 hours of single channel 96K 24bit audio to my internal Macbook Pro boot drive using the same software/configuration under 10.4.9 without a single glitch. I do recognise that when requiring heavy disk IO it is not advisable to record to the boot drive. However, 1 channel of audio can be reliably recorded if the system is well maintained.
    Thanks to all for your comments and suggestions.

  • Transport buttons on my M-Audio Oxygen 8 v2 midi keyboard controller

    I can't get the transport buttons (record/play/stop) assigned on the transport buttons on my M-Audio Oxygen 8 v2 midi keyboard controller. I've tried assigning it in Key Commands but it's not recognizing when I hit the transport buttons on the device.

    not possible to download.
    this message you get:
    "Oxygen 8v2, 49, 61
    Version: Class Compliant
    Release Date: January 30, 2006
    Applies to:
    Oxygen 61, Oxygen 49, Oxygen 8 v2
    Operating System(s):
    Mac OS 10.3.9, Mac OS 10.4.2, Mac OS 10.4.3, Mac OS 10.4.5, Mac OS 10.4.4, Mac OS 10.4.6, Mac OS 10.4.7, Mac OS 10.4.8
    Release Notes:
    This device is class compliant and does not require driver support for OS X.
    Note Added March 21, 2006: Axiom Series has been qualified for use with Intel-Based Macintosh computers.
    M audio Netherlands just says it has to work with the drivers from the osx. I also tried to reinstall the driver from the cd that was delivered with the oxygen.
    No change.
    I sure have been thinking of taking others.
    greetz

  • M-Audio Oxygen 8 Help needed

    Hello,
    I'm trying to install and use my M-Audio Oxygen 8 for Logic Pro (and other uses). I've installed the drivers and I'm not getting any response in Logic. I've plugged it directly by USB. Do I have to plug it into my interface(Tascam US-122) by MIDI? Things don't seem as automatic as I thought, what else do I have to do?
    Thank you in advance for your help.

    Since it works in GarageBand, this probably won't help, but check AudioMidi Setup, and make sure your Oxygen 8 shows up there, hit "rescan Midi" even if it does, then launch Logic. Make sure when using Logic you don't have any other audio app grabbing at the Oxygen 8 (e.g. GarageBand). I have an Oxygen 8 on my intel Mac and with the latest MacTel driver, it originally showed up as connected to my MT4 midi interface (and it is not--it is connected directly via USB). After making that change in Audio Midi setup, it worked fine in Logic.

  • M-Audio Oxygen v2

    Hi- I just got the new M-Audio Oxygen v2 and I'm wondering if any other users here have one and have any setup tips for use w/ GB.
    I'm most interested in using the built in transport keys with GB. I assume they would work... since M-Audio makes the iControl and since the transport keys look like they are laid out for GB (including a loop button with the same icon as GB's loop button).
    But if there are any other setups anyone can share that would be great!

    As far as I know, only the iControl works as a control for GB.

  • Quickly assign M-AUDIO oxygen nobs 1-8 filter cut off automation

    hi, how do i link M-AUDIO oxygen nobs to plugin. For example I would like to use (1) and manual move the "cutoff" effect in the es1?
    is this done through touch mode?

    well I'm happy to grab your hand for this one - as i love Logic's ability to do this so quickly!
    OK.... first click on / adjust your evoc20 formant shift to activate it as the "last tweeked knob".
    Now, go to Logic Pro>Preferences>Control surfaces and select the first item in the menu which should read "Learn Assignment for "Formant Shift"".
    A small floating window pops up: 'controller assignments'.
    move the oxygen 8 knob you want to assign the formant shift knob to...and move the formant shift knob around too.
    Click on the "learn mode" button to deactivate it.
    Now, simply twiddle the oxygen 8 knob and hey presto you will see the evoc20's formant shift move in tandem. cool.
    You can now assign other controls as desired.
    This is one of my favourite features of Logic 7.
    Hope that helps
    Rounik

  • M-Audio oxygen transport mapping

    Iv got an M-audio oxygen 61 and an Oxygen8 v2, both have transport controls on board, any got any idea how i can assign these transport controls to the logic transport?
    i do have the m audio enigma editor thing but never rly known how to use it!

    Hi
    in Logic, open up your key commands window (option K) and under global locate your transport controls. select one of them and on the lower right hand side of the window you will see a button that says "learn new assignment". Press that and then press corresponding transport button you want to use on the controller. That's all there is to it.
    it doesn't matter which CC# you assign to the buttons on the Ox 8, you can just leave them at there defaults.
    Don

  • Automation issues with M-audio oxygen 61, and NI massive

    Hi,
    For some reason, when I want to assign a CC on my keyboard to control automation, Massive recognize the command, the knob in massive which i pressed " midi learn" moves, but only once and stays to that position. If i move the command on my keyboard again, nothing happens. I have tried to reset midi command, restart Logic and my mac, but same thing happens.
    any help?

    OK, I haven't tried this, but here's an idea that should in theory work:
    Program your Oxygen so that the eight buttons you want to use don't send patch change messages directly, but regular MIDI CCs.
    Assign these buttons to eight corresponding screen controls in MainStage (Layout mode)
    Specify a unique program change number for each patch in your concert (in the Patch Inspector).
    This is the important bit: Create the mappings for your buttons at the set level: Select one of your sets and map each button to the exact patch number within that set, that you want to select with the respective button. (map to "Actions" -> "Jump to Patch"). Since these set-level mappings will only take effect as long as you are playing a patch within that set, you can set up independent mappings to completely separate patch numbers within each set.

  • About M-Audio Oxygen-8

    I cant get to work my midi keyboard on my macbook black C2D , i was just wondering if any of you knew if this keybork is no longer compatible with new intel mac or newest operating system?, since is very old and the new one is OxygenV.2, i cant find the right drivers for it because the one that is on the drivers cd says is just compatible with OS 9, and there are not any new drivers for OSX, or i cant find them...so any help?
    Thanks.

    I should try the driver for v2:
    http://www.m-audio.com/index.php?do=support.drivers
    and select 'Keyboard Series', then the keyboard and the OS.

  • Mainstage 3 Audio Output

    Is it possible to assign channel strips to different outputs?  This would be helpful routing backing tracks, click tracks, ect to separate channels on the board.
    Thanks
    Scott

    Hi
    Sure.
    Assuming that you have a multi-out audio interface connected and set up in MS Preferences audio as the output device, simply click-hold on the Output slot of the channel strip in the Strips area of Edit mode.
    CCT

  • Connecting M-Audio Oxygen 8 keyboard to GarageBand...

    Hi.. I'm having difficulty connecting my new keyboard to my computer. The computer senses it there, and I just installed the latest driver, but when I play on the actual keyboard while in GarageBand, it shows I'm hitting keys but there's no sound. (there is only sound if I use my mouse to press the keys in the keyboard window). If ANYONE can help me figure this out that would be WONDERFUL. Thanks!
    1.5 GHz PowerPC G4 (Mac Mini)   Mac OS X (10.4.4)  

    Yeah, when I'm testing it I'm either in "new track..." browsing through the instruments or just in... "idle". (I dunno what to call it, but basically when it shows my song and I can press play if I like) Would some setting like volume on the keyboard be the problem?

  • M-Audio M-Track problem with Mainstage 3.0.2

    I recently purchased an M-Audio M-Track and wanted to use this to input guitar tracks into Mainstage 3.  However, when I try, it does not recognize any inputs.  The M-Track is working fine, because I can use it without any issue with Mainstage 2 and it also works fine with Ignite.  I have seen other entries in the forum for with the same issue for the Fast Track.  For the Fast Track, it appears that the problem was fixed with new drivers.  However, there are no drivers for the M-Track.  Has anyone been successful in getting 3.0.2 to recognize inputs for the M-Track?

    Hello, crosbygs. 
    Thank you for visiting Apple Support Communities. 
    Here are a couple resources I would recommend going through for this issue. 
    MainStage 3: MIDI devices overview
    http://support.apple.com/kb/PH13519
    MainStage 3: Audio preferences
    http://support.apple.com/kb/PH13675
    Cheers,
    Jason H. 

Maybe you are looking for