Cubase 9.5 - Cannot load VST plugins in big projects

Jenya_Melnikoff · April 27, 2018, 10:09pm

Upgreded to 9.5.21 - same issues with RAM.

cyberluke · May 9, 2018, 5:34pm

Yes I also have this problem and I live in country next to Germany, but we cannot open SB support ticket, we have to use this forums only!!!

mart · May 10, 2018, 11:02am

This is a known major issue for a few years now:

Download and install the FLS checker (see top of forum). It tells you how many unique plugins you have left to instantiate on your system in a nutshell. If you use many of the same plugin you can use as many as you like. Some plugin vendors use more of the open system static linking slots that others

Steinberg are carefully moving to help resolve the issue but it also lies at the door of the plugin manufacturers and moreso Microsoft

kavinsky · October 23, 2018, 10:27am

I had this for years too
steinberg has dropped their ball with fixing stuff lately. shame.

kavinsky · October 23, 2018, 10:27am

I had this for years too
steinberg has dropped their ball with fixing stuff lately. shame.

mart · October 23, 2018, 3:48pm

Its not just Steinberg its a Windows issue. Everyone affected needs to make separate complaints to the worst offender plugin vendors (UAD to name but one) to change the way their plugins fundamentally allocate their resources in a nutshell. Without doing that it will never be fixed!

Psychlist1972 · January 10, 2019, 5:43pm

Hi All

Sorry to spam threads, but I want to make sure everyone hit by this knows that a solution is in the works, and is currently available in the latest Windows 10 Insider build.

The per-process FLS slot limit used to be 128 going back at least to Windows Vista. PCs have gotten more powerful, though, so folks are really starting to run up against that limit before running out of CPU / memory. Additionally, some more recent and complex plugins use quite a few of those slots themselves. So to unblock musicians, we’ve rewritten the code that does FLS allocation and bumped the slots up to over 4000.

Technical folks who want to test on a non-critical PC are encouraged to do so. For the rest: if there are no issues found, this update will be in the 19H1 release of Windows 10 later this year. DAW and plugin developers do not need to do anything as this change is in the OS.

Official post:

Synthtopia asked me a bunch of questions about it and therefore has more technical details for those of you who want a more in-depth explanation:

Pete (Microsoft)

marQs · January 10, 2019, 5:56pm

Looking forward to that update (I usually don’t) - this will be liberating!

xanthos84 · January 10, 2019, 7:53pm

Psychlist1972:

Hi All

Sorry to spam threads, but I want to make sure everyone hit by this knows that a solution is in the works, and is currently available in the latest Windows 10 Insider build.

The per-process FLS slot limit used to be 128 going back at least to Windows Vista. PCs have gotten more powerful, though, so folks are really starting to run up against that limit before running out of CPU / memory. Additionally, some more recent and complex plugins use quite a few of those slots themselves. So to unblock musicians, we’ve rewritten the code that does FLS allocation and bumped the slots up to over 4000.

Technical folks who want to test on a non-critical PC are encouraged to do so. For the rest: if there are no issues found, this update will be in the 19H1 release of Windows 10 later this year. DAW and plugin developers do not need to do anything as this change is in the OS.

Official post:
Announcing Windows 10 Insider Preview Build 18312 | Windows Insider Blog

Synthtopia asked me a bunch of questions about it and therefore has more technical details for those of you who want a more in-depth explanation:
Microsoft Windows 10 Update Will Let You Use More Virtual Instruments & Effects In Your DAW – Synthtopia

Pete (Microsoft)

Wow, someone from Microsoft directly replies to my thread which is now open for a long time.

And with awesome news, too. Thanks Pete!

Happy day today!

mart · January 10, 2019, 8:13pm

Psychlist1972:

Hi All

Sorry to spam threads, but I want to make sure everyone hit by this knows that a solution is in the works, and is currently available in the latest Windows 10 Insider build.

The per-process FLS slot limit used to be 128 going back at least to Windows Vista. PCs have gotten more powerful, though, so folks are really starting to run up against that limit before running out of CPU / memory. Additionally, some more recent and complex plugins use quite a few of those slots themselves. So to unblock musicians, we’ve rewritten the code that does FLS allocation and bumped the slots up to over 4000.

Technical folks who want to test on a non-critical PC are encouraged to do so. For the rest: if there are no issues found, this update will be in the 19H1 release of Windows 10 later this year. DAW and plugin developers do not need to do anything as this change is in the OS.

Official post:
Announcing Windows 10 Insider Preview Build 18312 | Windows Insider Blog

Synthtopia asked me a bunch of questions about it and therefore has more technical details for those of you who want a more in-depth explanation:
Microsoft Windows 10 Update Will Let You Use More Virtual Instruments & Effects In Your DAW – Synthtopia

Pete (Microsoft)

This is amazing news Pete.

uarte · January 15, 2019, 1:49pm

Great news, Pete! Thanks for posting and more importantly, thanks for pushing this at Microsoft and getting some real, tangible results. Looking forward to the release!

emrah · February 1, 2019, 11:00pm

joelalucas:

Hey there. So I have been having this problem for years now. I recently tried the jbridge solution, and to my surprise it seems to have completely solved the problem. Although, it has only been a couple of days, but I am cautiously optimistic. What is puzzling to me though is that, if running 64-bit plugins through jbridge solves the problem, despite the shortcomings of Windows, or UAD and Waves software, can the problem be really that impossible to implement in Cubase? I know nothing about software programming and perhaps I am thinking too simplistically about it, but can’t Steinberg or UAD write some code to do to the plug-ins, whatever jbridge is doing? Or is “jbridge guy” some reclusive coding maniac who won’t share his secrets no matter how much money Yamaha throws at him?
Anyway, for about $25 CDN for jbridge, I’m back to work and not pulling my hair out (for the moment).

Hi there. How did you solve this problem by using Jbridge? i have same problem on Pro 8.5

Could you please tell me ? I have already jbridge and what should i do?

emrah · February 1, 2019, 11:03pm

Could you please tell me how I can solve this limitation by jbridge? I have it and what should I do? I have only 64bit plugins.

emrah · February 2, 2019, 5:27pm

Is there anyone who can tell me how can I solve this issue temporary by jbridge? Should I convert all x64 VSTs to jbridge x64 then scanning, adding them to in Cubase? And use jbridged VSTs ?