Installing Waves stuff there is always these redistributables from Microsoft Visual Studio(2008, 2012, 2015 and whatnot) that are installed too.
So using Waves everybody would be safe?
Looking in ProcessExplorer in a not so large project - 6 effect plugins and 4 synths at the moment - 208 DLL’s are loaded in the process.
Eleven are from Waves.
From the abstract of that post OP got the wrong idea what is the solution. It’s not quite that simple.
And there is actaully at least three levels of linking:
a) static traditional linking into executable file of the code - can be C-runtime or anything else, often a OBJ-file.
b) static linking of import libraries for DLL’s - dll must exist when software start or process does not start.
Shared Runtime C-library MSVCRTxxxx.dll must exist or process does not start if that is used. If statically linked it’s not needed.
c) dynamic linking of DLL’s - you make calls from within software to locate DLL’s and if they exist you can use LoadLibrary and then map each call into that DLL as you need it. Usually done on other stuff than runtime C library. Plugins would be in this category, but most things handled by VST SDK I presume. So all plugins are dynamically linked to daw.
So not sure how all this talk about this C runtime library is valid to the problem.
DLL stands for dynamic link library - so there is some confusion going on over linking methods and DLL’s.
Looking around a bit it seems to be windows 10 only, or?
A bit discussed here: