mainstage 3.6 crashes opening a concert

I also have a lot of concerts that crashes Mainstage instantly on load. Some of my very old concerts don't crash on load, however.

Rolling back to Mainstage version 3.5.3 from my TimeMachine backup fixed the issue. Seems that version 3.6 has way more bugs than any previous version of Mainstage I have seen.

One temporary work around that I have found, is to open the default concert... and then after it opens successfully, in the "Open Recent" tab choose your desired concert and it should open that way for now. It's how I have gotten around a lot of previous crashing issues. Sometimes you have to do it a few times until it finally stays. Hopefully an update to the utterly destructive 3.6 update will come soon and fix a lot of the software-breaking issues it created.

... also, I've just had success in pulling the app bundle out of time machine (ver 3.5.3), it works fine sitting in the applications folder alongside the latest version (3.6). Thanks to the people above in the thread who suggested this.

I had this happening as a result IK's Hammond Plugin. Now it says failed validation if I try and enable it.

I am also having crashes when loading concerts. Doesnt seem to make a difference if its an older one or one I created in 3.6. I have rolled back until they release a fix.

Same thing here - my larger and more complex concerts created in earlier versions crash when opened in 3.6. I can't make any sense of the error log and it doesn't seem to be a particular plugin (my main setup uses primarily Kontakt, Massive X, Omnisphere, Serum, Alchemy, Massive spread over ~15 patches, which has never been a problem until now).

This is on macos 12.2.1 (2019 MBP, i9), everything fully patched and updated.

I find it incredibly ironic that Apple’s position with situations like this forces people into exploring illegitimate means just so they can get Apple’s software working again….which only “broke” due to an offical Apple update. This (still) blows my mind, and I’ve been using MainStage for just over 15 years.

FWIW, I don’t support illegitimate software but this option has saved many of my friends and colleagues after they’ve manually or automatically updated without having taken precautions.

For future readers of this thread: if you copy and paste the MainStage app and then rename it (e.g. MainStage “x.x.x”), you can update the default MainStage installation and still retain the full use of the copied/renamed version of MainStage i.e. you will then have - and can use - multiple versions of MS on your system. Of course, in addition, ALWAYS back up each MS update so you have a safe copy to revert to should the need arise.

I’ve been doing the copy/paste/rename thing for 15 years and it has always worked perfectly and safely. No need to have Time Machine just for this specific purpose….you simply need to be aware and careful. PLUS, never EVER allow your Mac to automatically update ANYTHING, including macOS!!!

Hello,

Same problem for me with the new version. Even with a fresh new concert... The new version is buggy!

I don't have a proper backup of my previous version of Mainstage. Just waiting for a fix... Very frustrating

I received a reply to my bug report on this issue, and sent them an example concert that was crashing as well as some other support info - so it appears that the dev team are aware of this and working on it.

(The feedback page is here: Feedback - MainStage - Apple)

How do you do that , I have the exact same problem and a gig in two days ;(

Is anyone willing to share a copy of 3.5.3 with me? I don't have a backup of the program itself. I've learned my lesson on that front. I would greatly appreciate it.

I have the same problem. Really frustrating. Is there a way to revert back to older version without having it on TimeMachine?

No. Without a backup, there is no legal way to do it. Despite all the issues many people are having with this release, that's the position.