- open pianoteq plugin, set the volume of sustain pedal noise to 0 (if i remember correctly is under "action")
- check the sample rate of pianoteq plugin in order to match mainstage one (and set both to 44.1Khz - 16bit)
- set mainstage buffer to default, there's no real need to modify it IMHO
- set mainstage master volume in order to just border the main audio meter red limit (you'll raise your mac volume or the output rig volume)
- disable WIFI and Bluetooth
this should help. if it doesn't look inside pianoteq plugins, there's a section inside options where you can tune it so that it doesn't fry your cpu
these are my settings:
Pianoteq stage 4.0.3 (to check settings open plugin, then "options" then "perf"
I/O buffer size 128, I/O safety buffer on, 128 samples driver latency (of course 44.100khz)
Audio Midi setup:
44.100khz 24 bit integer (integrated sound)
2.4 Ghz Intel core 2 Duo with 4GB Ram.
happened a couple of times with sustain pedal, the sustain pedal noise was overdriving and making lot of sub-150hz noise. i went to "Action" and muted sustain pedal.
you can also try disabling internal pianoteq reverb and use a MS builtin one.
Finally you can try removing your sustain pedal from your layout and placing it on again. Be sure nothing is overlapping!
If you keep having issues try to use "activity monitor" to check if some background little software is eating up our computer cpu.
Good luck, I'm sorry i can't be more straight-to-the-point.
I've been struggling over the last few months, and was putting my frustration with CPU spikes and overloads down to updates to OSX and Mainstage, and the fact that I'm running a (don't laugh...) MBP 2.33GHz Core 2 Duo, with 3Gb Ram.
However, I've found something that has really helped here.
Disabling 'Multicore Rendering' in Pianoteq's Options, on each instance of the plugin in my set has helped immensely. It's returned my rig to the performance I was getting a couple of updates ago. I had not added anything (plugins or channel strips) to my main performance set (I've actually stripped it back as much as I could over the last six months because of overloads), but CPU load had been getting worse with every update to both OSX (Lion) and MainStage, to the point where it was almost unusable.
I suppose this may apply to other plugins that have options for multicore rendering, particularly for those of us using antique core 2 duo technology...
Hope this helps.
Has there been any luck figuring out what the problem is here? This has only happened to me once on stage ever, and I had to reboot Mainstage for it to cop on. But of course that ain't ideal in a gig situation. I've notcied its mainly the ESX24, and one or two ther sampler plug-ins that do this unusual thing. Really annoying cuz thats all my string section compromised. If anyone has cracked it yet, please let me know, I'm so curious and ******!
Using a Mac 10.6.8, 2.26 GHz Core 2 Duo, 8GB ram, 32-bit Mainstage