There is no magic number but there is a range that you will see if your surf the forums - apparently some vsts use more "slots" than others with UA plugins being more greedy than others and waves being better than most ( I can confirm the UA behaviour) In the Steinberg forum you'll see posts from Steinberg staff that the upper limit of unique vsts is somewhere in the 50 to 56 range. Studio One is apparently about the same. Reaper is reportedly a little better with upper 50s to mid 60s. But they are all in that range. Some people are getting around it by applying jbridge to 64 bit plugins. I haven't tried this and for now I have only reached my ceiling on a few projects.
Also Cubase 9.5 uses more resources than Cubase 8 and Steinberg made a suggestion to remove a few components to free up a few more slots and they are also gradually doing some internal tweaks to allow more plugins to run but they say it won't be huge difference and these internal changes are being hampered due to backward compatibility with Windows 7. They have explained that the solution lies with the vst developers recompiling plugins to link dynamically to the run-time libraries (I don't truly understand this particular detail - I am just parroting this particular detail back to you).
The unfortunate thing in regard to this behaviour is Cubase gives no indication whatsover that a project is failing to load specific plugins and people have spent hours trying to isolate issues that are a very deep in a mix trying to figure out why some spot effect doesn't sound the same. It is very frustrating. Sometimes they load ... sometimes they won't. Sometimes different plugins will fail and others there were failing will load. Also some projects that worked fine in Cubase 8x will have vst loading issues in Cubase 9x because the app itself uses more resources.
For most people they likely won't hit these limits but there are some of us, probably quite a few of your clients, who really need that available power and reliability for professional/ time sensitive projects.
Also this is not a ram issue which is often the default response of people who haven't encountered the problem when they chime in on the topic.
Thanks, although I'm well aware of this one and if it's affecting you then there are further workarounds being developed, but you'll need to speak to them to establish which is the best one for your setup. I have one in place for my clients already, but it's not a catchall fix and on the wrong hardware combination it's as likely to cripple the system as fix it.
This is also on the Steinberg forum regarding the upper limit of unique VSTs related to statically linked run-time libraries.. if you read the thread you'll see mention of Protools, Studio One, Reaper and others also being impacted by this to varying degrees.
https://es.steinberg.net/forums/viewtop ... 8&t=101195
Both of these bottle-necks are a serious impediments to upgrading. If you can't use the power/cores then the upgrade is rather pointless.
Yeah, this is the one I wasn't fully aware of. Like one of the posters within the linked thread, I've got a vague recollection of it being discussed with older builds/under older OS versions, but I've not seen it occur in a good number of years and thought it was long gone by this point. I'm just intrigued to know what the magic number is, but having glanced over the thread it appears to be a moving target depending upon other resources.
Asusp9712Core,RayDats,OASYSPCI,Cubase9,KorgLeg,Avalon737s+2022,UA4710D,6176,DCS,LA610MK2s,Neve, ARC2, Soundtoys,UADOCTO,AdamA7X, SphereMics, BCF+R2000s, DrmBrut,MiniLog,Volcas,MoogSubPhat,EnsqDP4,VirusC,Scope,MinBrut,Plugiator,NIS61 Ultimate,ComposrsCld.