MainStage 3.2.2 & GarageBand 10.1.0 Issues

I've been having the same problems as many others with MainStage 3, so I have eagerly awaited Apple's attempts to repair what they destroyed. Update 3.2.1 failed to address any of my issues, so I awaited update 3.2.2. Having now installed that update I can now report that, although I can now open Apple's factory default Concerts (which were considered the wrong format by version 3.2.1), it has created larger problems. Not only has it trashed the Concert I was working on (it now hangs up when trying to open the Concert created with version 3.2.1 and saved under version 3.2.2), but now GarageBand refuses to stop loading the MIDI file I had opened from within that MainStage Concert (using Script Editor).


I have removed all of the relevant Preference files for MainStage and GarageBand, repaired disk permissions, restarted the computer, all to no avail. I am now going to reload an older copies of MainStage, GarageBand and the Concert I was working on. I can't believe how badly Apple has screwed up this, once reliable, product. Maybe version 3.2.3 will work...or maybe I should wait for version 4...


If anyone has any other suggestions on how to resolve these issues, or where I should go from here, I'd welcome hearing them.

MacBook Pro (Retina, 15-inch, Mid 2015), OS X Yosemite (10.10.5), MainStage 3.2.2 & GarageBand 10.1.0

Posted on Oct 22, 2015 11:12 PM

Reply
8 replies

Oct 23, 2015 6:15 PM in response to rc tech

I'm triggering a GarageBand MIDI file from within MainStage. I've got a button mapped to an Apple Script that launches GarageBand, opens a specific MIDI file, triggers Play, and then returns me to MainStage. Everything worked fine until I updated to MainStage 3.2.2. When It began refusing to open the Concert I was working on, GarageBand also started Automatically opening the last MIDI file I was working on within that Concert. Now, whenever I try to open GarageBand, it opens that same file. If I move that file into the trash, it opens another file from the list of recently opened files. If I clear the recent file history, Garageband recreates it and opens one of those same files. It also requires me to use Force Quit to close it.


I've gone back to MainStage version 3.2.1 and I can now open some of my old concerts again, but not all of them. I've also deleted all of the Playback files that I was running within my concerts (in favor of the MIDI files). However, now I'm getting CPU Overload messages every couple of minutes. I'm running all of this on a mid-2015 MacBook Pro, so CPU capabilities should not be an issue.


Does this clarify things? I'm not convinced that the GarageBand issue was caused by MainStage, but the unstable nature of MainStage suggests they might be related. Having to force close MainStage every time it hangs up trying to open a concert can't be good for other open audio applications.

Oct 23, 2015 10:12 PM in response to EMWds

Yeah, the lack of a MIDI sequencer implementation makes life hard in MainStage compared to able*cough*ton.

I also have a mid 2015 MB Pro. It's simply ridiculous that even a most basic standard template - stock MainStage template!! - fires my CPU through the roof. There's something horribly wrong with the whole MainStage/Core Audio system.


If anyone knows a good answer i would really appreciate it. It's a shame apple doesn't interact with users in this forum. I hope they at least read it.


You should also file a MainStage feedback support form from within the file menu, or here: http://www.apple.com/feedback

Nov 13, 2015 1:40 AM in response to EMWds

Hi all, is there news from Apple ? I'm still "freeze" in my 3.1.1 version (the only one that works - it could be better but ... stay indulgent in front of the incapacity of find solution from Apple - . I won't upgrade to ElCapitan (too risky).

do you have advice to find the same tool than Mainstage but on PC (Windows 7 to 10) ? (I don't know if Forte is still in dev. ). thanks in advance.

I will have a MacBook 2014 probably on sale (apparently it is not sufficient to run the ineptitude from Apple ...)

Nov 13, 2015 1:45 AM in response to Procman

Don't be too discouraged. There are workarounds for many issues. As for PC, you might want to try Ableton Live. It's a whole DAW, but it's intended to be used in a "live" situation (hence the name "baked" potato).


The 2014 Macbook will be able to run Mainstage if you can live with a 256 samples buffer setting. Also you have to set up your concerts in such a way that you don't load them up with tons of CPU-hungry plugins. But this is true for every DAW or live music app on the market.

Nov 13, 2015 1:57 AM in response to Foxboy71

Thank you Foxboy, I can live with a poor buffer because I only use external hardware. But I would like to run a Toontrack Superior -just a Kick + Snare + CH) and I dare not try (too afraid to have to goback with TimeMachine...). In short, I feel "blocked" with a "non professional / sure" software. It's not confortable. I hope the 3.2.3 will solve ALL the problems and maybe (I hope... I hope) it will be compatible with Yosemite (because too much problems semms to appears with audio plug-ins in ElCapitan to upgrade now).

I had a Mac for 10 years and switched to PC for 10years. I come back (2014) with a Mac and I ask myself to switch again ... very annoying :-/ Please APPLE: ACT !!!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MainStage 3.2.2 & GarageBand 10.1.0 Issues

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.