Apple MainStage 3.3.1 Crack
Mina Spartin
I am running a Mac, with version 10.8.5, and Mainstage 3, but I am having trouble setting up the MIDI channels. For example I create two channel strips, one for a piano sound and the other for a string patch, but when I press a key on my AxiomPro 61, it triggers the sounds of both the piano and the string patch. I know it is becaue they are both set to trigger on channels 1-16, and that is the problem, I can not figure out how to "route" the MIDI channels correctly. I think my problem is in the "Layout" tab in the "assignment" section, but i am not sure. Spent hours fiddling with this today, could really use some help.
In layout mode, I create one keyboard for each MIDI channel I want to use with my master keyboard. For each keboard I select the correct input device (my master keyboard) and the correct MIDI channel (only one channel for each keyboard, not "1-16"). Then in some patch I create a few channel strips, and for each channel strip I select the correct keyboard as input. You can do this by activating the channel strip and then going to the midi input -tab. So then by changing the output MIDI channel of my master keyboard (where I have quick buttons for this) I can control which soft synth is playing in mainstage.
If you only want one instrument to play, just assign one channel strip per patch. Note the patch list- three different patches. Each has only one channel strip. The second example shows the channel strip of patch 1.
Are you trying to control both channel strips from the Axiom Pro 61? Do you want to play them one at a time from the Axiom? If so, assign each channel strip to a different patch. Routing MIDI channels is different in Mainstage from hardware MIDI devices. Give me more details and I'll get you on the right track.
I assumed I would just choose the controller/keyboard and then assign each channel strip to it's own midi channel, and there in lies my issue. I clicked on the channel strip I created, and set the midi input to my keyboard (C1), but the only way I hear anything is to set the channels to 1-16----which then triggers all sounds at once.
First, create a new patch(in edit mode). To the the right of the patch list, click on the "+" to create a new patch or click on the cog wheel for other patch list options. Then create a channel strip by clicking the "+" in the channel strip section. If you want to copy a channel strip to a new patch, select the channel strip, go to edit>copy(or command>C). Then select the new patch and edit>paste(or command>V). Don't worry about assigning MIDI channels. To access your patches you have the option to have them respond to program change numbers from your keyboard. If you want to split the keyboard, create two channel strips and set their note ranges in the channel strip inspector>layer editor(get there by first selecting a channel strip). See snapshots below.
I don't think I am quite getting my problem across. I have multiple channel strips created, and have various plug ins already setup for each. Track one is my piano sound, track two is my bass plug in, three is my strings sound, etc.
As I mentioned I think the "Assignment & Mappings" tab in Edit is where my issue is----if I go there and select MIDI channels "1-16" I can then hear what I am playing---BUT it triggers all three parts, the piano, bass, and strings all at once.
Here is a snapshot of the trouble I am having----notice in the "assignments & Mappings" tab I only get sound when I select "1-16" channels, you can see in the bottom left the meters triggering on all three channels when I strike a key on the keyboard.
Thank you very much. I was actually able to do as you suggested, I set up two keyboard in Layout (keyboard 1 and keyboard 2) and assigned them to MIDI channels 1 and 2, and by manually turning one of my encoder knobs on my AxiomPro 61 I can switch between the two.
But it seems like I should be able to just click on a channel strip and be able to hear that particular sound and I noticed one other big issue-----when I pulled up a B3 organ patch, it suddenly showed up under my "channel 1" with various control parameters, like modulation for the B3 patch----so if I had it setup with a piano or something on channel one it would change my settings....
Just in case anyone is using an AxiomPro 61----shouldn't there be some "omni" type setting in Global that would allow the keyboard to work witout having to turn an encoder knob to change the channel MIDI need to transmit on?
I doubt if it's possible at all to make Mainstage work like you want, i.e. make clicking a channel strip somehow affect which channel strip receives MIDI input. Logic works like that, because it makes sense in a sequencer, but Mainstage is a live tool. I think usually the case is that people do not want to touch channel strips at all when performing, the UI to use is the workspace, patch list and your MIDI hardware.
Why don't you just create multiple patches and put each sound (channel strip) in its own patch? Then you could just click on a patch to change the sound (in this case you only need one keyboard in layout, input channels 1-16, and set this keyboard as midi input for all of your channel strips).
I actually set a patch up in my AxiomPro which would allow me to easily use to buttons on my controller to quickly move through MIDI channels, but then Mainstage apparently re-routed the buttons on the AxiomPro when I started the program, so even that wouldn't work.
Essentially, what I'd like to do is just have a template for our basic live setup, which includes: 1 Bass patch, 1 Guitar patch, 2 Vocal patches & 1 Playback track, and be able to create 4 in-ear mixes for each of us...
The problem I'm having is that the terminology in MainStage 3 is kinda confusing & nothing in the manual or any tutorials I've hunted down have anything about setting up MainStage for a full band.....yet like I said, I've seen a couple people using it for their full band's setup, live...
I think I finally made some progress yesterday, by figuring out that a "patch" in mainstage isn't exactly just a patch, in the traditional sense...and that a "set" basically represents a song, not a full set...the labels were what was really confusing me. I kept setting up a set and then opening individual patches under the folder, that I thought were needed for each individual instrument, and couldn't figure out why it was only letting me use one patch at a time...lol
So, what I did was open a new "patch" & loaded all our instrument/vocal patches via the channel strip & it seemed to work, but I'm still pretty new to midi mapping and all that, so I didn't get all of my setup done...
Does that sound right? Should I think of a set as representing an individual song & a patch as representing our global settings/patches for all instrument patches on that song? That's really the only way I've figured out how to get all of our channels "armed" at once...
Now, if you want to use Mainstage by itself, without automation, you may need to create your channel strips at the patch level for anything that will change often through each song. For example, if you want your guitar sound to change between the verses and choruses...then don't make the guitar track at the Set level...only make it within each patch, so that it will have the different settings.
As Authentic Identity has posted, what you've asked is easily possible. However, be careful with the plugins you use because some add a degree of latency that mightn't be acceptable to some band members.
I hear you man! I looked up this discussion precisely with the same exact question... In fact I even watched a guy on youtube ( ) @ 2:50 do it and my mainstage does not give me the option of "new concert" like his does... It just gives me the option of "New..." and goes right to the templates... when he did it, it opened a blank template just like we both want. Does anybody else experience this?
I'm running Mainstage 3.3.2 with a variety of 3rd party software plugins. When playing a piano patch in Kontakt (for example) often Mainstage will stop playing these notes and spit them all out at the same time a few seconds later. This does not register on the CPU load history window.
This started happening during a concert series, and I tried everything possible to fix it. All the sounds are on external SSDs. I replaced the SSD enclosures with brand new USB3 enclosures plugged directly into the iMac.
Check your audio buffer settings. Go to preferences>audio>advanced settings. Try adjusting the settings to achieve an optimum balance of performance and CPU load. Other issues could be your USB or USB-MIDI cable that connects your keyboard to the Mac. Try a different cable.
It's not an audio buffer setting. I've adjusted the buffer to plenty large enough, but it's not a CPU issue because it doesn't show up as a CPU spike. I tested it again, and the rainbow wheel shows up.
Have you considered updating the OS to High Sierra (10.13.5)? I don't know if that will make a difference. I was able to duplicate the MIDI buffer issue. MainStage doesn't respond well to CC 64 continuous data. I don't know if you're using a pedal that sends continuous data. Switching it to a simple on/off setting (0 or 127) seemed to help. Run MIDI message monitor to see what commands your controller sends that may be a factor.
Please check, if your master keyboard spits out MIDI info, that's not required, like Aftertouch, etc. If so, switch it off in the keyboard itself to lower the amount of data processed by the MIDI engine in MainStage.
Another unusual thing might be the USB wiring / power supply. I had issues with my audio interface if using the 3-prong plug with the power supply. This seems to lead to a USB ground loop, which causes pretty unpredictable things, like MIDI devices coming and going, audio interface ceasing their services, etc. Once back to the 2 prong plug, all went well again.
That might well be. Please report, if switching off autosave does change the situation. If so, you might consider dropping off a report at apple.com/feedback. Maybe a developer reads this and fixes the issue. OTOH, a minute ago I didn't know, that Mainstage has autosaving ..... never missed it.
7fc3f7cf58