Bugs/missing features in MainStage 3.1

I installed MainStage 3.1 a couple of days ago, and while I haven't had the opportunity to explore the new version very extensively, I have found a few annoying bugs and/or missing features. For me personally, probably the most annoying bug involves master mute. In v. 3.0.4, "M" muted/unmuted all audio from MainStage in Performance mode. Now, hitting M (or [CNTRL-M]; they both seem to be assigned to toggle master mute in keyboard shortcuts) just mutes and immediately unmutes (or vice versa, depending on the initial mute state) the audio in something like a tenth of a second. Has anyone else seen this behavior?


Also, running MainStage in Performance mode no longer seems to disable the screen saver. It's disconcerting to be in mid-performance and have the screensaver cut in. I looked around the interface to see if this was a preference somewhere, but couldn't find it.

iMac with Retina 5K display, OS X Yosemite (10.10.1)

Posted on Jan 23, 2015 9:02 AM

Reply
15 replies

Jan 24, 2015 12:46 AM in response to ericmurphysf

3.1 has completed screwed up a complex series of screen control mappings I've been using in concerts since v.1...they simply don't work properly anymore. As an example: I have a single audio input for my live sax playing with 3 different channel strips with separate settings for soprano, alto & tenor sax. I have screen controls that will solo one of these channel strips but mute the other two simultaneously...these no longer work. I also have screen controls for different delay values so I can simply click "Short", "Medium" or "Long" and the relevant delay value is changed...these no longer work. Of course, each of these screen controls also light up when activated (or muted) and none of the lights work anymore either. For me, this update ***** big-time.


I've sent Feedback to Apple but who knows what'll happen with this.


EDIT: Interesting that the word "s u c k s" above has been censored.

Jan 27, 2015 9:20 AM in response to lohogan

I wonder if this isn't another instance of commands (either from the computer keyboard or from a MIDI keyboard) being executed twice. Maybe you could try an experiment: try mapping a couple of drum buttons to move to the previous and next patches in a set or concert. See if, when you press one of the drum buttons, MainStage moves up or down two patches rather than one. I suspect what's happening is the buttons you have mapped are toggling on and then immediately off. This seems to happen with many, although not all, commands in MainStage 3.1. Muting from the "M" key on the keyboard is affected, but invoking the tuner by hitting the "T" key is not.

Jan 28, 2015 7:27 PM in response to thewildest

I have exactly the same issue as thewildest. I use MainStage for electric guitar. When I change patches in v3.1, there's a pause in switching over to the new patch. During that pause, there's some hissing or crackling, as well as some effects noise (from effects I don't use). After a few seconds, the patch changes over to the new patch. This makes MainStage 3.1 unusable for me. Version 3.0.4 didn't have this problem; it changed patches immediately and cleanly.


Another bug is that hitting "V" to toggle view plug-ins doesn't work. I can see the plug-in as long as I hold down the "V" key, but it disappears as soon as I release the key. Looks like it's doing the same thing with Master Mute (keyboard shortcut "M").


I too have the problem of the screensaver turning on while in performance mode. Obviously, this is a bug, and isn't supposed to happen. The workaround of turning off the screensaver temporarily would work if this was the only bug. Sadly, it's not.


I want to downgrade to 3.0.4 until an update is released, but that older version is no longer available on the Mac App Store. I have it in my Time Machine backup, but when I try to use it, the support files are missing (such as Apple Sound Library Layouts). I have a call in to the Pro Apps Team (which supports MainStage) to ask them where I can download a fresh copy of 3.0.4 again. When I speak with them, I'll reference this thread.


It's disappointing (and somewhat offensive) that an application labeled "Pro" (and supported by the "Pro Apps Team") would ship with bugs like these. My livelihood doesn't depend on this software, but I know people for whom it does. I hope they didn't upgrade yet.

Jan 31, 2015 7:30 PM in response to Madddcow

I spent a bit of time Friday on the phone with a very helpful Senior Advisor on Apple's "Professional Applications Team" (the group that supports Logic and MainStage). He and I discussed a few bugs, including the "M" and "V" keys not properly toggling Master Mute and Plug-Ins, respectively, Performance Mode not disabling the screensaver, and the noisy & lengthy patch changes. I also took the opportunity to reference this thread for examples of some of the issues we're experiencing.


The Senior Advisor was able to reproduce all but the last bug (he was in his office and didn't have an electric guitar and an audio interface handy). But he apparently shared the feedback with a MainStage software engineer, and confirmed that the development team is looking into the issues. He kindly offered to keep me in the loop regarding an update to 3.1.


He also helped me restore the prior version (3.0.4) from my Time Machine backup, so I'm back up and running until the update is released.


If you upgraded MainStage from 3.0.4 to 3.1 and are running into issues, consider reverting back to 3.0.4 until 3.1.1 is released. You'll need a Time Machine backup for this- Apple won't make 3.0.4 available for download again.


If you're a MainStage 3 user and haven't upgraded to 3.1 yet, I'd hold off until these bugs have been addressed.


If/when I learn more, I'll post it here.


Cheers.

Feb 4, 2015 7:23 PM in response to KOOLMIKKE

To restore version 3.0.4 from your Time Machine backup, you need to restore the both the application and the support files. Here's a step-by-step guide. It assumes you DO NOT have Apple's Logic DAW installed:


1. Rename the existing MainStage application to "MainStage 3.1" in your Applications folder.

2. Archive the existing Application Support folder (Macintosh HD/Library/Application Support/Logic). Right click on the folder and select "Compress Logic."

3. Delete the existing Macintosh HD/Library/Application Support/Logic folder, leaving only the archive you just created.

4. Launch Time Machine and restore the MainStage application (from your Applications folder).

5. Rename the MainStage application you just restored to "MainStage 3.0.4"

6. Using Time Machine, restore the application support folder (Macintosh HD/Library/Application Support/Logic).


When you launch MainStage 3.0.4, you should now have access to any concerts you created in that version. Note that version 3.0.4 will NOT open concerts created in 3.1.


Hope this helps.

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.

Bugs/missing features in MainStage 3.1

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