Level 4

2,378 points

MainStage 3.2.2 cpu overload issue still exists

Hello,

does anybody notice a decrease of performance on 3.2.2?

Today, i installed the 3.2.2 update, and the first thing MainStage presented me was a CPU overload from a simple electric piano channelstrip.

I then tried the Alchemy, and it's gone from bad to worse. In 3.2.1, Alchemy would CPU spike for the first seconds and then settle down to a level where you could somehow use it.

In 3.2.2, Alchemy creates constant CPU spikes, so i cannot use it anymore.

And yes i have a newly bough 2015 Macbook Pro (the big one, dedicated graphics, evil performance).

MainStage is BUGGY. Worse than any other Apple program i ever used. I am seeking for a solution desperately, because i need MainStage to make music for a living.

Any solution deeply appreciated.

MacBook Pro, Mac OS X (10.6.7), 8GB, Logic Pro

Posted on Oct 23, 2015 12:18 AM

28 replies

ap_nc

Level 1

24 points

Oct 28, 2015 11:43 AM in response to Foxboy71

Have you tried running MS in low resolution (checkbox in get info) or trying different screen resolutions.

Screen resolution seems to have a big impact on CPU for me.

Without low res checked my cpu is much worse in 1280 x 800 than it is in 1650 x 1050.

Foxboy71 Author

Level 4

2,378 points

Oct 28, 2015 3:43 PM in response to ap_nc

Thank you for the idea.

It may have a small impact, but i still get CPU overloads at 128 samples running Alchemy default preset. Could see no measurable change.

And ugh is this ugly! 🙂

Oct 29, 2015 7:39 AM in response to Foxboy71

try running Performance mode in a window rather than maximized. Then reduce the window size a bit. Myself and users on another forum have reported positive results from doing this. I realize this is just a workaround but I, like yourself, need to us this software professionally as I have previous versions. The bottom line is that it used to work great and after the update it does not. reliability is a must in a live situation.

Foxboy71 Author

Level 4

2,378 points

Oct 29, 2015 7:40 AM in response to daFrimpster

Thanks, good idea. Maybe this will help.

However, i need performance full screen because i have my chord sheets in the mainstage window. Meh. Will try to find a workaround

Anyway thanks.

kaurkenk

Level 1

0 points

Oct 29, 2015 10:46 AM in response to Foxboy71

I found out that there is feedback detection running in the background all the time, even if it is disabled in the preferences. For me it consumes over 60% of CPU constantly. I does the same when I make new project. When I close CPU load history, then the main CPU monitor looks okay. There was a thread somewhere where apple had instructions to fix this problem, but none of them helped. So do not update to latest version. I will try to download previous version somewhere, this was okay.

ap_nc

Level 1

24 points

Oct 29, 2015 11:24 AM in response to kaurkenk

Try clearing out your preferences and recheck disable global feedback protection when you redo your settings.

This worked for me.

It was not working properly before I dumped the old prefs.

ap_nc

Level 1

24 points

Oct 29, 2015 3:14 PM in response to daFrimpster

I think this is a graphics issue.

Different screen resolutions, different window sizes and running in low resolution all have an impact on cpu.

Foxboy71 Author

Level 4

2,378 points

Oct 29, 2015 2:51 PM in response to kaurkenk

that's actually the first thing i turned off. This happens without feedback detection, too. It's not the solution, though it had some impact on my old 2011 Macbook Pro.

Foxboy71 Author

Level 4

2,378 points

Oct 29, 2015 2:56 PM in response to ap_nc

Didn't work for me. In fact, i was working with a very fresh installment of MainStage because my old Macbook had an error, so i installed it on a brand new machine from scratch. I also took care not to overload the system and keep it all smooth + clean to be optimized for audio.

Sorry, preferences is not the answer.

Foxboy71 Author

Level 4

2,378 points

Oct 29, 2015 2:59 PM in response to ap_nc

...aaaand i also tried the graphics. Many many many changes in resolution like suggested before.

Still not a chance.

Guys: To reproduce the error please try the following setup:

128 samples I/O buffer (without extra security buffer).

Load factory preset "keyboard minimalist".

Replace Electric piano Plugin with Alchemy (default preset)

make some glissandos over the on-screen keyboard with the mouse. Sometimes you don't even need that. The first single tone sends CPU through the roof sometimes.

ap_nc

Level 1

24 points

Oct 29, 2015 3:11 PM in response to Foxboy71

Reproduced here the same.

Alchemy does seem to have serious some cpu hogging issues.

Loaded EXS, EFM and a couple others and no similar problem.

Actually the prefs clearing was for the feedback protection issue kaurkenk was having.

Foxboy71 Author

Level 4

2,378 points

Oct 29, 2015 3:12 PM in response to Foxboy71

Okay guys, for all who are still following this issue:

I have found a method to reduce the average CPU load from about 75% to about 65%, and get rid of most of the more nasty spikes as well. It's not all gone but has improved dramatically, and i could clearly measure it with the CPU monitor. It's also reproducible so you might want to test it yourself.

This only applies to the Macbook Pro with a dedicated graphics card. You have to go to the system preferences ➜ energy saving ➜ disable automatic switching of graphic modes. (This means your computer will run using the dedicated graphic card at all times).

moscheja

Level 1

11 points

Sep 19, 2016 11:08 AM in response to Blueberry

No it isn't I have a iMac with the best CPU and power, CPU view shows a maximum of 25 % load, but nevertheless Mainstage shows 'Overload Messages', it muts be a bug in Mainstage !

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 cpu overload issue still exists