Originally Posted By: Blake - PG Music


If you are using the 64bit version of Band-in-a-Box (most likely) the file name must be:
MaxPluginsToScan64.txt

This changed in 2019 since the 32bit version will scan for different plugins than the 64bit version. The PluginScanLog.log file should show that 0 plugins are scanned, or which ever number you put in it. For example, if you have "max=2" then your PluginScanLog.log file should show:

Counting plugin GUID {6A08CF80-0E18-11CF-A24D-0020AFD79767} ...
FriendlyName = ACM Wrapper
Counting plugin GUID {E9AFF214-D315-4EC0-A6E7-6C73511C5D21} ...
FriendlyName = PG Click and Pop Remover

This is a bit of tedious way to narrow down which plugin is slowing down the process, but it should work. Note that for the next update (build 716) the BootupLog.txt will show the time each plugin scan takes, so you can narrow it down faster.


Thank you Blake,

I'm using the 64bit version of Bb, but having the file MaxPluginsToScan64.txt in the Bb folder does not seem to affect the number of plugins loaded...

Even curioser, that MaxPluginsToScan64.txt file is automatically deleted when Bb boots up whereas the PluginScanLog.log file still lists the same number of plugins loaded.

Maybe will I have to wait for build 716 to have my problem sorted. BTW, this new feature will be helpful in my case!

BiaB2024 64bit last build (desktop app), Win11 Pro 23H2, Intel i9 13900 24-core, 64GByte RAM, RME Fireface 800, Steinberg UR12, Cl1, Studio One 6, Samplitude Pro