Mainstage Optimization Advice

Question

Level 1

8 points

Mainstage Optimization Advice

I got a MacBook Pro today - 2.2ghz, 4GB RAM, 200GB 7200rpm HD.

I've been using Mainstage (1.0.2) with it, and I've found that a buffer of 128 is an ABSOLUTE minimum, so that I don't get constant dropouts/clicks. Ideally, it needs to be set to 256, but the latency isn't too good from there upwards, so I'm trying to keep it to 128 if at all possible.

But, I've only been doing 2 instruments layered - piano, strings, with a couple of plugins on each, and I have to be very careful how many notes I sustain etc., for fear of dropouts. The CPU meter is constantly above halfway even with simple playing, and often approaches 80%+.

Also, I loaded a Yamaha piano sample (included with Logic Studio) into the Explore/Instruments top piano, to replace the Bosendorfer (which plays fine at a medium buffer level), but the Yamaha refuses to play at all, even on the highest (unplayable) buffer setting. It stutters like crazy.

As my machine is high spec (full 4GB RAM, 7200rpm HD, 2.2ghz Intel Core 2 Duo), can someone please help me to optimize everything so that I'm not playing live with terrible latency, and so that I don't have to watch what I'm playing (and watch the CPU meter) all the time. Surely I should have enough power for just a standard set using Mainstage (just a couple of layered sounds at any one time - I'm not talking 20 instances of Sculpture here!).

Thanks for any help and advice anyone can give me.

Macbook Pro, Mac OS X (10.5.1)

Posted on Jan 28, 2008 5:49 PM

Reply

Answer 1

MarkW19 Author

Level 1

8 points

Jan 29, 2008 3:58 PM in response to MarkW19

Can anyone help?

I've played a lot with Mainstage today, and with most of the templates (RnB, Electronic etc.), MOST sounds are ok, BUT I do have to watch what I play/sustain, as the CPU meter is constantly over 70% for most sounds, even simple ones like grand piano etc.

But, these are just single sounds - like an organ, and it's almost going into the red all the time.

Surely, with a MacBook Pro with 4GB RAM, I shouldn't be having any issues at all with just single sounds?

Reply

Answer 2

Jan 29, 2008 5:27 PM in response to MarkW19

Make sure MainStage is the only application running. Then restart MainStage and see if the problem still occurrs. What is the average CPU usage with only MaInStage open running the concert in question?

Thanks.

Reply

Answer 3

MarkW19 Author

Level 1

8 points

Jan 29, 2008 7:14 PM in response to Sir Mixalot

Mainstage is always the only app running, and it's been restarted many times today and yesterday, it's always the same...

I've created my own concert with a couple of simple layered sounds, and also tested all of the keyboard templates - what's odd is that even when not playing, CPU usage is 20-25%+ !

Then, when I start playing, it jumps up and stays around 60%, often going a lot higher when it's an ES2 synth sound or something.

I don't want to increase the buffer from 128 to 256, as the latency is worse of course. And, having tried all of the buffer sizes, increasing to 256 makes a minimal difference to the CPU usage anyway.

I thought my MacBook Pro with 4GB RAM and 7200rpm HD would have had no problems with this! Yes, if I was layering 10 Sculptures with 4 Space Designers on each, but not just a couple of relatively simple sounds.

Hmm...

Reply

Answer 4

MarkW19 Author

Level 1

8 points

Jan 30, 2008 11:42 AM in response to MarkW19

Well, today I created a new patch, which only contained 3 sounds - piano, electric piano, and bells just in one octave. Just a simple reverb (not Space Designer) on each.

And, before even playing a note, my CPU meter is above 50%!!

What's wrong with my system? I have a 2.2ghz Core 2 Duo, 4GB RAM, 7200rpm Hard Drive, buffer set to 128 (or 256, it barely makes a difference), and they're barely complex/intensive sounds that I'm using...

Notes cut out when I sustain more than a few at a time, and the whole audio cuts out sometimes too.

Can someone give me some advice to set this thing up so that it's useable please without having to limit my playing/sound choices so much?

Reply

Answer 5

gkeiser

Level 1

0 points

Jan 30, 2008 12:55 PM in response to MarkW19

I'd start with repairing permissions for Macintosh HD. Then before you launch Mainstage disable Airport. Go to System Preferences, select Sharing and make sure nothing is shared (none of these services should be running).

Next Select Energy Saver.
Settings for: Power Adapter
Optimization: Custom

Put the Computer to Sleep... Drag it to Never
Put the Display to Sleep.....Drag it to Never
Uncheck "Put the hard disk to sleep...

I would imagine you won't be using the laptop w/ Mainstage while in battery mode. Repeat the same for Battery (Settings For:).

Click on Options and uncheck all but "Show battery status in the menu bar".

What's your interface? Did it require drivers (MOTU, RME)? They could be the culprit as well.

If you ask me I don't think Mainstage is ready for a "mission critical" live performance. It's appropriate for keyboard players more than for guitarists. I play w/ backing tracks and I can't imagine not being able to see a list of the tracks in my set. I figured out the Apple Scripts for iTunes, but if I can figure out how to display the track order in Mainstage without switching between the apps it would be nice. It makes me nervous for some reason, ya know!
Meanwhile, I'll keep using Ableton Live.

Let us know if you need more help.

George

Reply

Answer 6

MarkW19 Author

Level 1

8 points

Jan 30, 2008 1:03 PM in response to gkeiser

Thanks for the advice, but I've already done everything you've said 😟

And as far as repairing permissions goes - I've only had the MBP for one day, and Mainstage was the very first (and only!) app I've installed, after Leopard.

The thing is, I get similar CPU usage in Logic itself while playing some instruments, so it doesn't seem to be Mainstage-specific. I thought my MBP would take all this on in its sleep!

Reply

Answer 7

gkeiser

Level 1

0 points

Jan 30, 2008 1:19 PM in response to MarkW19

I read on another forum that a lot of guys are doing a clean Leopard reinstall as soon as their machines arrive and then one music app at a time, check performance, then install next, etc.
I have the exact same permissions repaired every time I run the Disk Utility. It's really strange.

You didn't tell me about your interface. I use mine with MOTU 828mk2. The drivers seem to be solid, but sometimes they don't mute the Mic/Line input I have the guitar plugged in. I don't think you can get good results with the builtin audio, especially at lower buffer setting.

I'd seriously consider reinstalling Leopard or maybe call Apple first. You can try to repair permissions after you boot from you DVD that came with the book. If you have another music app, install it and check you CPU utilization. Perhaps your Logic installation is corrupt.

I have to fly to a gig now, but I'll catch up with you later.

George

Reply

Answer 8

MarkW19 Author

Level 1

8 points

Jan 30, 2008 1:27 PM in response to gkeiser

Hi George,

Sorry - I'm just using the built-in order on the MBP, as I thought that would give the best (least) latency? Are you saying that an external FW interface would improve things? That won't change the fact that my CPU is at 50% sometimes even before playing a note though! And, I want to just take the MBP out on its own if possible, for portability reasons...

I may do a clean Leopard install, do you really think that would change my CPU usage?!

Reply

Answer 9

MarkW19 Author

Level 1

8 points

Jan 30, 2008 4:55 PM in response to MarkW19

Well, I just wiped my drive and installed Leopard again, along with Logic/Mainstage, and it's just the same. CPU idling around 50%, even when only a couple of sounds are selected in the patch, and more importantly - when I'm not even playing anything!!

Hmm...

Reply

Answer 10

MarkW19 Author

Level 1

8 points

Jan 30, 2008 7:08 PM in response to MarkW19

Now, here's the weird thing - I forgot to install the Mainstage 1.0.2 update after I re-installed everything, and I opened my concert, and CPU usage on this particular patch was 10% at most.

I upgraded to 1.0.2, and the same patch is 40-50%+!!

What gives?

Reply

Answer 11

msteveng

Level 1

5 points

Jan 31, 2008 8:00 AM in response to MarkW19

what I would like to know is why the CPU usage increases whenever I play a note. I have one patch for example that idles around 70% but if I attack a note real hard it sometimes jumps to 100% and gets into the red. I don't know how mainstage works or the plugins themselves, but it would seem to me that once you have a plug in loaded, it should already be using the max cpu it would need. I am not sure why playing a note loud or soft should have impact on the CPU usage.

Reply

Answer 12

MarkW19 Author

Level 1

8 points

Jan 31, 2008 9:03 AM in response to msteveng

I'd just like my patches not "idling" at 50%+ when I'm NOT even playing a note! 🙂

Reply

Answer 13

MarkW19 Author

Level 1

8 points

Jan 31, 2008 9:04 AM in response to MarkW19

What buffer setting do you use in mainstage?

Reply

Answer 14

MarkW19 Author

Level 1

8 points

Jan 31, 2008 10:14 AM in response to MarkW19

Can anyone with MacBook Pros please do a test for me? :-

Open Mainstage (only app running), and choose one of the keyboard templates - Jazz - then select the grand piano sound. What is your CPU usage (%) while not playing, and what does it go up to (average) while playing relatively complex/sustained but not over the top?

I'm sure my MBP 2.2/4GB RAM/7200rpm HD shouldn't be having trouble with this?

Reply

Answer 15

aerol

Level 3

555 points

Feb 4, 2008 10:51 AM in response to MarkW19

My portable is a MacBook Pro 2GHz Core Duo with 1.5GB RAM.

If I open the Jazz concert and with the Grand Piano patch selected the help tag that is displayed when I hover over the CPU meter in Mainstage indicates that 8% of the CPU is used. This is with Mail, Safari, iChat, Skype, iCal and TextEdit also open. I don't have any audio hardware attached so built-in is being used. Buffer size is set to 128.

Sorry, I don't have a MIDI keyboard attached so I can't test the playing part of the question, but while sitting idle it would appear that I am not having the problem you are seeing.

Reply