busy mix most plugins will no longer load

I have lost track of the TENS OF HOURS this issue has cost me. I understand that it may be complicated to resolve but it’s completely unacceptable that my sessions do not recall properly.

I cannot believe that Cubase 9 has still not brought a fix - and until it is, there is absolutely no way I will be upgrading.

Wow, this is really a killer. I know of the problem as I ran into it earlier with big mixes containing plenty of plugins. The workaround to only add plugins that are already used in the project was fine for me (anyway no chance of adding something new) but…

… yesterday I realized that projects that were created with that workaround now have plugins missing when I open them :imp:

This has never happened before and is a real show stopper! The mixes are literally blown.

Thought id chime in once again as nothings happened since the last post! Whats happening Steinberg? This problem is massive and nobody doing anything to update the customers on a fix? Everyday this problem is occurring and its ruining my sessions. I just upgraded to Cubase 9 and the problem is still there, how can you even release a new version with such a great problem?? Laughable :laughing:

Added a feature request: Remove dll limit on Windows - Cubase - Steinberg Forums

Same problem here after updating uad.

I’m on Windows 7 and Cubase 8.52 pro and use a uad octo card. Everything worked great (when uad device was found - what wasn’t and is still not always the case). In November and December I bought some new plugins: Slate Reverb, Fabfilter Pro-R, Plugin Alliance bx-control, Melda Vintage Rotary, UAD Elisia Mpressor and UAD studio d chorus.

My UAD-Software was about 9 to 12 months old - and because of the studio d chorus I have had to update. I installed uad 9.0 - and now some plugins (different manufactures) don’t load randomly.

Is it possible that it’s a problem with the newer uad version? Or maybe the bx-control causes the issue?

Very frustrating that this problem is discussed here for quite a while and there’s still no solution. I think it could be a problem with the newer uad software - cause my older working version was older than this thread. Did you all had the issues one year ago?

Ps: Sorry, my English isn’t that good. I hope you understand me

Ok guys more of you need to write to UAD support… this is what I just got as a status… 5 users have complained and its not enough to drive UAD to do ANYTHING.
"
From UAD Support…
""Ïts not clear why this has come to fore, and seems to be a question that all plug in and DAW manufacturers are wondering about as well. I’ve talked to our Engineering team about this previously and they confirmed that nothing changed in our software at any point to start invoking this limitation, and that our software has always been effected by this .dll limitation in the same way. Since this is ultimately a Windows limitation and not related to any specific DAW or plug in manufacturer there could have been a series of Windows updates that caused this limitation to be more easily reached or something similar that would have affected all Windows systems at once, although that’s still just a guess.

Regarding improving our plug ins to be less effected by this issue - as I’m sure you can understand, what we choose to spend development and maintenance time on is directly related to the issues and problems that our customers are reporting to us. While I agree with you that this issue has the potential to affect all user on the Windows platform, in reality we have had very few users (less than 5 total) who have ever contacted us to report that they’re running into this limitation. We also have to take into consideration the huge amount of time that it will take to switch all of our plug ins from using the static C runtime library to the Universal C runtime library, and keep in mind that even that won’t get rid of the limitation, it will only push it out further. “”

I’ve been experiencing this too, going back several months - just in case Steinberg needs to hear from more users about this, though it sounds as though they’re on the case.

Currently running Win 7 Pro SP1, with 32 Gig RAM. Mid-way through what I imagine would be considered a mid-sized track count - 75 tracks, including group channels (about 8) and FX (also about 8). At a total plug-in count of just over 120, no more plug ins will load.

With 75 tracks, many (most) of them actually have NO plug-ins inserted on them … yet.

This is incredibly restrictive - and super frustrating after having an expensive computer specifically built just to run Cubase! Effectively, there seems to be no way that Cubase, in its current incarnation, can be used in anything like a professional situation when running Windows!

You can do no worse than chime in on the bugs forum and also contact the support of your main plugin vendors. It’s a windows issue but Microsoft and the software vendors together need to be petitioned to come up with a fix. If not enough users report this nothing will be done

I have had the same problem since I switched exclusively to 64 bit.
Regardless of Windows (7 or 10) from the moment a Cubase project alone reaches the +/- 6GB of ram, it begins to not load certain plugins. And from a point cubase does not even load his own natives!

intel i7 6700 quad-core processor, 32 GB ram, Apollo firewire, cubase 9.0.1 … the same goes for 8 or 8.5.
The only solution is to give up windows

I’m having some success loading Steinberg’s own VST3 plugins, such as the tube and vintage compressors, but not a lot of luck elsewhere now.

My project was 107MB but I have 64GB ram, with 34GB free atm. I’m closing out the project, removing ‘dead wood’ and the project is down to 84MB but the issue continues.

I had be plagued with this problem but the past 2-3 weeks I’ve been mixing very complex mixed with extremely high counts of varied plugins and have not hit a load limit !? ?!!

Could a Windows Update have happened in the past 2-4 weeks that lifted the limit?? Anyone experiencing similar running Windows 10 ?

Could be. Seems Windows Updates have more of an effect on things than it should. The one in March caused all of my Projects using Brainworx plugins to crash on load - I had to remove them from my vst directory.

Mind you, I bet that’s down to bad coding practises on Brainworx’ side, rather than Microsoft.

Hey guys, I have been having this issue from last december. Finally I decided to jump to Hackintosh. Got it installed on my desktop couple of weeks back & everything is sorted. I am not having any more issues. Plugins are no longer disappearing & I am able to load more plugins into heavy sessions which I couldn’t earlier.

I was using Win10 & Cubase 9 earlier. & I was having issues with TRacks Classic Compressor,
UAD Precision Multiband Compressor, VSM3, Slate Trigger2 etc. Now they are all working fine.

If it’s hackintosh though your on OS X right? This is a Windows only problem

Salut,
first of all, thanks to all of you who provided information this far. It helps a lot
I ran into this problem two days ago, never had any issues before, using tons of plugins. I so serched on the iNet and found… nothing helpful
https://stackoverflow.com/questions/1437422/working-around-fls-limitations-with-too-many-statically-linked-crts
I tried to hide all my plugins from the black list into a separate folder, made all not-used plugs inactif. Nothing helps.
well, the problem appeared after I tested a mix in an other studio over my laptop, which is , guess what, a windows pc. BUT it is not the first time I do this kind of testing, it was the first test after I made my win security updates (WIN7).
Before I restore my C: (system), gladly I made a backup before updating WIN, I wanted to know, wether Windows changes sth or writes sth onto the Cubase project file. I cannot explane otherwise, why the problem is only on this particular cpr-file and no other, even on my main audio-computer, with no iNet connection , so no win update…
Thanks in advance for any suggestions,
Stevie from France

Have you tried that Fabio suggestion?



As Fabio said this is not a solution, however it helped me to be able to work on some projects affected

Ya, I tried that option, but didn’t help.
But something strange happened, after the worst case scenario where most of my FX Plugs dissapeard and couldn’t not be re-instantiated:
everything went back to normal !!! I don’t know why. I re-opened some of the bak-files to find out, where it occured and saved them as cpr-files. I went on and I could re-open the corrupted filesand everything was fine. Verystrange, but I’m happy.Like I said, I never had any issues with my config on my main audio machine. The only thing which is to be tried out, that I load the projects on my laptop, where now runs a non-updated version of win 7.

hello all
i am desperatly trying to get kontakt 5 to even appear in my instrument section
i have tryed almost everything and each time i end up rolling back to 8.5 which is a pain because this version sees all of my great plugins
i would like to know why kontakt 5 will not open in cubase 9 as this is the main instrument i use
please help
cheers
paul

i have also informed native instruments to see if its there end
cheers

for me it looks like a 32/64 bit issue. Cubase 9 does no longer support 32 bit plugs, and/or check your blacklist