kengetz

Nice idea, but there are something like 150 patches in the concert, and the saving problem is intermittent -- happens around every other time I save. I can't believe there isn't a way to save the concert to a "text-based format", and then reimport it, or do some other diagnostics on it. How can there be a program that's used for live performance that has such a fragile file format, and that can't be resurrected on failure? This is unacceptable. A $500 waste of money. Thanks, though. - -Ken I had a similar problem and it drove me nuts. Assuming your concert loads ok (mine didn't) I'd suggest troubleshooting by removing your patches one by one to see if any of them are causing the problem.

Well, CPU is pegging (turns red, completely to the right on the meter) every time we switch a patch. The memory meter shows about 80%. It's a pretty big concert (over 150 individual patches with lots of layered instruments in each patch). We bought more RAM (should be arriving today) so hopefully will be better at 4GB. If not, I'll be back. Thanks -- Ken What is the memory and CPU display showing?

Also have another player with a recent MacBook Pro 13", and it contains 2GB memory. We get a serious delay when switching patches, and the CPU pegs. Could this be due to not having enough memory? Any suggestions on what would cause this delay?

Performing in a "broadway"-style pit, and have two concerts set up, one for each act of the show. I also have created concerts for the second keyboard. The other pianists' concerts work fine. No matter what machine I run this on, my two concerts seem "corrupted"--that is, Mainstage 2 crashes all the time. Most often, it crashes while saving changes, but it often crashes when I load one of the, and them press a note. If I then reload the concert, it works fine. Mainstage rarely crashes in Perform mode, only in edit mode. Any suggestions? Any way to resurrect a corrupted concert? Thanks -- ken