Mainstage, Pianos -- Plug-ins vs. Stand Alone vs. "Tones" on the RD-2000 EX
It's been a journey and one I'm ready to end. We'll see what happens next. ANYWAY.
I'll refer to the posting I did in Digital Pianos regarding key learnings about the tech of Mainstage version 4.3.1 on MacOS Tahoe and Golden Gate and M4 36 GB Mac Mini. The primary issue was overloads (sounds bad in theory, in reality, for my private use, mostly not an issue unless they occur while recording.)
Claude (Opus 5.5 medium judgement) was the most helpful resource in all of this. Claude is patient, thorough and non-judgmental
Siri (even the new one which resorts to Gemini, or the prior instance that will route you to ChatGPT) isn't worth it due to likely using a less advanced AI model. I went through several iterations of it telling me to change Mainstage settings that no longer existed in the current version, referring to techniques obviated by updates to Mainstage. Likely drawing from those same 'expert' fora.
For people who just want to play their virtual pianos, I think Mainstage is overkill, and unnecessary unless you want to use the Apple pianos (which are decent enough.) You could also do so in GarageBand, which is on iPhones and iPad (Mainstage is not.) GarageBand also supports piano plug-ins. I'm guessing the support for Pianoteq on iPad/iPhone doesn't include the mulit-core setting...
The learning that caused me to drop Mainstage is that when you set up a keyboard 'concert,' it, without asking, adds reverbs (associated with halls,) choruses and what have yous at the concert level.
Not even mentioned in my discourse on this topic is the very recent discovery that these third-party piano plug-ins have settings for multi-core processing (on by default) that overrides Mainstage's strategy of allocating a single core per patch. So, another side quest to figure out how to turn off multi-core processing in each of my plug-ins.
The best I can say is that I've learned a lot. I've also reinforced I would much rather suffer AI 'splaining than the human equivalent.
For my purposes, the best approach is as follows:
- Use the stand alone apps for the manufacturer (Kontakt, Synthogy, VSL, Pianoteq)
- When changing between apps, close the unused app
- Leave the multi-core settings active in the stand alone apps
I've setup aliases for each, then copied each alias into a single .nosync desktop folder for easy access.
This closes the book on this topic for me.
As for the RD-2000 EX's collection of pianos.
They're really nice. The one thing that's pretty different about them is pedal behavior and it seems consistent across piano 'tones.' Pedaled notes seem to decay more rapidly than what one experiences in the various piano plug-ins I have, and possibly real-life pianos. Also, one of the Warm Touch 'tones' includes damper pedal noises that I've not encountered yet on other piano 'tones.'
I wouldn't hesitate to use them in a situation where I didn't want to have my computer along (though I could use Pianoteq on my phone...) ANYWAY... Onward!