Mainstage Mixing

I have searched but still no avail.
I want to start taking our electronic music on the road and play live, we use logic and use the plug ins a lot so mainstage is a good choice.
We cant play EVERYTHING live so ideally we will have to keyboards and a guitar.
What i want to know is is there an interface i need that means i can control mainstage, ideally like a mixer, so i can control the backing tracks as well as the keyboards externally.
For example, i would like a seperate track to control bass, drums, ambient noise etc. Almost like a Akai controller for live with those faders on the bottom.
Or how would anyone else play live for electronic music with mainstage with only 2 keyboards?
Glenn

I can speak for the Behringer, haven't tried the Evolution The bcf2000 is a bit klunky and challenging to learn, but there is plenty of online support, and the motorized faders sync up nicely with MainStage. So, yes you can control all the volumes with the faders, plus anything else you want with the rotary controls. I don't think the Evolution has motorized faders, so I would go with the Behringer so the faders move to adjust to your current MainStage volume settings. Less thrash!
If you keyboard is MIDI in/out only, you will need to be using a MIDI interface connected to your Mac, like a MIDISport or something. The Behringer will connect via USB. The MainStage doc explains how to set up a virtual instrument, played via your physical keyboard. To get your backing tracks synced up, there have been some other recent threads about this, so you may want to read those. You can also run your guitar through MainStage, but would need an audio interface. Some interfaces combine audio and MIDI, though, so one interface could do double duty.

Similar Messages

Main Stage 2 Mixing Console plus backing track play list ?

Is it possible to set up a play list of backing tracks in the 8 channel mixer template ? I need to run 4 sets of 10 songs all within the 8 channel mixer since the band all plug into my presonus and we use the Mainstage mixer as our main board. I need to be able to select between songs while keeping the same mix on the console.

MainStage doesn't have "tracks", only channel strips and sets/patches. And the limit was 255 in MS1, now it is 1023. I think a few users actually reached the 255 limit in MS1

Mainstage 2 external fader assign to mainstage 2 fader

Hi,
I am trying to assign my external hardware mixer fader to mainstage software fader.
If i touch any button on my hardware mixer : fader volume, play stop etc. the midi info window
in mainstage (top center) indicate that midi is communicating with mainstage.
I am trying to assign my hardware external fader 1 to 8 and the master fader to my mainstage software fader.
I can't find the way to assign them to the mainstage mixer.
Anybody using a external mixer with mainstage instead of a keyboard?
Thanks
Luc

Thank you for takiing the time CCTM
Basically, i was able to build faders into layout. assign them to my MS faders into edit. I was also able to assign the Tascam FW1884 fader to the MS faders but they act like crazy moving up right away and down without any slow motion like a volume fader would do. i think it is the way the cc are read or some sort of midi programming?
I am totally new to midi stuff so... I tried to change my midi to mackie control emulation and i was able to get the fader move normally in the layout mode until i remove my finger from it. after letting go the cursor the left inspector option are change auto: the channel option, type option, the number option change automatically to new values that make the fader act like a on off button instead of a fader?
i thinking about using my boss gt-8 then. Using footswitch to press play, next song etc. again that is probably a lot of programming to match MS buttons and options? i will have to figure out the midi mapping if i can't get my FW1884 to work the same midi language...
Do you have any advice
Thanks again grealtly appreciated french guy so excuse my english
Luc

Piping dry audio into MainStage for mixing/auditioning fx

Hello, is there anyway to pipe multiple tracks of dry audio and midi (like the playback you would see in logic) into mainstage so I can mix and audition fx/plugins using playback instead of performing live stopping tweaking knobs and on and on? Should I just do this in Logic for each song, save the channel strips, and then load them up into mainstage when they are all finalized? Thanks ^^

I'm not familiar with the apogee duet but assuming that it has multiple audio outputs, you will be able to select the output channel for the metronome through its channel strip, just like any other channel. That will give you exactly what you want.
As for reliability, my experience is that MainStage 2 by itself has become quite reliable if you're just using internal synths and softsynths and you create your concerts from scratch rather than importing concerts from MainStage 1, this latter apparently being the cause of glitches for quite a few people.
However, if you want to use external MIDI devices, then I have found that MainStage2 causes eroneous notes to be generated from time to time. As long as you're not doing any MIDI output, you should be in great shape.

Mainstage 2 & Euphonix MC Mix

Have been using MC Mix with my Logic 8. Upgraded to Logic 9, & would like to know if any knows how to utilize the Euphonix MC Mix as a control surface for MainStage 2.
Running MS2 in 32 bit mode, therefore no issue with Eucon protocol for Logic 9.
I know you can map Midi signals to controls, but with the MC Mix using Eucon protocol possible.
Layout mode recognizes the Euphonix mixer, but will not learn.
Any help ideas or ridicule appreciated

I've decided to "take the plunge" and jump right into Logic 8. The few days I spent mucking with Garage Band really helped as there are some similarities with Logic. With the help of forums like this and Apples' superb printed manuals which accompany Logic 8, the task seems quite "doable" for a relative newcomer to computer based recording. I just got my Euphonix today and I KNOW it works beautifully with Logic. Just for fun I may give it a try with Garage Band and see if indeed it does work. Thanks for the replies guys!

Anybody using MainStage as their only live mixer?

I'm interested in mixing small combo gigs and maybe even some corporate a/v stuff using MainStage on my MacBook Pro in place of a mixing board.
I'd probably get a small MIDI controller like the Korg nanoKontrol for quick access to a few key parameters, but I'm not looking to get all King Tubby about it. Also, I'd like to keep the overall footprint small.
I'm figuring I would go with 8 in's and out's via my MOTU 896, and hook up to a power amp and speakers.
Thoughts? Experiences?

here's what I'm thinking about:
Came up with this idea the other day and going to start working on it in the next couple weeks. 8 channel firewire interface (eventually 16) into mainstage setup as a virtual mixer like a lot of people have done...and then using touchosc on the iphone/ipod touch as my wireless control surface to control the live mix. then using the 2 of the outputs on the interface for the mains, and then having 4 independent monitor mixes for each musician using powered monitors on stage. This method will hopefully allow me to save presets for each song.
http://www.hack2learn.org/wp-content/gallery/touchosc-vdmxinterface/TouchOSC-Int erface%20006-wText.png
touchosc is program on the iphone that is basically an interface that allows you to put whatever- buttons/faders/rotary knobs/pads/eqs/x-y grids/ect -that you want on up to 4 pages...if you google it you'll get some ideas of what all you can program on it...the iphone then connects to your computer over a wireless network and sends OSC signals to the computer...then use a program like osculator that converts those signals to midi signals that can be sent to mainstage...then use the learn function to map all of your parameters..and thats basically it. You would think that there would be latency going over wifi, but i hooked this thing up to ableton to use it like a small MPC beatpad, and there was no latency at all. Of course i created a direct wireless network from my mac to my iphone..that might have helped...
now obviously an iphone or ipod touch is small, but imagine doing all of this on an IPad? yes? I'm really excited about the IPad for this one reason almost...the idea of controlling the live sound "wirelessly" with a 10inch touch screen device from any part of the room...It theoretically sounds doable, but gonna have to go through some major testing before i rely on it.
the one part i havn't figured out yet is to be able to run a headset with built in mic into the IPads headphone jack to use for monitoring and as a talkback mic to the stage. If only the IPad could run multiple programs at a time.

Can I use my iPad 2 with Mainstage 2 as a mixing surface for my keyboard rig?

How do I use ipad2 with mainstage as a mixing surface for my keyboard rig?

Hi Capp 543:
I don't really use it any more live, mainly because I use my iPad for reading music and don't want to switch around apps. I'm not part of the company, but I'll try.
IMO the iRig manual is way way too simplistic.
I am attaching some jpeg's of what helped me solve it, though it was tough. If it doesn't open, search Audio Midi Setup help for "sharing midi data over a network". You have to create a wireless session using Audio/Midi setup, OR create an "ad hoc" network using bluetooth if there's no wi-fi (another set of problems...). This may be your issue. There are a few things beyond getting the wireless network appearing that you have to do, that's why I'm suggesting this even though you did it, or a part of it.
In particular:
"Anyone" has to be set as who can connect to me in the lower left of the wireless midi setup screen, and
First get everything else ready, meaning the iPad connecting, THEN LiveRig has to be launched from closed, meaning do an icon hold and close in down iPad, then open it up for it to connect, when everything else is ready. for some reason that helped me.
In MainStage, you of course need to go to the MainStage #1 Setup screen, drag in sliders, then "learn" them to the LiveRig, which should now be seen when you click "learn" and move a Liverig slider. I have a vague recollection about not seeing iRig in the MainStage #1 top left device window, but then going into the drop-down menu there where the device shoudl be, selecting it, then learning the sliders. Then in the #2 Edit window you assign the sliders etc.
I would suggest first connecting it via midi wires and getting it to work, which will help you decide if a problem is in the wi-fi or somewhere else when you go to connect it up with wi-fi. You'd need the Apple Camera Connection kit adaptor. I myself would alway run it via midi if I'm playing live, too many unknowns with unknown networks.
Hope that helps.
Neil

Can MainStage split the audio outputs from a plug-in to separate busses/out

Take EXS24 or Battery 3 or Kontakt as examples
Only one plug-in instantiated but each drum 'hit' sent to separate outputs from within the plug-in/VI and brought into the mix on Audio/Aux channels for separate processing.
It's easy to set up in ProTools and Logic.
(I don't want to send the output of the channel strip to a bus - I know how to do that)
I've read the manual so many times and can't find any answers.
Does MainStage actually allow this routing ?
Thanks for any help
Lee

As far as I know, the only way to do what you want in MainStage is to set up an EXS24 for each output.
The EXS24 does have an option to load with multiple outputs, but I haven't found a way to make it work on my set up.

Weird Slider Behavior in MainStage 3

I was in rehearsal last night using Mainstage to power sample play. Ran into a problem. I've created a patch out of a mix of three sample plug ins: two EXS sounds and 1 Kontakt sample, hence, 3 channel strips. I had set the volume sliders at various levels to get the right timbre, but while performing, those sliders would automatically change without me touching anything but keyboard keys and sustain pedal, changing the patch to an unwanted timber in mid-stream and forcing a re-set of levels after stop. Anyone have any ideas why this might be happening or if there are settings changes or other fixes I might try to correct this?
Grateful for any response,
Michael

Thanks, you 2. My contoller is an older M-Audio Keystation 61s. It had been hooked up to an older Macbook and the operation was clean. But, I've just hooked it up to a new MacBook Pro running MS 3 and the problem started. I'm wondering if this could be part of the issue:
The new laptop runs USB 3. It's supposed to be backward compatable with USB 2, which is the controller output, but the M-Audio site cautions that this may cause problems. They don't support USB 3 as of yet. In general, the hookup works - Keystation is powered, is recognized and plays all MS libraries. But now I wonder if there's a compatability problem causing the CC7 problem.
There's a way block CC7 messages in MS? I'll look into that, but if you can simply explain, I'd be grateful. Thanks.
Also, if my theory is correct, do you know of any device out there that can do a clean (sans speed boost) USB 2 to 3 Conversion inline?

MainStage 2.2.1 released

Symptoms
MainStage 2.2.1 is a software update for MainStage 2.2. MainStage 2.2 is a feature upgrade for MainStage 1.0 and 2.0 customers available for purchase on the Mac App Store. MainStage 2.2 includes several new features and fixes.
Installation
Resolves several issues related to the download and installation of basic and additional content.
Performance
Addresses an issue in MainStage 2.2 that could decreased performance of the Playback plug-in on computers with one or two cores.
Resolves an issue in MainStage 2.2 that could decreased performance when using the 8-channel mixer & backing track template.
Resolves an issue that could increased latency when playing software instruments with MainStage 2.2.
Improves performance when running multiple instances of EXS24 in 32-bit mode on computers with multiple cores.
Addresses an issue in MainStage 2.2 where performance decreased compared to MainStage 2.1.3 on non-hyper-threaded 2-core computers.
Audio
Fixes an issue in MainStage 2.2 where only the left side of the stereo signal was sent to an Aux if the channel strip had any mono to stereo conversion.
Panning now works correctly on outputs other than output 1-2.
Sends set to Post Pan now pan properly on mono channel strips.
Fixes an issue that blocked sidechain input for plug-ins.
Resolves an issue in MainStage 2.2 where the left side of external stereo audio signals was duplicated and processed by both sides of a stereo channel strip.
Plugins and Patches
Fixes an issue with using keyboard arrow keys to scroll through the Patch Browser.
The Hide Ruler option for the Waveform object again works as expected.
The slide direction of drawbars in EVB3 is no longer affected by the Scroll direction setting in Mac OS X 10.7 Lion.
Resolves an issue where the bottom of some plug-in screens were not accessible on 11” MacBook Air when the plug-in was opened in Controls View.
General
Corrects various problems in MainStage 2.2 with non-English localizations.

CAN MAINSTAGE 2.2.1 DO THIS?
Take a look below at SONAR...
You'll notice on the left...
- The Song/Project List with infinite number of songs. Open up next song Automatically or user defined. Change Song/Projects around on the fly with the mouse. Yes you can have the next song open up automatically, or user defined such as any delay you wish before the next song starts, or start the next song by pressing the spacebar. Also closes current Project/Song when done & opens up next Project/Song.
You'll notice on the right...
- Opens up the Project you're going to play, with ALL AUDIO, VIDEO, MIDI IN/OUT PROGRAM/CONTROL CHANGES, AND ANYTHING ELSE YOU WOULD PUT INTO A SEQUENCER, & CONTROL EXTERNAL/INTERNAL DEVICES!
P.S. WE ONLY USE SONAR BECAUSE APPLE DOESN'T SEEM TO WANT TO INCLUDE THIS CAPABILITY IN LOGIC!
- SO DO WE HAVE TO TRANSFER PROJECTS INTO MAINSTAGE?
- DOES MAINSTAGE TO THE ABOVE?
click to see image full size...

What kind of audio interface do I need for audio out from MainStage 3?

I have a Yamaha MO8 that I use for playing in the worship band at my church. In the past, I've just directly routed audio from the MO8 through a direct box and into the sound system.
I'm looking to switch my setup and use the Yamaha MO8 as a midi controller in MainStage 3. I have this part working — the problem is getting the audio from my MacBook Pro.
The audio output sounds fine through the MacBook Pro speakers or through headphones plugged into the audio out / headphone jack; however, if I plug the direct box into the MacBook Pro's audio out / headphone jack, the signal the sound system gets is very pretty weak and very distorted.
I'm assuming I need an audio interface between my MacBook Pro and the direct box / sound system. Since it's a 2010 MacBook Pro, I'm assuming my only output option is USB (unless the digital audio out can be used). If that's correct, would something like the Scarlet 2i2 work for me?
Thanks…

Yes, you'll need some sort of audio interface to get a good signal back to your mixer.
The Scarlet 2i2 would work for you but you may find a few limitations. I use a MOTU Audio Express and it has the advantage of being a mixer as well, so I can mix in a backup signal from the onboard audio outs of my controller (Kurzweil PC3x) in case MainStage goes down (it happens on rare occasion). Firewire is my preference so the MOTU checks that box. I also like that I can connect my MIDI cables to the MOTU and have one cable going into the computer.
If you need this sort of compact redundancy, I would shoot a little higher than the Scarlet. If you don't feel the need for a backup line and USB works for you, then the Scarlet unit would be an excellent value.

Got crackling audio in MainStage 2.2.2? I did, and here's how I fixed it...

A lot of people are talking about an issue in MainStage 2.2.2. where crackling audio gradually builds in the signal and eventually becomes unbearable. I had this issue but none of the solutions I found in the support community worked for me.
The obvious fix is the increase the sample buffer size until the issue goes away (as it's often a matter of the CPU not being able to handle the load, especially on older machines). You can also turn on the Safety Buffer checkbox, which can further reduce the problem. My issue wasn't solved this way, unfortunately; no matter how high I increased the sample buffer, the problem persisted.
It seems the problem was being caused by my USB interface, which is a very good unit (the Focusrite Scarlett 18i6). My first mistake was that I used the Scarlett for input, but used built-in output. I suspect the Mac (2012 non-Retina MPB, 2.3GHz i7, 16 GB RAM, SSD) had trouble synchronizing with the device. I routed the output to the Scarlett as well and that seemed to fix the crackling. I had a problem with the device putting the dry signal Mainstage, which wasn't good. I then downloaded the software mixer (found on the Focusrite site) and, when I tried to run it, it told me the Scarlett needed a firmware update. So that was applied. I then ran the mixer and chose "DAW1" routing preset. After that... no more problems at all.
If you're having this exasperating experience with crackling and the buffer size doesn't fix it, perhaps the steps I took could help you find a solution as well.
Good luck!

A lot of people are talking about an issue in MainStage 2.2.2. where crackling audio gradually builds in the signal and eventually becomes unbearable. I had this issue but none of the solutions I found in the support community worked for me.
The obvious fix is the increase the sample buffer size until the issue goes away (as it's often a matter of the CPU not being able to handle the load, especially on older machines). You can also turn on the Safety Buffer checkbox, which can further reduce the problem. My issue wasn't solved this way, unfortunately; no matter how high I increased the sample buffer, the problem persisted.
It seems the problem was being caused by my USB interface, which is a very good unit (the Focusrite Scarlett 18i6). My first mistake was that I used the Scarlett for input, but used built-in output. I suspect the Mac (2012 non-Retina MPB, 2.3GHz i7, 16 GB RAM, SSD) had trouble synchronizing with the device. I routed the output to the Scarlett as well and that seemed to fix the crackling. I had a problem with the device putting the dry signal Mainstage, which wasn't good. I then downloaded the software mixer (found on the Focusrite site) and, when I tried to run it, it told me the Scarlett needed a firmware update. So that was applied. I then ran the mixer and chose "DAW1" routing preset. After that... no more problems at all.
If you're having this exasperating experience with crackling and the buffer size doesn't fix it, perhaps the steps I took could help you find a solution as well.
Good luck!

MainStage 2 performance / CPU Spikes

MainStage 1 was almost perfect.
Just to join the misery ... Same problems (i am reading about on Forums everywhere) here with MainStage 2. Huge cpu spikes and stuttering audio from Virtual Synths. Basically unplayable. CPU usage is at least 30% higher, even when NOTHING is happening. Also memory usage behaves strange, its way too high. Nr of Virtuals doenst really matter, lets say 3x a Native Instr B4II is enough to crack it.
Strangely enough .. as a Rewire App (receiving 20 channels from Ableton, and mixing them in MainStage) ... it behaves quite well.
They got to be working on a fix here. I Hope. Any Apple insider reading this who has word ?

44100KhZ / 16Bit.
After re-creating my entire concert from scratch, my problems are 'sortof' over.
No audio stutters anymore.
Conclusion : Importing MS1 concerts in MS2 is probably not without errors.
===
Still, CPU Usage Meter goes crazy (randomly in RED).
I know .. many people told me .. don't worry .. its fine.
Just don't like it, and if the MS2 CPU Usage Meter is mirroring the one in Activity Monitor, whats the bloody use anyway ?
===
Memory Usage behaves strange. Its rising and rising while i am changing patches. Seems to me Memory Management has a bug.
Still hoping for a fix.

MainStage 2.1 release (64-bit)

MainStage 2.1 Update
This update delivers improved compatibility and numerous fixes.
Issues addressed include:
Support for 64-bit native mode
Compatibility with 64-bit Audio Unit plug-ins
Improved compatibility with MainStage 1.x documents
Multiple Playback plug-ins in the same group now sync reliably
Improved recording when using the Loopback plug-in
Updated System Requirements
32-bit mode requires Mac OS X 10.5.7 or later
64-bit mode requires Mac OS X 10.6.2 or later
The update is recommended for all users of MainStage 2.
For detailed information on this update, including some restrictions when working in 64-bit mode, please visit this website: http://support.apple.com/kb/ts2566

MainStage 2.1 Update
This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2.
* An issue where Pressing Command-N to create a new concert could lead to MainStage quitting unexpectedly while the Save dialog was open for a previously loaded concert is resolved.
* An issue that sometimes led to MainStage quitting unexpectedly when closing a concert or quitting MainStage is resolved.
* An issue in which the Invert checkbox for mapping ranges could be unexpectedly enabled in a concert where the minimum mapping range was set, but the maximum was not altered is resolved.
* An issue where CPU usage was initially higher than expected when loading some concerts created in MainStage 1 is resolved.
* Importing patches from a concert whose layout contains more keyboard screen controls than the current concert no longer sometimes leads to incomplete display of settings in the Channel Strip Inspector.
* An issue that lead the the name in the Mixer to fail to update when renaming an alias of a channel strip is resolved.
* An issue where changes made to MIDI Out parameters on an external channel strip were not immediately displayed in an alias is resolved.
* The screen display of an expression pedal in an alias patch now moves correctly in response to incoming data.
* The number of sends shown on channel strips now immediately updates as expected after cut, copy, or paste of channel strips.
* An issue that prevented mapping a screen control to the mute parameter on Bus 8 is resolved.
* An issue where it was not possible to return audio from an Aux higher than Aux 8 is resolved.
* Sends no longer sometimes lose settings when patches are imported, copied, cut, and pasted.
* Polyphonic aftertouch is now sent to external instruments as expected.
* Polyphonic aftertouch sent to software instruments no longer causes unexpected parameter changes.
* Dragging an audio file into an empty patch now creates a channel strip with a Playback plug-in instantiated, as expected.
* An issue that prevented EVB3 drawbars in the workspace from correctly updating when MIDI to Preset Key was enabled, and a new preset was triggered via MIDI, is resolved.
* An issue that prevented screen controls from updating properly in response to CC7 and CC10 messages is resolved.
* Mapping to Solo now works properly with hardware buttons that send single MIDI values.
* Changing a Send All mapping from a channel strip directly to a MIDI mapping now works correctly.
* Grouped buttons now update correctly with the send level parameter.
* Mappings are no longer sometimes lost when importing layouts and patches exported from MainStage 1.x.
* Reset to Saved Value now works reliably when changing patches.
* MainStage no longer intermittently stops responding when choosing Undo after deleting patches.
* An issue that prevented Keyboard objects from sending to all channels of a multitimbral external instrument is resolved.
* Inputting notes while auditioning patches no longer sometimes causes MainStage to sometimes unexpectedly quit.
* The I/O plug-in now works correctly on channel strips with "no input" selected.
* MIDI input now works reliably with grouped keyboard controls.
* The alert dialog "The document 'Untitled Concert' could not be saved as '2'" no longer appears when saving a concert with a long file name.
* An issue that prevented Apple Remote from working as expected in Full Screen mode with Mac OS X v10.6.2 is resolved.
* Setting preferences when there is no concert open now works as expected.
* Parameter tabs now maintain a consistent order for multimapped parameters in duplicated patches.
* Changes to "send Program change" and "send Bank change" in patches are now reliably saved.
* Recordings in Loopback are now reliably maintained when Play on patch change is used while the transport is running with "Snap to:" set to "Bar/Beat."
* Count-in now starts immediately on play in the Loopback and Playback plug-ins.
* Setting a Loopback and Playback plug-in the same group and then recording to the Loopback no longer causes MainStage to quit unexpectedly.
* Issues that sometimes caused the metronome to drift out of sync with the Playback and Loopback plug-ins are resolved.
* MainStage remains responsive when making tempo adjustments in concerts that contain multiple instances of the Loopback plug-in with sync enabled.
* The "Start with Play Action" command now reliably triggers all instances of Playback and Loopback in a group.
* An issue that sometimes caused a small section of unexpected audio to sound when switching to a patch with Playback that had previously been stopped with the "instantly silence previous patch" command is resolved.
* The "Begin Finding Patch in Performance" key command now works properly with patches whose names start with numbers.
* Using the Undo command after deleting an object that is a member of a group in the workspace now correctly maintains the object's group membership.
* Control labels are now correctly displayed when switching from full screen view to layout view.
* An issue that caused the workspace in layout view to be invisible when remote connecting to a computer running MainStage with no display connected is resolved.
* An issue that caused objects to become ungrouped when dragging them from the palette to the workspace is resolved.

Cannot hear sound through headphones when running mainstage- Mackie 1220i interface

I am currently running Logic Studio with my MacBook Pro with a Mackie 1220i mixer/interface. I can hear the processed sound fine on the mic channel and the guitar channel when the headphones are plugged into the mixer but I get no sound when the headphones are plugged into the MacBook Pro. I am trying to set up a concert in Mainstage. Suggestions?

If you want to hear through the headphones of macbook pro you should change,
in preferences of manstage,
Go to audio
Audio output from Mackie,
set Built-In Output

Mainstage Mixing

Similar Messages

Maybe you are looking for