MainStage 3.7 released

New in MainStage 3.7


New Features and enhancements

  • Add the legendary sound of the Quantec QRS and Quantec Yardstick hardware reverbs— the most acoustically accurate room simulations ever created.
  • Use the ChromaGlow plug-in to apply rich saturation to any track with an advanced plug-in modeled from some of the world’s most sought-after professional audio gear.
  • Use Plug-in Search to find and add any plug-in directly from the plug-in menu.
  • Click on any plug-in slot in the Mixer while holding the command key to quickly remove plug-ins.
  • Download the new Modular Melodies sound pack and discover hundreds of loops crafted from patchable hardware synths, and a collection of meticulously designed Alchemy synth patches.
  • Download the all new producer pack from Pom Pom.


Stability and reliability

  • Importing a Patch from a different Concert that contains an instance of the Playback plug-in configured to "Start on Patch/Set Change" no longer causes MainStage to quit unexpectedly.
  • Swiping left or right in the Layer editor with a Magic Mouse no longer causes MainStage to quit unexpectedly.
  • MainStage no longer quits unexpectedly when opening the context menu for a Smart Control with VoiceOver enabled.
  • Resolves an issue where MainStage might quit unexpectedly when quickly loading Alchemy presets in the plug-in header using the arrow keys.
  • Navigating the text field in a Patch List using the VocieOver cursor no longer causes MainStage to quit unexpectedly.


Accessibility

  • VoiceOver can now be used to navigate the Mixer.


Mixer

  • The channel strip name no longer resets after adding or removing plug-ins.
  • Control-clicking a panner that has been previously set to "Stereo Pan" without selecting anything from the menu no longer changes it to "Stereo Balance."
  • While renaming channel strips, tab can now be used to select the next channel strip name.


Logic Remote

  • After choosing Quit and then cancelling in MainStage, Logic Remote no longer continues to show the message "Save the project in MainStage on your Mac before processing."


General

  • Selected Patches and Sets in the Patch List can be copied to the clipboard and pasted as plain text into any text editor. Text on the clipboard can also be pasted into the Patch List and names that match Patches in the Library will load and those that don't match will create empty Patches.
  • MainStage now exits full screen mode when closing the app.
  • The Program Change section of Patch Attributes now shows values of 0-127 when MIDI Settings is configured to display program changes with a range of 0-127.
  • Pressing Fn (Function) or the Globe key + F on your keyboard now toggles full-screen mode.
  • Patches generate sound as expected after changing the sample rate using Audio MIDI Setup. 

Posted on Jan 30, 2025 11:26 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 6, 2025 3:35 AM

I can confirm a problem with 3.7 where I can't change the output sound interface. At my gig I have a MOTU M4 via USBC. It shows up but when selected the sound keeps playing through the original sound interface (MBP speakers). Opening the audio settings window reveals that "MacBook Pro Speakers" is still shown as the sound interface.


At home I was unable to change my concert to any different sound interface. Serious bug here - maybe it's just with opening previous concerts - I reverted back to 3.6.6, was happy I backed it up to another folder or the gig would have been ruined.


I'll have to keep an eye out for the next update.

19 replies
Sort By: 
Question marked as Top-ranking reply

Feb 6, 2025 3:35 AM in response to mfritze

I can confirm a problem with 3.7 where I can't change the output sound interface. At my gig I have a MOTU M4 via USBC. It shows up but when selected the sound keeps playing through the original sound interface (MBP speakers). Opening the audio settings window reveals that "MacBook Pro Speakers" is still shown as the sound interface.


At home I was unable to change my concert to any different sound interface. Serious bug here - maybe it's just with opening previous concerts - I reverted back to 3.6.6, was happy I backed it up to another folder or the gig would have been ruined.


I'll have to keep an eye out for the next update.

Reply

Jan 31, 2025 1:55 AM in response to mfritze

I just installed the MainStage 3.7 update.


In the Toolbar, the "CPU" and "Memory" sections of the Meter are no longer showing. The control to switch these on used to be in MainStage->Preferences->General in the Display Tab, but in 3.7, MainStage->Settings->General has no Display tab.


Have the "CPU" and "Memory" meter's been removed from MainStage 3.7? These are crucial tools when work with large MainStage concert files containing multiple instruments.


Reply

Jan 31, 2025 5:02 AM in response to mfritze

Yes, but having CPU and Memory usage meters in the MainStage Meter control is very useful, we appear to have lost something important in moving to 3.7. Besides the "Activity Monitor" will look like a massive spreadsheet to most users, better showing a summary inside the MainStage window.

Reply

Feb 6, 2025 11:50 AM in response to Morwick

I concur, this is an actual issue (not recognizing interface outputs), and a biggie at that. Users, please be sure to back up your current version of MainStage BEFORE updating to the new version as you will otherwise have no way to revert to a working version. MainStage Team, please bump this up the list of things to address and fix. Thanks!

Reply

Feb 8, 2025 8:32 AM in response to mfritze

The solution for now is:

In macOS's System Settings in Sound tab choose (as output) audio interface you want to use with MainStage. Go back to MainStage and set desired interface or "System Settings" in Audio tab. Works for me.


Another words, you have to set audio interface in system settings to use it with MainStage :)

Reply

Feb 12, 2025 7:26 AM in response to glenn729

FYI: the CPU meter and the memory meter were no longer accurate since Apple Silicon came out and Audio Units were moved into a separate process.


I noticed that by looking at the memory usage via Activity Monitor vs. what MainStage reported. The CPU is in a similar situation: the all big plugins (Kontakt, Omnisphere, etc) can't be measured reliably – I think they are just too complex.


I think that is the reason why it was removed.

Reply

Feb 16, 2025 7:05 AM in response to Morwick

Same issue for me using a universal audio at home and Focusrite at church. What worked for me was to unplug the audio interface while MainStage concert was open and then plug it in again. A pop up asking to use the interface shows up and I select use. This worked for me, hope a fix is on the way soon.

Reply

MainStage 3.7 released

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