@dterry, I really don't think that the point of a multi-mic library is to not use them. I could also save system ressources by not using half of the articulations. Or using Violins 1 only. You get the point.Generally, with multi-mic libraries, I don't think that using a single mic position is good or desirable most of the time. Not with Spitfire, not with Orchestral Tools, Cinematic Studio series OR Synchron.
No, the articulations single-sections analogy isn't valid here - two very different tradeoffs.
Of course the point of multi-mic is to provide options, but it doesn't mean you can't or shouldn't use a single mic if needed, or if multiple mics simply are not necessary. I'm not sure what you are suggesting VSL give up to allow you to run all articulations and mics. Velocity layers make a noticeable difference when using velocity crossfade via cc fader. How much RAM are you trying to fit this into?
I would think anyone buying libraries with these options would be well aware of the need to configure systems, and mixing options, to make use of them, or be willing to compromise. Surely users don't think they can run a full Synchron orchestra template on a 32G, or even 64G PC with all mic options. I wouldn't consider building a new system with less than 128G at this point, even before Synchron.
Fwiw, OT's Berlin strings work fine with a single mic, if you use the right one, or have the score mixed by a score mixer (done that before). What sounds good "out of the box" doesn't necessarily work as well in a mix, especially with other libraries in a complex score, at least when these are not just for mockup reference.
To bring something positive back to this thread - Synchron is a new standard, at the very least for the surround/Atmos options. Every library requires some work and skill to get convincing results, if you write for the music instead of the samples. There isn't much VSL, EW, OT, Spitfire or anyone else can do to change that.