Musical Stuff

Q: 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

Close

Q: MainStage 3.2 claiming concerts are corrupt

  • All replies
  • Helpful answers

first Previous Page 3 of 4 last Next
  • by Watto1000,

    Watto1000 Watto1000 Sep 6, 2015 3:13 PM in response to leedos
    Level 1 (0 points)
    Sep 6, 2015 3:13 PM in response to leedos

    Success! Thanks :-D

  • by Mac-nl,

    Mac-nl Mac-nl Sep 6, 2015 3:30 PM in response to leedos
    Level 1 (0 points)
    Sep 6, 2015 3:30 PM in response to leedos

    This also dient work for me.

     

    my problem was that i cloud load my old concert in MS2..

    but when i saved it... I cloudent load it again.

    (corupt file)

     

    what i did.. I made a new setup... And then coppied all my presets (seperate) into it..

    BUT i found out... That it went wrong with Some presets.. (Corupt file)

    so... Lot of work...

    then i desided to look at the wrong ones... And what was the case....

    all presets contraining aliassen (pointing to 1 instrument) went wrong.. So i deleted them...

    now iTS working..

     

    i Also had a problem with midiloops....

    BUt im not Shure iTS About MS3.2 of my fault.

     

    hope This is helPing for others...

  • by Mac-nl,

    Mac-nl Mac-nl Sep 7, 2015 10:45 AM in response to ap_nc
    Level 1 (0 points)
    Sep 7, 2015 10:45 AM in response to ap_nc


    I found out that my concert doesent load because of some paches are fuckedup.

    And always when it contains a alias (intrument that points to another preset).

    I made a new setup.. and copied my paches one by one..

    then i got the problem that it was very slow... and hanged all the time..

    but that was because of an IAC midi loop..

    Fixed that.. and now its working fine...

  • by mgrafton,

    mgrafton mgrafton Sep 7, 2015 4:41 PM in response to Musical Stuff
    Level 1 (0 points)
    Sep 7, 2015 4:41 PM in response to Musical Stuff

    I had the same problem. Foolishly I upgraded to MS 3.2 and didn't even think about testing it.  

     

    I was setting up on stage for a gig, I ended up going through previous concert files, found one that worked and got through the gig.

     

    I have resorted to rolling back to MS 3.1.1 as it has stood the test of time. I shall experiment with MS 3.2, but it has lost my trust already.

     

    I found that even working concert files, when saved and the reopened fail to open. So this is clearly a bug!!!

  • by Mac-nl,

    Mac-nl Mac-nl Sep 7, 2015 11:23 PM in response to mgrafton
    Level 1 (0 points)
    Sep 7, 2015 11:23 PM in response to mgrafton

    Did You use aliasses in the concerts that You use (the ones that dont work)???

  • by Musical Stuff,

    Musical Stuff Musical Stuff Sep 8, 2015 2:06 AM in response to rc tech
    Level 1 (0 points)
    Sep 8, 2015 2:06 AM in response to rc tech

    Many thanks RC Tech for looking at this. I'm waiting until after the weekend to look at this again, as we have a gig on Saturday and I don't want to take any risks in advance of that! I'm planning on upgrading my wife's laptop to 3.2 to enable me to investigate this further. I do have additional sound modules loaded and licensed (such as PianoTeq and Korg's M1 emulator), so unless there's a specific reason why they don't run under MainStage 3.2 (and the CoreAudio spec hasn't changed, so there shouldn't be...), then I'd be surprised if this were the issue. Anyway, I'll do some more experimenting once the gig is over, and then post the results here.

     

    Kind regards,

    Cameron

  • by rblino,

    rblino rblino Sep 8, 2015 9:26 PM in response to Musical Stuff
    Level 1 (0 points)
    Sep 8, 2015 9:26 PM in response to Musical Stuff

    I have this same problem... and a gig coming up on Saturday!

     

    One thing I have noticed (that wasn't mentioned in this thread) is that I can open my old concerts in 3.2 as long as my audio preferences are set to "Built-in Output" and "Built-in Microphone". As soon as I switch it to my "Universal Audio Apollo" interface everything breaks.

     

    I know this might not "technically" be an OK question to ask... but does anyone know where I can download 3.1.1? I'm kind of getting desperate here and I'm not encouraged by the fact that no one from Apple is replying to these threads...

     

    Any help would be appreciated.

  • by Musical Stuff,

    Musical Stuff Musical Stuff Sep 9, 2015 1:48 AM in response to rblino
    Level 1 (0 points)
    Sep 9, 2015 1:48 AM in response to rblino

    rblino, I've copied my MainStage 3.1.1 app to a folder in Google Drive. If you can give me your Google identity (e.g. gmail account) then I'll give you access to the folder; you may then be able to copy the application to your Applications folder. I can't guarantee this will work for you, but you might like to give it a try, given your gig on Saturday...?

  • by rblino,

    rblino rblino Sep 9, 2015 8:28 PM in response to Musical Stuff
    Level 1 (0 points)
    Sep 9, 2015 8:28 PM in response to Musical Stuff

    @Musical_Stuff,

     

    Thanks so much for the kind offer. Fortunately I was able to get 3.1.1 from my son's Mac

     

    Everything is working fine now. Can't believe I was stupid enough to upgrade... Very disappointed in @Apple.

     

    Thanks again!

  • by bwhli,

    bwhli bwhli Sep 18, 2015 1:39 AM in response to Musical Stuff
    Level 1 (5 points)
    Sep 18, 2015 1:39 AM in response to Musical Stuff

    There is obviously a bug, but rebuilding the concert from Concert.patch does seem to work...

  • by dougemery,

    dougemery dougemery Sep 18, 2015 1:48 AM in response to bwhli
    Level 1 (10 points)
    Sep 18, 2015 1:48 AM in response to bwhli

    Bwhli, only as long you aren't using aliases in any of your patches in the concert.

  • by SonicLandscape,

    SonicLandscape SonicLandscape Sep 20, 2015 12:05 PM in response to Musical Stuff
    Level 1 (0 points)
    Sep 20, 2015 12:05 PM in response to Musical Stuff

    If anyone is uploading or sharing MainStage concerts via dropbox, remember to ZIP them before uploading - the new version of MainStage is much fussier about the exact naming of files and folders inside the MainStage package. All of the corrupted files messages I've seen so far come from folders inside the MainStage package being renamed by uploading to dropbox (or box.net). ZIP them before uploading them, and their isn't a problem.

     

    -c

  • by Jeff Krueger,

    Jeff Krueger Jeff Krueger Sep 20, 2015 9:43 PM in response to dougemery
    Level 1 (5 points)
    Sep 20, 2015 9:43 PM in response to dougemery

    Today I ran into this problem and managed to narrow it down (at least in my case) to pasting multiple aliases to the same External Instrument channel strip. I filed a bug report with Apple with the following steps to reproduce:

     

    1. Create a new concert (I used the Keyboard Minimalist template)

    2. Delete the default patch

    3. Create a new patch containing an External Instrument channel strip

    4. Copy the new patch

    5. Paste as alias

    6. Paste as alias again

    7. Save the concert

    8. Close the concert

    9. Try to reopen the concert. Sometimes MainStage crashes and sometimes I get the error message "The document “Corruption Test #5” could not be opened. The file isn’t in the correct format."

     

    I was not able to reproduce the problem with Instrument, Audio or Aux channel strips. Hope you find this information helpful.

     

    ~jeff

  • by Vm0112,

    Vm0112 Vm0112 Sep 25, 2015 9:44 AM in response to Musical Stuff
    Level 1 (0 points)
    Sep 25, 2015 9:44 AM in response to Musical Stuff

    Quit MainStage and run this from the terminal: defaults delete com.apple.mainstage3.

     

    Reboot and see what happens. Worked for me.

  • by Blueberry,

    Blueberry Blueberry Sep 26, 2015 12:51 AM in response to Jeff Krueger
    Level 4 (2,944 points)
    Sep 26, 2015 12:51 AM in response to Jeff Krueger

    The issue with aliases seems to be fixed in 3.2.1

first Previous Page 3 of 4 last Next