So I’m also having trouble with this bug: http://www.steinberg.net/en/newsandevents/news/newsdetail/article/vst-plugin-loading-limitation-on-windows-3852.html
Nuendo 7 also has this problem, which is to be expected I guess. The problem is, since I installed redstone this problem has gotten a lot worse. I had it before but only on huge projects. Now projects that worked on the older windows 10 crash on opening on “redstone”, giving me a c++ error.
I can manage to open the projects by loading them on my macbook pro, freezing EVERYTHING that can be frozen and then loading them back in windows. But after this I still can’t load extra plugins.
This is super annoying since now I have to finish my projects on my macbook
Is there any time frame known when an update comes to fix this? I saw on KVR that U-He had suggestions to fix this.
Actually I use both and since Windows had been working good for me, with some ups and downs, for years now I never thought I’d say this, but today I was considering to install a dual boot as a hackintosh on my pc…
I hope they fix this soon…
BTW, the quicktime problem (no video) is not that bad… you just have to take the risk of installing quicktime
Thankfully a lot of plug-in developers are aware of the issue now and have fixed things at their end which lessens the problem (as long as you’re up to date with the plug-in bundles). Steinberg also need to make changes at their end to fully resolve it.
My Win 7 machines stay offline and therefore cannot be updated by MS. I have never experienced any sort of the problem mentioned. Obviously, MS is pushing updates to their OS variants that are causing issues:
Everything is working fine.
Microsoft decides to push OS updates to all various manner of code in their various OS iterations. Without asking the user’s permission. The person who paid to own and use the hardware/software.
In doing so, MS breaks various functions at the developer and end user level.
Developers then waste time fixing what MS broke instead of improving their product.
End users waste time experiencing, analyzing, blaming the wrong party, working around (hopefully) the issue and then finally applying the the fix the developers provide after varying amounts of delay.
Everything is working fine.
Repeat, beginning at Number 2 above.
And people wonder why my DAWs are offline, thinking it’s archaic. Not if you want to avoid the cycle I described and spend that time making music, instead.
Can you follow up with how you know that to be true? The issue appears to exist across a number of DAW software packages.
I have various versions of hundreds of audio plugins and VSTi on my system, doing large track count mixes with many, many plugins as well as having updated through all the variations of Nuendo beginning with N2. I’m currently running N 7.1.20. Some of my Templates instantiate with hundreds of plugins in total.
I have never seen this issue. And my DAW is offline. The OS has not been updated in years. Zero plugin issues for me.
It’s not the number of plug-ins in the session but rather the number of unique plug-ins which aren’t using the dynamically linked C runtime library and thankfully most of the major vendors have fixed the issues now.