MainStage 1.0.1 available

Here's to seeing Logic 8.0.1 shortly to solve the controller problems.

I'm guessing this is the same issue with Logic finding controllers. Might not be a problem in MainStage but the core libraries somewhere. We'll get an update if they spew one out this quick I'm sure one for Logic will be coming.
R

Similar Messages

  • MainStage 2 manual available

    The MainStage 2 manual is available:
    http://manuals.info.apple.com/enUS/Exploring_MainStage2.pdf

    Seems to lead to the SAME version of the User Guide as seen HERE

  • Where can I get an older version of Mainstage?

    I am a worship leader and would like to use Mainstage to run loops and backing tracks during a live setting. My MacBook is a 2006 A1811 with a core 2 duo processor, running 10.6.8 . It can not download Mainstage 3, where can I get an older version? PLEASE HELP!!!!!

    Older versions of MainStage are no longer available for sale. The _only_ way might be buying a used Logic Studio 2 box which contains MainStage 2.1.3. Quite a pricy endevour for an almost 3 year old application.

  • Logic Express and MainStage 2

    Is it possible to use MainStage 2 with Logic Express 9.1.5.?  Are there any limitations to not having Logic Pro 9.  I'm very happy with LE9.1.5. as it meets all my needs (perhaps with the exception of not having Space Designer) but if I need to upgrade to get the most out of MainStage 2 then I will.  I've posted this in the Logic Express Forum, as well, as I'm not sure of the best place to get an answer.
    Thanks

    Oh yeah, and Logic Express will automatically inherrit 15,000 new Apple Loops from 6 Jam Packs and probably more than 1000 EXS24 sampled instruments!! So, yeah, $29 is a great upgrade for Logic Express. To be clear though, the 120+ plug-ins from MainStage will not become available in Logic Express. They only work in Logic Pro and MainStage.
    Have fun!
    ps- get started fast with video training..
    http://www.macprovideo.com/tutorial/mainstage2101

  • Mainstage 3 for Plug-Ins Only vs Mainstage 2

    I use garageband for recording and read that I could use the Jam Packs by just buying Mainstage 2. I don't care about loops, I only want more software instruments to use when I plug my midi drum set in. I need to upgrade my OS to get Mainstage 2, so I ordered an OS upgrade. Now, I see that Mainstage 2 has been replaced by 3 and I do not have the RAM required for 3 (4GB). I do not want to buy RAM now in addition to the OS I didn't even really want to buy. Will Mainstage 2 still be available? Could I just buy Mainstage 3 and only use the plug-ins even if my cpu is too slow for the program itself? Bonus: how many more drum kits does 3 have vs. 2?
    THANKS!!!!

    Regardless of what happens more RAM is always a good thing... and given how cheap RAM is you should always want to add more.
    If you have already bought MainStage 2 it will still be available in the Purchases tab in the Mac App Store app. If you don't have 2 then you can no longer buy it from the store.
    You asked if you can use just the plug-ins of MainStage 3 even if your CPU is too slow. The problem with that is that it's the plug-ins that require a fast machine. Launching the app isn't going to be the problem on a slow machine... it'll be as you start to add plug-ins. If you you very sparingly use plug-ins then it should be OK.
    Not sure about how many kits as I still need to download the additional content.
    Good luck...

  • XServe with Snow Leopard and Mountain Lion Clients

    Okay, bare with me, as I'm fairly new to the whole Mac Server world. I have learned a whole lot over the last year and I've been able to completely manage our 60 Snow Leopard Clients on our XServe.
    Last year, I came into an existing setup with ~60 clients running Snow Leopard and an XServe running on Snow Leopard. We utilize Server Admin and Workgroup Manager to manage our user accounts and our clients. We have over 300 users and utilize Portable Home Folders with our accounts.
    Over the last year, I've learned a whole lot about managing the system that is already setup. I've made quite a few preferences and file structure changes utilizing Server Admin and Workgroup Manager. After getting new hard drives in three machines, I learned how to re-image them and get them set back up with our Workgroup Manager. I learn things pretty quickly and have a pretty high technology aptitude.
    So, here is the predictament I'm in now...our county just purchased 31 new Macs to add to our network. These are running Mountain Lion.
    I have a few questions, and I'm not exactly sure where this post should have been. I think the major questions/issues I face right now include:
    Will I be able to manage the Mountain Lion clients utilizing our existing server and Workgroup Manager?
    We need our server to work seemlessly with the 31 Mountain Lion clients and the 60 Snow Leopard Clients.
    Once I get one machine setup correctly, I need to create an image of it so that I can then utilize this image on the other 30 machines.
    How do I create an image and then deploy it?
    Do I complete this step before or after I have setup the first client with Workgroup Manager?
    Also, am I missing something? I just want to make sure I'm not missing anything important in regards to getting these new workstations setup on our network.
    Thank you so much for all your help! Any information you provide is much appreciated.

    No, you don't need an new license.
    But the Mac App Store doesn't allow you to download software, which you originally bought on DVD. Logic Studio is/was only available on DVDs, while Logic Pro, MainStage and Compressor are available in the Mac App Store as inidivdual applications.

  • When is Apple going to make Mainstage available to iPad users ?

    I'm a drummer and music producer, and I would love to see Apple make Mainstage 2 available for the iPad. Why haven't you guys done this yet ?

    These are user-to-user forums and are not monitored by Apple - and nobody here knows what Apple's plans are. If you want to leave feedback for them then you can do so here : http://www.apple.com/feedback/ipad.html

  • Mainstage Update available 2.1.3

    Hi,
    anyone there seeing secret improvements not mentioned in the update descriptions?
    Fox

    MainStage 2.1.3 Update
    This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2. Issues addressed include but are not limited to:
    MIDI Processing Issues
    The Patch List no longer lags behind the Workspace in response to rapid bursts of incoming patch change commands.
    MIDI messages on channels other than channel 1 are now properly routed to multitimbral software instruments.
    Compatibility Issues
    MainStage now properly displays factory presets for third-party Audio Unit plug-ins.
    Fixes an issue which caused MainStage treat multiple keyboards of the same model as a single keyboard.
    Fixes an issue in which MainStage did not respond to Concert download requests from the VAX77 keyboard.
    Improves compatibility with Native Instruments plug-ins configured to use multiple outputs.
    Stability issues
    Fixes several issues that sometimes lead to MainStage quitting unexpectedly when closing a concert.
    The template browser no longer becomes unresponsive after deleting a user-created MainStage template in the Finder.
    Resolves an issue in which MainStage might become unresponsive when Undo was performed after deleting several patches.
    MainStage no longer quits unexpectedly if the Tru-Tape Delay pedal time setting in the Pedalboard is at its maximum value at very slow tempos.
    Performance and stability are improved when switching between software instrument patches.
    Resolves an issue in which dense clusters of incoming MIDI events might cause MainStage to quit unexpectedly under some circumstances.
    General Issues
    The value displayed in the Layer Display Height Inspector control is now properly updated after Undo or Redo.
    Resolves an issue introduced in MainStage 2.1 that sometimes set the send values on certain channel strips incorrectly when patches were imported.
    Undo now works correctly after a channel strip is cut from a patch and pasted at the Set level.
    Fixes an issue introduced in MainStage 2.1 that prevented parameters from being mapped to screen controls in alias patches.
    Resolves an issue in which the polyphony set in patches containing ES2 was not always saved properly.
    Fixes an issue on multi-mapped objects in which the Momentary checkbox had no effect if set for the first mapping.
    Mapping multiple Pedalboard Sync parameters to a single screen control now works properly.
    Fixes an issue that stopped the Delete key from deleting mappings from the Mappings tab on the Screen Control Inspector.
    The "Send to All > Transpose Octave Up" and "Send to All > Transpose Octave Down" mappings now work correctly in patches with multiple channel strips.

  • Apple Loops in Mainstage?

    I'm very new to Logic software. I noticed that all the Apple Loops are easily accessible in Logic but not MainStage. Is there any way I can use them in MainStage? I tried exporting tracks as WAV and AIFF files but then couldn't figure out how to import them to use in MainStage. If Apple Loops can't be used in MainStage, is there a way to make, say, an atmospheric sound keep playing until you stop it from just one touch of the keyboard?

    Thank you. So, using MainStage as a live instrument, I'd like to play some of the great sound effects (wind/water/dog) and atmospheres I can find in Logic Pro under Loops. Is there any way to access these with MainStage? It would be a pity not to be able to for live performance, but if it's not possible, are you suggesting that I create the atmospheres for myself using the EX24 and Ultrabeat, or are you suggesting that there may be a way to use those software instruments to create loops of the sounds that are available in MainStage?
    thanks!

  • How can I use my UC-33e as a drawbar controller for EVB3 in Mainstage?

    Hi,
    I am a complete noob when it comes to Mainstage. I've been using Logic for close to a year now with relatively few problems, but I am stumped when it comes to MS, for a couple of issues anyway. Here's one:
    I use various software B3 emulations - EVB3, B4 and VB3. I use my Evolution UC-33e controller as the drawbars controller. I use this in Logic with no problem, took me a minute or two to figure how to set up the EVB3 but it all works great - in Logic.
    I was thinking that MS was basically Logic minus the recording and sequencing, but as for now that doesn't appear to be the case. I have my keyboard and the UC-33e both transmitting on Ch 1. When I call up the Jazz Organ patch (for example), I can still go into EVB3 and set it to recognize the NI controller set (which is what the UC-33e transmits), but when I move the drawbar controllers I will get patch changes, parameter changes, but nothing relating to the EVB3. I can go into layout mode and get the Drive control to work, as 'Distort Drive' is one of the parameters that are available on the layout for this patch, so I know it can work.
    Do I have to create a new layout that contains the controllers on UC-33e? I want to at least be able to use the drawbars, Leslie fast/slow, volume & drive.
    I'm also curious to know why this setup works with no problems in Logic but not in MS. I have 3 weeks to get MS set up correctly, but if I'm still having trouble in a week I'll just use Logic - I know that will work!
    -Doug

    I think I'll make it easy on myself. No MS, just NI. I'm using two keyboards. I'll use the Pro-53 for synth sounds, and have it set to see my little Arturia controller. I'll have Akoustik Piano and the B4 running on my 76-key controller, and since the B4 is set to run on Ch 1, I'll set AP to run on Ch 16 and just toggle back and forth using the MIDI buttons on my controller. If I need a Wurly or Clav I can boot up Elektrik Piano and set it to a different channel. Of course I can still use my UC-33e for the B4 as the drawbar controller as well.
    It's not elegant and I won't get to use channel strips or effects but it is way easy to set up, it gives me the sounds I need for classic rock, and most importantly, it works

  • Please help...  GiO not working properly with Mainstage.  GiO lights errors, and Gio Disconnected errors.

    I have a gig ion 11/22, and I am DESPERATE TO FIX THIS....
    Mainstage 3
    Brand new Macbook air
    Brand new Apogee Gio
    I've tried multiple reloads of the software
    2 macbook air 13"
    and 6 GiOs.
    These things aren't talking to each other.
    I bought the laptop SOLELY to run mainstage.  No other garbage is cluttering the box.
    I have 1 concert file, with 50 songs (Patches)
    Each patch has a few pedals configured on the layout screen, which are linked to the Pedalboard in Mainstage for various effects
    AT MOST, I have 1-2 channel strips PER PATCH...  Nothing seriously tasking on the CPU.
    THe CPU meter shows <20% capacity, always.  Usually <10%
    A few of the patches have a channel strip with a 3 second .wav file (audio channel strip)  NOTHING HUGE AT ALL.
    Problems scenarios:
    1.  MAINSTAGE FREEZES ON LOAD = 3% of the time....  
    Mainstage freezes at starup..  Jams on the "loading MIDI" message.  happens 3% of the time.
    2. MAINSTAGE reports "GiO has been disconnected" = 100% of the time...  
    I can sometimes play for 1 hour, no issues.... then all of the sudden, I hit a Gio Button, and i get the "Gio has been disconnected" message. I cannot play a gig, without this failing...    I have to REBOOT mainstage to get the stuff talking again, sometimes I have to RESET the Gio too (by holding a button and pulling/attaching the USB)  Sometimes Mainstage reconnects itself to Gio, most times I have to reboot everything.
    3.  GiO LIGHTS MALFUNCTIONING. = 80% of the time.
    Sometimes while I'm playing, the lights on the Gio fail to cycle when I press the buttons...  The lights on the MAINSTAGE screen layout behaive correctly, and the audio output is modified correctly when the buttons are pushed.... but the Gio foot switch lights fail to cycle.  For a particular song/patch, sometimes they work, other times they wont.
    I've had Apogee tech support working on this to no avail.
    They told me to unplug other usb devices.
    Try new cables.
    Increase the buffer size to 256 from 128 (which i did, but the latency/delay is unacceptable, and the problem still persisted anyway.)

    Super,
    I have a new Macbook Pro with Retina and an Apogee Gio and use Mainstage 3 under Mavericks (OS X 10.9.1).  I am experiencing similar problems to yours so I do not believe it is a problem with your particular machine or set up.  I have been using Mainstage and the Gio for a few years under Snow Leopard and Mainstage 2 without these particular issues.
    I am having the same hang on 'waiting for midi' at startup when the Gio is plugged into the USB port.   This seems to be occurring more and more.  I tried both ports on the Macbook Pro and it occurs on both of them sporadically.  I would say maybe 10% of the time.   I have discovered if you unplug the Gio usb cable at this point and plug it back in it will allow sometimes allow Mainstage to finish booting up. 
    The Gio is disconnected message I only had one time.  Only appeared the very first time I was using it on my new system.  I believe this was under Mavericks 10.9 (not 10.9.1).  I haven't been getting that message since.
    The Lights on the Gio hardware unit and Mainstage do not appear to be working properly here as well.  They seem to work properly for a while but then they lose sync with the templates.  I initially thought this might be caused by my particular custom template.   I tested today using the stock Gio Mainstage template from Apogee and the lights begin to lose sync on the Gio.  Buttons mapped to various pedals or amp settings on the Gio will sometimes stay on when they are supposed to go off or visa versa.  Using the looping functions the various foot pedal buttons sometimes display incorrectly (on when they are supposed to be off). 
    I believe the problems are  with Apogee's Gio driver or a software issue with Mavericks.
    I have filled out a feedback form to report this to Apple.  I would recommend you do this as well so they know it is an issue.  http://www.apple.com/feedback/
    I would also contact Apogee and see if they have an updated driver coming soon or if they have any other recommendations.
    If you resolve this issue or hear anything, please post.  Thanks.

  • 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...

  • Mainstage und Mac Book Air

    Does Mainstage  2.2.2. work with Macbook Air ?
    I1m working with  MacBook Pro  2,4Ghz  8 Gb  RAM,
    but sometimes the  Processor is  fully  employed  and  the  sound is  crushing,
    Has  sommebody  experience ?
    Thanks
    Gunter  ,   Detmold

    Without more specifics, it's hard to tell what is causing your CPU overload. If you're having the problem with just a few channel strips in a patch using only Mainstage instruments and EXS samples, try opening preferences>audio>advanced settings. Turn on the I/O safety buffer. Increase the I/O buffer size if necessary. You may be able to balance performance and latency. Multiple instances of the Space Designer plugin and ES2 synth tax the CPU. If you're using a lot of these in one patch, try eliminating a few.
    I would choose a MacBook Pro over a MacBook Air for Mainstage because it generally has a faster processor. The newer MacBook Pros are available with quad-core processors. If you want to upgrade to Mainstage 3 at some point, faster is definitely better.

  • Why does mainstage load every instrument for an entire concert at once?

    I have recently finished a UK tour using Mainstage at the centre of my keyboard rig and while I got through without any hitches, I had 30 songs to program in the run-up to the tour and almost all of them involved strings in some form or other (I use Omnisphere for this) - I ended up not being able to store them all in one master song list concert because the massive amount of memory needed by having 30 instances of Omnisphere meant that it would crash straight away. I got around it by splitting the list into two concerts but it was frustrating and slowed down the process of building sets for each gig while on tour. Also, this was a fairly simple tour to program for - if I did something else which was more intensive, I've no idea what I'd do!
    I know that in the West End they use Forte on their keys setups, and I am starting to see why....however, I love the interface of Mainstage (and the fact you can use it on a Mac!) and wish that Apple would address this issue asap! A setting that allowed you to choose whether to load the entire concert into memory on startup (a definite plus given the near-instantaneous patch change times if your Mac can handle it) or just to load one patch at a time would be great.
    Has anyone else found this to be a problem, and come up with any different workarounds? Is there anyone from Apple that checks these forums who could comment?
    Thanks
    Steve

    Thanks for the replies guys - seems this one is a bit of a contentious issue! In hindsight I could have used the string sounds at a higher level, although with most of the songs there were tweaks made to the patch because I was blending the Omnisphere with a rack Motif ES module in varying degrees as the song required. I will investigate aliases also - I was unaware of these!
    But I still stand by my original point, because it limits the possibilities of using Mainstage as a database of songs e.g. for a job where you have a lot of songs in the repertoire and will be creating a different set from these for most gigs. As I mentioned, it became impossible to open the master song list and transfer songs one by one to another Concert.
    And with the comment about 64 bit making the problem disappear....well, yes but that seems a bit ridiculous that all the powerful Macs around at the moment (mine being a top-spec late 2009 15" MacBook Pro) will have to 'lump it' with 'only' the 4GB available to them!! It should be plenty equipped to handle what I throw at it, and in the case that there are a lot of memory (or CPU) intensive plugins there should be the choice of whether to have the entire concert / set / song loaded into memory on startup.
    Again, I'd refer back to Brainspawn Forte, which seems like 'the' choice for most keyboard players and show programmers. There is minimal load lag, even when loading up very complex patches that in Mainstage's current form would have it eating up resources and crashing! I'm going to reluctantly investigate using Forte within Boot Camp, but still hoping that eventually Mainstage will mature into an even more flexible and intuitive program for live work - it has a great interface!

  • MainStage 2.2.2 released

    MainStage 2.2.2: Release notes
    Products Affected
    MainStage 2.2
    Symptoms
    MainStage 2.2.2 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.
    Resolution
    About the MainStage 2.2.2 Update
    Stability and Usability
    Resolves an issue in which MainStage might quit unexpectedly on OS X Lion v10.7.4.
    Resolves an issue in which MainStage sometimes quit unexpectedly when loading certain concerts.
    Resolves an issue in which MainStage quit unexpectedly when a second mapping was assigned to a screen control that already had a mapping assigned.
    Fixes an issue in MainStage 2.2.1 in which assignments and mappings could be inadvertently deleted by removing a screen control in Layout Mode.
    Resolves an issue related to the download and installation of basic and additional content.
    The menu item for Release Notes now opens the correct URL.
    Compatibility
    Compatibility with the VAX-77 keyboard is improved.
    Resolves an issue in which patch lists were not updated to VAX and Axiom keyboards if the keyboard lost and then regained connection to the computer after launching MainStage
    General
    Resolves an issue with MainStage 2.2 and 2.2.1 in which EXS instrument files were not available if they were in aliased folders.
    Fixes an issue in MainStage 2.2 and 2.2.1 in which the I/O Plug-in did not route audio to outputs.
    When mapping a Screen Control to a parameter already mapped to another Screen Control by using the plug-in GUI, MainStage now correctly maintains independent mappings for each Screen Control.
    Resolves an issue in which using the Command key in conjunction with up and down arrows in Edit mode with Map Parameters enabled caused MainStage to assign the mappings to Next Patch and/or Previous Patch.
    Fixes an issue in MainStage 2.2 and 2.2.1 in which mapping a Screen Control to jump to a patch or a set no longer worked.
    Screen Controls mapped to more than one parameter now operate smoothly over their entire range with all range scale settings.

    Grabbed MS 2.2.2 last night, loaded, started and promptly crashed. Switched to 64 bit mode and it runs but my 32 bit plug ins (inc apple plug ins) dont work properly (causes crackles). Switched back to 32 bit mode and MS crashes after about 30 secs with no action on my part. I've looked for any special instructions concerning 2.2.2 but have not found any. Has anyone else out there used 2.2.2 yet in 32 bit mode?

Maybe you are looking for