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