Ahh, I I think know why - because you have only the “Standard” versions. I missed that before. The Studio are all based on the VI “full” version - the standard versions no longer exist for the Studio. So it is an upgrade because you get more samples/techniques equivalent to the VI “Full” versions. That’s why the cost is higher. If you had the full versions of the VI solo strings, the cost for the upgrade to the Studio Solo Strings would be significantly lower.
1 Like
I’ve tried various combinations (and discovered that Dorico needs a restart - because that’s when it reads them in - for changes to take effect) but still can’t get it right:
I either get two exclamation marks either side of Synchron (and Synchron Surround), which seems to mean it/they isn’t/aren’t available; all of them again; or none.
What would the correct VST 2 setting be for, say, just Synchron Player version 1.3.2235 (on macOS 15.4.1, please (it’s not at root level of /Applications) until I add the Symphonic Riot maps and have to face VI Pro? This page explains the overall principle of this; but doesn’t give the detail which I think I need.
Michael,
Of course. I have some thinking to do. Thanks.
I do find the Studio/VI solo strings to sound fairly unconvincing when reasonably exposed, compared to the Synchron ones. I purchased the Studio Solo Strings not because of the sound, but because sometimes I might need some specific articulation that the Synchron ones don’t have. That’s the same reason I bought Studio Brass.
Recordings on the old Silent Stage probably were cheaper to make than Synchron Stage recordings because it’s not taking the hall away from other purposes. So, they could sometimes get away with recording more techniques. Although as far as string sections are, Synchron Duality Strings has more than any previous VSL dry libraries, so just because it is more expensive to sample in Synchron doesn’t always mean they will sample less. But in general terms, I would say it is the case.
1 Like
Leave all of the VSL stuff in the “blocked” side, don’t have any of it in the “allowed”. I don’t know if Ivory has a VST3 version, if it is VST2 only you can leave it in allowed. For most people the “allowed VST2 Plug-ins” list should be empty.
If you get exclamation marks, it is simply because you probably added the VST2 version of the plugin in an existing file by mistake and then blocked it and now it is no longer there. Just leave the VST2 stuff blocked and load the VST3 version instead.
1 Like
Hmmm. I thought that would have done the trick:
But I still get this - even with a new Project:
Will do. I think it’s still VST2.
Thanks. Yes. That’s clear. It is for me know, and restarted and cleared that cache etc. But it still seems not to have cleared the list, doesn’t it…
I remember we used to have to manage a text file manually of VST 2 (?) plugins with Dorico 1, 2, 3? Could that still be the case, do you think?
That looks correct now - there are no duplicates in the list anymore in that latest screenshot.
In your old screenshot you had two of the “Vienna Synchron Player” (with identical names).
1 Like
Michael,
That’s good to know for me in the future :-).
Which doesn’t have solo strings, as far as I can see; does it?
No, it doesn’t.. Duality Strings is just section strings only.
1 Like
Michael,
Yes, I see. The implication is that everything that’s there is forced to be VST 3?
But what’s the difference between Synchron and Synchron Surround?
In the not too distant future I expect to be able to discard everything except Synchron!
In my case I really do want solos.
Correct, because the VST2 versions are blocked. Therefore anything left has to be VST3 (there’s no UI in the program to block or allow a VST3 plugin, all VST3 plugins are allowed in Dorico unless Dorico itself blacklists something due to detecting a malfunction/bug).
1 Like
No, the VST2 blacklist/whitelist control was moved into the “Allowed VST2 Plug-ins” section of the UI so that people don’t have to edit the text file anymore. And that’s just for VST2, not for VST3. All VST3 are allowed in Dorico unless Dorico itself blacklists are plugin when it detects a major bug or malfunction.
Yes. Your memory is better than mine, Michael.
I think I’m all set for the moment. Very many thanks for all your help!
1 Like