mainstage 2.2.1 and MAC OSX Lion update 10.7.4 CRASH!

There are some tips in this thread, like removing a toolbar object:

https://discussions.apple.com/thread/3960938

Hi

having same issue, saw a post about hiding the MS toolbar. Tried it last night, ran okay (other than two patches changing by themselves while playing) with bar hidden and crashed each time I 'unhid' the bar. Will continue putting MS through its paces tonite. Hope this helps.

This is scary! this means I can't update Lion anymore...

Hope they find the solution quickly!!!

Wanted to say thanks! Hiding toolbar worked for me as well, one day STRESS, but thanks to you all it resolved the problem!

Greetings from holland

Unfortunately I have done all these suggestions and can no longer even launch Mainstage. Set it to 64 bit; removed Activity window from toolbar and when I launch MS the interface opens for a few seconds and crashes - EVERY TIME! This is completely unacceptable. Any other suggestions? BTW, I am currently searching fro my copy of Lion to do a clean OS reinstall but that is such a bogus option to Apple users.

Chris

Hiding toolbar did not work for me. I'm using 2.1.3, really hope this issue gets solved ASAP as we're all relying on it onstage!!

You won't like the answer, because they fixed the issue with 2.2.2. Unfortunately, you'll have to pay 30$ for it

Busterkubrick, you're right on both fronts.

1) I don't like the answer at all

2) Problem solved with 2.1.3 crashing: buy the upgrade to 2.2.2 (as of today 6/22/12)

On a side note, it boils my blood that Apple is squirreling us out of $30.

On one hand, this is wonderful for people who are new to Mainstage as it only costs $30 to get an awesome program...

For existing users like us it feels pretty crumby to be forced into buying something that gives you NO NEW FEATURES at all. It just works again. That's it.

Am I totally off base here? Or was this a straight up money grab for Apple?

For 2.1.3 users there are 3 options:

1. Upgrade to 2.2.2
2. Downgrade to 10.7.3
3. Wait till 10.7.5 or 10.8 is released, which probably fixes this issue

SmithBurg wrote:

For existing users like us it feels pretty crumby to be forced into buying something that gives you NO NEW FEATURES at all. It just works again. That's it.

MainStage 2.2 actually has a bunch of new features and improvements:

• a new multi-threaded audio engine, which allows to use as many CPU cores as the Mac can provide
• an Assign & Map table, which gives a nice overview over all active mappings and allows to create assignments & mappings without using the layout mode. You can also create assignments without a screen control and - a very frequent request - block MIDI messages.
• many small things, like the option to send any MIDI file to external MIDI hardware on patch change; a larger UI font; the saved value for controls can be seen and altered; globally disable the feedback protection.
• The Mac App Store license allows you to install MainStage on any Mac you "control", not just one desktop and one laptop.

2.2.2 also seem to have retina support in the workspace, which looks quite nice.

Fair enough regarding new features, albiet these small additions I seem to have no use for at the moment. I was able to map things fine before. And as for the new multi-threaded audio engine, the first single note I played using 2.2.2 gave me an overload warning. So far pretty unimpressed. Hopefully it grows on me and they continue to support it and weed out the bugs frequently. Very nervous about its stability for upcoming shows.

Its disconcerting to say the least to see that last post by SmithBurg was one year ago. Disconcerting because there didnt appear to be a clear cut solution to an issue that seems to be happening to many users in that for whatever user's MS setups were doing at the time, the end result is that the program quits "unexpectantly" during a show.

I had been using MS originally on a late 2009 MB pro, and as my patches evolved, I started having several issues which would quit MS.

I did find what seemed to be a solution by reinstalling the OS to 10.6.8, and and new "unclogged" system seemed to fix the issue. HOWEVER....a few months later and it "quit unexpectantly" in the middle of a show, or I couldnt get my focusrite scarlet 8i6 inteface to work in preferences...(had to use the MB pro minijack out!! Which was very noisy with the power supply and I do NEED the power supply for a 4 hour show (that old banana)

I digress......

So, i think my laptop has had its day with all the issues id been having, and I go out 2 months ago and buy Apple's flagship macbook pro for $4200, with the idea that the ultra high specs of the laptop should do the trick.

MS reinstalled....I dont use 3rd party plugs as im content with MS sounds, (although i did install kontact to try out and it was far too memory intensive, so dont actually use it.

So for 1 month I play various shows with no issues. I have not changes the setup at all EXCEPT adding one patch that I made.

Then one gig last month it happens again. I'm flabbergasted now. "MS quit unexpectantly" but I DONT have wi-fi connected at the random venue, and CANT send apple the error report.

My only choice is to reboot and attempt to get the flow of the show back up again. Thus loosing the error report.

I NEED a solution, and I cant understand what the error report is even saying.

SPENDING $4200 on a new laptop, and if i had hair, I'd be pulliing it out.SHOULD I HAVE GONE HARDWARE INSTEAD? I know MS now, SO used to it, and i love MS far too much if only it worked for more than 5 seconds.

PLEASE APPLE HELPPPPPPPP!

or any kind users out there with some kinda fault finding knowledge

You are clearly having a different problem. Please post a crash log.

BTW: you are not running out of memory, right? Do you use MainStage in 64-bit?

Also, I would like to add that the decision to use MS instead of a hardware setup from the START has had a real cost to it. NOTE that I am a bass player who decided also play keys, and I, in NO way would have purchased all the gear below had I had not made the decision.

To be fair, I already owned the first laptop...

Novation nocturn 49 midi controller $400

then upgraded to a Akai MAX49 midi controller $800

Focusrite Scarlett 8i6 Audio interface $500

A keyboard stand $ 69

Heavy duty Roadcase $500

Laptop bracket $100

first gigging Macbook pro $2000

New 2013 Macbook pro retina $4200

ATH-M50 Audio Teachica headphones $250

Necessary leads around $200

BSS Di box $200

memory stick to transfer patch files $40

Hard drive to backup the setup $100

Spare laptop power supply around $90

Volume pedal $50

Sustain pedal $30

Sub Total $9529

I am aware that owning a laptop that is used for emailing, invoicing for gigs, and watching the ocassional youtube link means that it isnt 100% used for my live work, but is a SMALL percentage, so knock a thousand bucks off for that just to be picky.

Even $8529 seems excessive to think that i:

1. DONT have a stable reliable setup.

2. Right now, MS quits far too much to allow it back in the live show.

Annoyed doesnt cover it. I just want a solution.

Please, anyone?

Hi Blueberry! After my 2nd rant, i noticed your post. Thanks for being so quick!

I tried 64 bit mode on the 2009 MBPRO when I started having crashing/memory/quiting issues. It would quit immediately after the UI came up. And yes, i constantly had memory issues maxing out. Even assigned a panic button to my midi controller, but freezing was a biggy there. I did only have 4Gig Ram on that machine, but after reading other users posts on various sites i was convinced it wasnt going to fix the issuen and apprehensive throwing money that way.

So, I get the new machine, and it worked fine with no serious issues for the first month, maybe only 4 gigs or so that month, so I didnt see any need to run it in 64 bit.

So, when I started having issues with my new laptop, i tried 64 bit mode, but it crashed/wouldnt load/took ages to change patches, but inveriably would quit with an error 20 secs to 1 minute after the UI comes up.

I will try to provide a error report in this forum next time it does it.

Wont be long! I promise! haha

Thanks again for your reply.