Skip navigation

MainStage 2.2.2 Stability for live

746 Views 9 Replies Latest reply: Mar 23, 2013 3:06 AM by JazzupMT RSS
tony8028 Calculating status...
Currently Being Moderated
Mar 10, 2013 4:13 PM

Hey Guys


I am making the transition from Reason to Mainstage for live use. My set up is based 100% on my DAW applications - no hardware at all other than the keyboard I use to trigger the sounds.


Up until now I have used Reason which is absolutely rock solid - I dont think it has ever crashed on me. The big down side is that I can only use Reason sounds, no VSTs etc PLUS the interface is not very good for live- in fact its terrible. You cant construct a set list, you bascially have to scroll through tracks of songs to pull up the patches you need.


Anyway, have been playing around with Mainstage - upgraded my MBP to 16GB of RAM, went 64bit on my Mainstage app, purchased 2.2.2 and have started doing shows using MS as my DAW.


I must say I have had some hairy moments....MS seems to crash A LOT! I see the "Mainstage has quite unexpectadley" message at least once a day, especially when setting up sounds. When I play live it does seem more stable because I am not doing much other than playing the sounds - it seems to crash more during the set up process.


Are there any optimisation tips that will make my macbook pro more stable for MS?


My set up is:

Model Name:     MacBook Pro

  Model Identifier:     MacBookPro8,2

  Processor Name:     Intel Core i7

  Processor Speed:     2.4 GHz

  Number of Processors:     1

  Total Number of Cores:     4

  L2 Cache (per Core):     256 KB

  L3 Cache:     6 MB

  Memory:     16 GB


My audio box is a Native Instruments Kontrol 1


Thanks in advance!

Macbook Pro, Mac OS X (10.5.8)
  • Blueberry Level 4 Level 4 (2,825 points)
    Currently Being Moderated
    Mar 10, 2013 8:56 PM (in response to tony8028)

    Please post a crash log.

  • Blueberry Level 4 Level 4 (2,825 points)
    Currently Being Moderated
    Mar 10, 2013 9:05 PM (in response to tony8028)

    You have multiple concerts open at the same time?

  • Blueberry Level 4 Level 4 (2,825 points)
    Currently Being Moderated
    Mar 10, 2013 9:10 PM (in response to tony8028)

    That one is "easy": your concert file is defect.

  • JazzupMT Calculating status...
    Currently Being Moderated
    Mar 23, 2013 3:06 AM (in response to tony8028)

    Hi Tony



    Hi Tony


    I downgraded to 2.1.3 and since then I had no problem with crashing.  2.2.2 does not work well. Read my discussion below on how I downgraded.   Don't know why Mac is not doing anything with this.


    Good luck






    Re: cpu overload after upgrading to 2.2.2

    Nov 25, 2012 9:03 AM (in response to donmr)

    I had the same problem when upgrading to Ms 2.2.2 from 2.1.3.  Not only was I having CPU spike, I was having audio clipping when playing a soft sync (ie: omnisphere, east/west) making it impossible to play and to listen also.

    I revert to MS 2.1.3.   This is how I did this.


    I went  and download MS 2.1.3

    I deleted MS 2.2.2 with app cleaner ( a free soft to completely delete applications on Mac.  Just google it to find it, YouTube videos available to how to use it)

    I reinstall Logic Pro 9 so I can get MS 2.0.0 which comes with the logic pro 9 DVD

    Then I installed MS 2.1.3


    Only problem is that I had to redo all my MS concert. But worth it because I have no more CPU spike and audio clipping. And it working a lot better then before.


    Is apple doing anything about this?  Mine was a free upgrade, I can't imagine paying for this and resulting in bad performance




More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.