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

rc tech

Level 2

240 points

Sep 1, 2015 1:23 PM in response to rc tech

Musical Stuff: if it's an audio unit problem this probably doesn't help until you disable the problematic audio unit, but I saved a copy of the concert in 3.2 after opening it. You can get it at https://drive.google.com/file/d/0B1zdTZifheJgU3JqMVFDTEZVdFE/view?usp=sharing

ap_nc: Maybe your concert has a different problem... if you can post it somewhere i would be happy to take a look.

ap_nc

Level 1

24 points

Sep 1, 2015 2:06 PM in response to rc tech

I have found a way to fix whatever 3.2 doesn't like when opening files.

Copy the concert. Open the copy in 3.1.1. Consolidate, Clean up, Save.

Then it opens in 3.2.

But now I can confirm what Authentic was saying about the Playback waveforms.

The Waveforms do not stick when you close and reopen 3.2.

lifenoise

Level 4

1,019 points

Sep 2, 2015 5:31 AM in response to ap_nc

I built a new template in MS 3.2 and imported my sets from 3.1 into it. So far, I've been able to save and reopen 3.2 concerts. If you have saved individual patches, you can load them from the patch list cog wheel>load patch/set. If not, create a new patch, then in patch settings select user patches>concert>set>patch to load them individually.

Sep 3, 2015 4:55 AM in response to ap_nc

Did not work for me.

Sep 3, 2015 6:38 AM in response to Authentic Identity

can apple let us down load 3.1.1 again , and up grade to 3,2 when its all fixed

ap_nc

Level 1

24 points

Sep 3, 2015 7:03 AM in response to MIDImogul

Darn.

Copying (copy to another folder, consolidate, cleanup) allowed me to open all my concerts.

The originals still give me the incorrect format error but the copies open.

I have a problem with waveform displays though.

My sets have approx 15 songs with playback at the song level.

I can go through all of the songs and get the waveforms to refresh by reselecting but when I close and reopen in 3.2 only the last waveform i touched before

saving is still showing. The rest are blank.

I created a test from scratch in 3.2 with nothing but 2 songs that only have a playback with a waveform display.

Same problem.

Yamansitar

If you have any sort of backup you can just copy the 3.1.1 app back into your applications folder.

Sep 3, 2015 8:16 AM in response to Musical Stuff

Same problems here. OSX10.10.5 > upgraded to MainStage 3.2. One more complex concert(routings +monitoring etc) won't load anymore. I opened the same concert in the same 3.2 MainStage in El Capitan (beta version) and?! Yes it opened and works as before. I've saved it in El Capitan. And tried to open it in 10.10.5 and it worked again as before..... For me this is the proof that there is something going wrong in the 'translation' to MainStage 3.2 in OS's before 10.11

Anyway this is a bug in 3.2 so Apple should fix this.....

leedos

Level 1

76 points

Sep 3, 2015 12:05 PM in response to Musical Stuff

Count me in. I upgraded to Mainstage 3.2 yesterday and I'm not able to open most of my concert files. Seems my basic ones work just fine. I restored from an older backup with the same result. I've already recreated my concert file once and it was very time consuming and don't want to go the route unless absolutely necessary. I can post my concert file if needed. I'm hoping for a solution, but will probably need to roll back to 3.1.x. for now. Thanks!

leon em

Level 1

44 points

Sep 3, 2015 12:49 PM in response to leedos

i had the same problem, I had the "wrong format" warning/error.

I fixed it by trashing the MainStage preferences.

rebooted

It then loaded my concerts again, and seems to be back to normal

Sep 3, 2015 1:18 PM in response to leon em

thanks bro ,,,, but how to trash MainStage preferences ??

I fixed it by trashing the MainStage preferences.

rebooted

It then loaded my concerts again, and seems to be back to normal

leon em

Level 1

44 points

Sep 3, 2015 1:24 PM in response to yamansitar

user > Library > Preferences >

trash

com.apple.mainstage3.LSSharedFileList.plist

com.apple.mainstage3.plist

reboot. Can't promise it will fix your problem but worked for me. You may need to show your user library

Select your home directory, then apple "J" (toolbar view- show view options), and select "show library".

leedos

Level 1

76 points

Sep 3, 2015 2:24 PM in response to yamansitar

From: MainStage 3: Troubleshooting basics - Apple Support

To reset your MainStage 3 user preference settings to their original state:

Quit MainStage 3 if it's open.
In the Finder, choose Go > Go to Folder from the menu.
Type: ~/Library/Preferences
Click the Go button.
Remove the com.apple.mainstage3.plist file from the Preferences folder.
Restart the computer.

I went ahead and renamed both com.apple.mainstage3.plist and also com.apple.mainstage3.LSSharedFileList.plist to test this out. Since I'm a bit impatient I skipped step 6. I opened my "corrupted" Concert file and I was able to open it without issue.This was the quick fix I was looking for!

Now I can start playing with integrating Alchemy into my concert!