MainStage 3.3 Upgrade CPU Meter

Hi, I run quite a few playback tracks in the live set for my band so naturally I keep an eye on CPU usage and to date have never had any problems, with the maximum levels being shown on the VU meter (mapped to CPU usage) of around 8%. Having recently upgraded to 3.3, I notice my VU meter now doesn't move above 1%, never, it's static. In Activity Monitor when running MainStage I'm seeing the system CPU usage run at around 2.75 - 3% which is still incredibly low... good news. My question is, is the new upgrade so vastly improved in terms of CPU impact or, could there be a glitch meaning the mapping of VU meters is no longer functioning properly, i.e. telling me the truth? Many thanks in advance for thoughts.

MacBook Pro, Mac OS X (10.7.2), 17" 2.33GHz 4GB RAM

Posted on Apr 16, 2017 1:38 AM

Reply
3 replies

Apr 16, 2017 5:59 AM in response to Living In A Box

In 3.3 I have noticed that while both the CPU meter assigned to the screen and the CPU meter in the toolbar seem to match up (see below, each showing about a 5% load) the CPU Load History, when run simultaneously, suggests that the meters are underreporting the CPU load. Notice in the screenshot below how the CPU Load History window shows a 10% CPU load vs 5% in the two meters. 3.3 does seem a lot better in avoiding memory spikes. I used to have to keep the "Display audio engine overload" box unchecked because it was triggering all the time. No more.

User uploaded file

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.3 Upgrade CPU Meter

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