![]() If you want to check that it is being seen by MainStage though, go to your MainStage preferences (cmd + ,) and the MIDI tab will show your midi status and how many inputs are detected. Regarding your Nanokontrol 2 actually working in MainStage, it really should be plug and play- hopefully just one of the other steps I mentioned is what kept you from seeing results. When you do that, the name of that parameter will show up in the list to choose from in your MainStage editor! All you have to do to edit the parameter you want in Omni is right click on it and select "Enable Host Automation" near the bottom of that menu list. That's because there are a ridiculous number of assignable pieces to Omnisphere. Other than your 8 patch levels (the volume of each patch in Omnisphere), you likely won't see other parameters to assign. ![]() Again I set up with just 3 midi channels, created a send from each each track to omnisphere, assigned the presets, then I imported a midi file from the. Ive just done another experiment this time with spectrasonics omnisphere. Sorry this is so wordy so far but this right here is the big catch that you may have been missing: Assign the sounds in Play to a midi channel e.g Godzilla Hits - Midi 1, Toms - Midi 2, Glitched Drums - Midi 3. In this list you can now choose parameters of Omnisphere to map to the element you selected in your workspace. The options right there are for your actual MainStage channel's volume, mute, and such but you want to edit your cutoff frequency and other stuff inside of your Omnisphere instance, so click on "Omnisphere" (likely at the bottom of the list there, it may have a green waveform sort of icon instead of those gray ones the other params in that list have). In there you can map your button, knob, or fader to a parameter in Omnisphere by using that third tab and selecting your MainStage channel that has your instance of Omnisphere on it. In edit mode, when you click on a parameter in your workspace, you can see 3 tabs in the bottom pane for "attributes", "mappings", and the last sometimes is unlabeled. That video doesn't go over mapping those params to Omnisphere but I've got enough to get you started there too: It seems the second fader in Microkontrol 2s default to the same MIDI CC as most modulation wheels on controllers are, so to make that 'keyboard' layer of MainStage only respond to your keyboard and not the microkontrol (and vice versa for your knobs and such), check out 7:00 of that video. Using the "assign" button when you click on one of the knobs or faders, you can then start to move the one on your kontrol that you want to assign to it and it should take! This is at around 5:15 in the video I linked. I think the best way to do it is like they are, where you edit the layout of your MainStage concert space to have the knobs and faders you want to map into Omnisphere there, then in the edit mode you choose what all of those knobs and faders do. Here's a video showing how to map your Korg Nanokontrol 2 inside of MainStage. Hey there! If there's a MainStage subreddit, I bet they'll honestly be better equipped to help out however I have used MainStage a little bit and can maybe get the ball rolling for you.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |