This isn't working, while MainStage 2.1.3, Logic 9.1.6, Live and every other program I have has no problem.
I've got a clean 64-bit MIDI driver setup, running on an octo Mac Pro, which is running a 64-bit kernel and running OS X 10.7.2. All the latest stuff and up-to-date.
I've spent a day and a half of my time trying to isolate what it might be which is causing this problem - but without knowing from Apple which requirements they've changed since the previous version, and also what in their requirements for MainStage is different than for Logic, I've got nowhere to go.
Seeing as "Bobfrompowell" is also having a problem (although I don't know if it's the same problem, on the surface it manifests itself the same)... I'm not alone in this...
I'm a pretty good reference for MainStage - I've gone out in front of thousands with just controllers, a MBP and everything I can throw at MainStage.
Essentially, I'll continue with v2.1.3, *still* hold off on buying an i7-based MBP until there's a version of MainStage that will work with it.
And, I still consider it really bad from a Customer Sat point of view that the EVB3 sustain pedal fix never came out in a Software Update release, even though Logic got this bug fix months ago. The point of MainStage was to be able to take your Logic instruments and reproduce what you did in Logic *live* in MainStage... If you use the EVB3, it hasn't been that way for months...
If anyone from Apple's MainStage team wishes to contact me directly, I'll be happy to provide details of what's happening here.
since MainStage hangs *before* it ever gets around to loading a concert, I never see a loaded concert window...
I restarted the machine while MainStage was hung, and on Lion, I always uncheck the checkbox to reopen all open windows when restarted, only this time I left it on...
I force quit MainStage and my Mac restarted...
I about fell out of my chair as when the Mac restarted, it did so with a MainStage concert file open!!! In the background, I saw the usual MainStage startup banner, and sure enough... it hung as it always does... but...
this simply CAN'T be the expected behavior of this release...
Look, if anyone has v2.2 and it all works good for you, be happy - it might be luck...
Now if only there was a way in the Mac App Store to clean install version 2.2 instead of having it upgrade... yep, can't do it... App Store says MainStage is installed, even after I trash it...
I'm the guy who doesn't have the MIDISPORT.
what is "USB MIDI compliant"? do you mean "class compliant USB"?
there has *never* been a requirement for MainStage for MIDI controllers to only work "driverless". that's just absurd and completely blows the architectured design of CoreMIDI.
please don't suggest there's a requirement which doesn't really exist...
I have controllers here that require no drivers... heck, I even removed any MIDI drivers on my system...
MainStage v2.2 still hangs.
thanks for trying to help though
the feedback page bombed out with an error message when I entered this information... there's also no way to attach/upload the dump file to the feedback.
I want a place where I can do a *real* incident/problem/bug report.
we don't have Apple stores here in The Netherlands... I'd be all over this at a Genius bar otherwise...
and yes, it starts when nothing is attached to this machine. *Sometimes* it starts when some, or even all MIDI devices are connected, but that wasn't more than twice in the 50+ attempts... From a troubleshooting point of view, it would have been better if it had of course, never started in the complete config...
if I start MainStage v2.1.3 first, leave it started without loading a concert, and *then* start up MainStage 2.2, the new version of MainStage starts.
I can close v2.1.3, and v2.2 still runs.
If I close v2.2 and then try to restart it (without first having 2.1.3 running), it hangs as described earlier.
There's nothing in the console log that explains this.
Apple, pls have a look.
could you be more specific?
1. which MIDI devices are connected? Which drivers are you using (if any are required)?
2. Does either of the workarounds work for you? (in my case, as long as a MOTU MTP AV is on - MS beachballs right away)
3. what, if any messages are you seeing in the console window?
4. what's your machine hardware / version OS X?
Apple will want you to create a support profile from within MainStage. I'm assuming you have either saved version 2.1.3 or restored from a backup or TimeMachine so you at least can fall back to that? You can create a support profile from there.
They also wanted spindumps and crashlogs if available (these are all visiible in the console). I had a peek at these and the support profiles. Seems like MainStage is well instrumented so that Apple should be able to resolve this remotely.
Once you've got this all ready - I'll point the guy @ Apple who contacted me to pick up your information as well.
I'm glad that Apple has contacted me - but I don't have a solution from the yet. But... they've got from me what they need.