All Articles News
This Windows 10 Update Will Let You Run Way MORE Plugins In Your DAW!
Hollin Jones on Fri, January 11th 3 comments
If you have ever wondered just how many plug-ins your Windows PC can handle, you'll be happy to learn that the number is about to go up. Way up. Here's how it's going to happen.

Windows has always had to cater to an extremely wide spectrum of users, since it's far and away the world's most widely used desktop operating system. And that has meant that although it is popular with creatives - much more so than it used to be thanks to the work Microsoft has done to improve its stability over the years -  it still has some technical limitations that can hold it back for some high end creative tasks.

One such limitation is about to be blown away however, with the introduction of a forthcoming update to Windows 10 - which you can read about in detail here. It's about the way Windows manages its resources, and concerns the fact that modern, multi-core PCs with tons of RAM are capable of running more processes than the operating system can actually deal with, due to a longstanding limitation. But the important part for musicians is this, as stated by Microsoft.

FLS Slot Limit Increase

"As PCs get more powerful, musicians have created increasingly complex projects with more tracks, more instruments, and deeper effects chains. As a result, some of those musicians were running up against a FLS (Fiber Local Storage) slot allocation ceiling that prevented them from loading into their DAWs (Digital Audio Workstations) as many unique plugins as they’d like. This build greatly raises that per-process FLS slot allocation ceiling, allowing loading potentially thousands of unique plugins. Beyond musicians, this change will positively impact any application that dynamically loads hundreds or thousands of unique DLLs that have statically-linked Visual C++ runtimes, or otherwise allocate FLS slots."

Synthtopia spoke to Windows expert Pete Brown about what this actually means in layman's terms.

"“It’s a bit hard to put this completely in layman’s terms because it’s a change to the kernel code in Windows. But here’s a shot:

FLS slots are how we manage small in-memory storage locations for what are called “Fibers”. Fibers are lightweight threads. Threads are bits of code that execute in parallel, sometimes on different processor cores. Almost everything done in parallel in a DAW is using either Fibers or Threads to allow that code to be run. How that is handled differs from DAW to DAW.

DAWs are a process that can load external code (plugins) that are contained in DLLs. DLLs (Dynamic Link Libraries) are compiled code that is packaged specifically to be loaded by other processes. DLLs are the main way code is shared on Windows.

Most VST plugins for Windows are compiled using a version of Visual C++. Visual C++ has a runtime library full of functions that are used by anything compiled with it. That runtime library allocates (depending upon version) one or two FLS slots per instance of the library loaded in a process.

Now, for convenience and ease of installation, most plug-in authors statically link that runtime. That means that the runtime code is included inside the plugin DLL, instead of referenced from another DLL. So, if you have 50 different unique plugins loaded in the DAW, and each plugin statically links the runtime, there will be 50 copies of that runtime code loaded into the DAW process. Each copy of that runtime code will allocate one or two FLS slots, so you can end up with between 50 and 100 FLS slots used just by the runtime.

If the plugin dynamically links the runtime (that is, the plugin references a runtime DLL that is installed with the plugin, or is already present on the system), only as many copies of the runtime will be loaded in the DAW process as there are unique versions of that runtime. So, if there are 50 plugins in the process, but collectively they use, say, 5 unique versions of the runtime, there will be only 5 copies of that code loaded into memory. This is obviously better for memory usage, but also better because there will only be between 5 and 10 FLS slots used."

If your interest in the nuts and bolts of Windows doesn't quite stretch to that level of detail, he also added:

"Developers don’t need to do anything, but end users will no longer have their DAW plugin count capped by this limitation. The new count means that, today, users will run out of memory and processor time before they run out of FLS slots. But we’ve made it much easier for us to change in the future if/when we need to make it more than 4000.

The limitation goes back to the Vista and XP timeframe. The reason folks are running into it now, is PCs have gotten so powerful, that musicians are hitting this limit where before they would simply run out of memory or CPU.”

So there you have it - you don't have to do anything except install the update to Windows 10 when it gets released, and you should find that any issues you'd had trying to load very large numbers of effects and instruments is magically solved. Thanks, Microsoft!

Via: [Synthtopia]
Learn to make music using the DAW of your choice: https://ask.audio/academy?nleloc=new-releases
Related Videos
Comments (3)

You must be logged in to comment.

  • banjo1
    I'm just curious. Does this ONLY apply to DAWs? What about something that isn't technically a Daw, like VCV Rack? It would be awesome if this promised improvement meant that we could use more VCV rack plugins than are possible now!
    • 4 months ago
    • By: banjo1
    Reply
  • Bycuzyi
    Given the changes are in how Windows handles the plugins, which are DLLs as are the modules in VCV Rack running on Windows, I see no reason why it would be any different than with DAWs. I could be wrong, but logically it seems there shouldn't be any difference.
    • 3 months ago
    • By: Bycuzyi
  • After lust Windows Update no More Harrison Mixbus 32 C VST Plugins woork ? I have the same problem all kind o VST2 plugins work om Mixbus32C only the AVA plugins are not working and not show in Plugins Manager ? I have cheked all and is well done ! [INFO]: Output channel count configuration not supported [INFO]: Input channel count configuration not supported [INFO]: --- Windows VST plugins Scan: C:\Program Files\Steinberg\VSTPlugins;C:\Users\hermi\OneDrive\Documentos\Plugins\VST [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-DS_64bit.dll (cache only) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-LegacyQ_64bit.dll (cache only) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-MC_64bit.dll (cache only) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-ME_64bit.dll (cache only) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: --- Windows VST plugins Scan Done [INFO]: harvid version: 803 [INFO]: Loading menus from C:\Program Files\Mixbus32C-5\share\ardour5\ardour.menus [INFO]: Loaded custom session defaults. [INFO]: Loading 441 MIDI patches from C:\Program Files\Mixbus32C-5\share\ardour5\patchfiles [INFO]: Loading plugin order file C:\Users\hermi\AppData\Local\Mixbus5\plugin_metadata\plugin_order [INFO]: Loading history from H:\Harrison-MixBUS-DATA\scan1\scan1.history [INFO]: scan1: no history file "H:\Harrison-MixBUS-DATA\scan1\scan1.history" for this session. [INFO]: --- Windows VST plugins Scan: C:\Program Files\Steinberg\VSTPlugins;C:\Users\hermi\OneDrive\Documentos\Plugins\VST [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-DS_64bit.dll - x64 (64-bit) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-LegacyQ_64bit.dll - x64 (64-bit) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-MC_64bit.dll - x64 (64-bit) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: * C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-ME_64bit.dll - x64 (64-bit) [INFO]: -> Cannot get Windows VST information, plugin ignored. [INFO]: --- Windows VST plugins Scan Done [INFO]: VST Blacklist: C:\Users\hermi\AppData\Local\Mixbus5\cache\vst64_blacklist.txt C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-DS_64bit.dll C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-LegacyQ_64bit.dll C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-MC_64bit.dll C:\Program Files\Steinberg\VSTPlugins\Harrison_AVA-ME_64bit.dll
    • 6 hours ago
    • By:
    Reply
Getting Started with Windows 8
Windows 8 101
Dream It. Do It.
Do you want to learn Getting Started with Windows 8?
Yes, I want to learn!
No Thanks, I just want to read the article.
Feedback
Course Advisor
Don't Know Where To Start?
Ask A Course Advisor
Ask Us!
Copy the link below and paste it into an email, forum, or Facebook to share this with your friends.
Make money when you share our links
Become a macProVideo.com Affiliate!
The current affiliate rate is: 50%
Classes Start Next Week!
Live 8-week Online Certification Classes for: