You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MainStage 3.2 claiming concerts are corrupt

I've been using 3.1.1 for a long time, in live gigs, very successfully, and today I was forced to download the 3.2 update (didn't know how at the time to turn this off - I think I've since found out how). When I ran it, it claimed all of my concerts were corrupted, and requested me to restore them from backups. This was bad advice, as they weren't corrupt, as I proved when I eventually managed to roll back to 3.1.1 using Time Machine, which then worked perfectly with these concerts. So there appears to be some incompatibility in file formats (not backwardly compatible) between 3.1.1 and 3.2. This is a major problem for me, and makes 3.2 unuseable for me, as it can't read my concerts that I've built in 3.1.1.

So my questions are:

(a) is there some way of getting MainStage 3.2 to accept concert files generated by 3.1.1, possibly by running some kind of upgrade utility on them?

(b) If the answer to (a) is no, then are there any plans to provide one in the future, or alternatively to patch 3.2 so that it can read concert files from 3.1.1?

Until this evening I'd been incredibly impressed with the power of MainStage, having used it successfully to process sound for multiple keyboards and guitars in gigs. It feels like this hasn't been tested properly, which is a real shame; I'd like to use the new features like Alchemy but I can't without rebuilding my entire set list from scratch, and that is not going to happen.

I don't think it's relevant, but following the guidelines, I'm using:

Yosemite 10.10.5 (completely up to date I think)

Model Name: MacBook Pro, 15 inch, mid-2014

Model Identifier: MacBookPro11,3

Processor Name: Intel Core i7

Processor Speed: 2.5 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 16 GB

Boot ROM Version: MBP112.0138.B15

SMC Version (system): 2.19f12

- Cameron

MainStage, OS X Yosemite (10.10.5), MainStage 3.2

Posted on Aug 28, 2015 2:34 PM

Top-ranking reply

Authentic Identity

Level 1

69 points

Posted on Aug 29, 2015 8:17 AM

Yeah...I was dumb and upgraded when I know better...

It's loading concerts from 3.1.1 for me...but it will not retain my Lyrics/chords in the text window, and it won't retain the Waveform's association with the playback plugins. I had over 100 patches with lyrics typed into each one that was being automated by Logic. e

All of those patches are now blank. I've retyped them in, saved and backed them up...nothing.

View in context

53 replies

Nomad_76

Level 1

10 points

Sep 26, 2015 7:14 PM in response to Musical Stuff

I can't believe I noobed, and fell for the update!

Deleting the preferences did not work for me.

Making a copy of the concert did not work of me.

HOWEVER: I exported a copy of my layout when I first made it (I spent so much time on it I had to back it up). So I loaded the minmalist template. I then went into layout, and imported my layout. Next I loaded all my saved concert Sets. Everything worked great the first time. I even saved and reloaded with no problems.

So if you are lucky enough to have backed up your layout, just import it into a new concert and all works as it should..

Whew!....Dripping sweat, tears of agony now turned into tears of Joy!

~Nomad76~

CCTM

Level 6

13,147 points

Sep 27, 2015 4:34 AM in response to Nomad_76

Apparently the issues with older Concerts is fixed in v3.2.1

Resolves an issue which stopped some older concert files from opening in MainStage 3.2"

MainStage 3.2.1 release notes - Apple Support

CCT

Oct 10, 2015 12:31 PM in response to ap_nc

I did that "consolidate, clean up" trick and it seems to work just fine.

Procman

Level 1

29 points

Nov 13, 2015 1:46 AM in response to Musical Stuff

Since I tried the 3.2 update (and 3.1.1 go back ... and 3.2.1... and 3.1.1 return... and 3.2... STOP !!!) My MS doesn't open "byDefault" the last used Concert. and I can't setup it. Some "patch send doesn't work anymore (but not everytime)... ????!!!!

Do you have advice to find a competitor to MS but Windows platform ?

Dec 6, 2015 8:34 PM in response to Musical Stuff

It seems this is not simply a version to version issue. This is also happening with MainStage 3.2.2 opening MainStage 3.2.2. files. Every few days, I start everything up and open my main file to get to work and I'm greeted with MainStage reporting "The document “Example” could not be opened. The file isn’t in the correct format." It will not open at all. I'm forced to revert to a backup. I never had this problem prior to this last 3.2.2 update and now I'm collecting a graveyard of MainStage files that won't open.

This totally took me by surprise the other day at a rehearsal and I was dead in the water with no access to any of my sounds or setups. I had to rig up something temporary which wasn't even close. Extremely stressful. If this were to happen to someone on a gig and they didn't have a backup handy, they'd be toast!

Now I'm having to continually keep multiple backups after every change just to ensure I have a copy I can rely on. (It's a real pain 'cause these files are about 6GB each.) Unfortunately, I cannot depend on MainStage 3.2.2 reliably storing any of my work in a file. For a while, the files open fine—I work with them, edit, save, whatever—then all of sudden, they refuse to open. I can dissect the contents for a few things but I can't really get things back the way they were.

This is an extremely critical bug that needs to be tracked down and fixed immediately. I have lost many hours and even days of work to this problem.

I'm running Mac OS 10.5.5 on a brand new MBP 2.8 GHz Intel Core i7.

PLEASE FIX THIS!

Dec 7, 2015 10:31 AM in response to leedos

If this problem can be fixed by simply trashing a preference file, the developers have absolutely NO EXCUSE for taking over three months to fix this critical bug!!! How can this not be a priority?

Unfortunately, this is starting to look like a trend. It feels like Apple is all too comfortable alienating their most loyal professional users. Just ask the Final Cut Pro or Aperture users about the train wrecks they've had to dig out from in the last few years. Hopefully, the music and audio production products are not next.

Procman

Level 1

29 points

Dec 8, 2015 1:06 AM in response to videographics

I don't understand why Apple doesn't fix that problem and all the bugs since the 3.1.1 I'm looking to find a solution with Windows system (Forte 4) . I was on mac (10 years) and I switched (10 years), and now (come back to mac in 2014) I search to leave Apple because they consider their user like crap.

It's just a shame. Shame on Apple.I'm very angry😠

Apr 18, 2016 10:06 PM in response to Musical Stuff

I'm in too.

My 2.9gig concert file takes about 25 minutes to load - this has been steadily getting worse since v3.1.1 (I've been using MS since v2). In the concert are 216 stock patches, about 1/2 Untitled Patch, and I had 4 playbacks in the concert and pulled those because another thread said if the tempos didn't match perfectly it would make concerts load / save very slowly (saving takes about 11min). I have no idea if this issue is related to the above file load issues but something has clearly gone south with MS since 3.1.1.

I use this large concert, open it's open, to set the click for the band and voice keyboards. If anyone has suggestions on how to reduce this load/save time I'd love to hear 'em!

MS v3.2.4

8gig 13" retina MBP dual core running 10.11.4 on a 256gig SSD with about 40gig free

MainStage 3.2 claiming concerts are corrupt