I got a quite long boot time of about 15 seconds on one of my 2 computers running Bb 2020 (On the other PC Bb just boots in less than 6 seconds).

The BootupLog.txt file shows that the "Maxplugins" function takes more than 10 seconds to complete:



What could possibly be the cause for this? I've tried different things like uninstalling DX plugins, but to no avail.

Any idea?

Can you copy the contents of C:\bb\Data\Logs\PluginScanLog.log and post it here?

Try white listing or excluding the BIAB executable from you AV to keep it from jumping in each time it starts - just an idea.

Here we go Blake:
----------------------------------------------------------
Plugin Scan Log

Calling Windows FFilterMapper2.EnumMatchingFilters...
... Windows FFilterMapper2.EnumMatchingFilters succeeded

Counting candidate plugins in the Enum...
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
Counting plugin GUID {EE521163-7F20-49F0-A6DB-3BF438397691} ...
FriendlyName = PG Dynamics
Counting plugin GUID {F8388A40-D5BB-11D0-BE5A-0080C706568E} ...
FriendlyName = Infinite Pin Tee Filter
Counting plugin GUID {00000000-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Chorus
Counting plugin GUID {00000001-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Delay
Counting plugin GUID {00000002-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Distortion
Counting plugin GUID {00000003-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Equalization
Counting plugin GUID {00000004-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Flange/Wah-Wah
Counting plugin GUID {00000005-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Amplitude Modulation
Counting plugin GUID {00000006-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Reverb
Counting plugin GUID {00000007-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Stutter
Counting plugin GUID {00000008-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Dynamics
Counting plugin GUID {00000009-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Graphic EQ
Counting plugin GUID {0000000A-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Noise Gate
Counting plugin GUID {0000000B-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Time Stretch
Counting plugin GUID {0000000C-0F56-11D2-9887-00A0C969725B} ...
FriendlyName = ExpressFX Audio Restoration
Counting plugin GUID {026D0AA0-9BB9-11D0-AEBC-00A0C9053912} ...
FriendlyName = Multi-Band Dynamics
Counting plugin GUID {23C9F225-40EC-11D2-9D36-00C04F8EDC1E} ...
FriendlyName = Track Compressor
Counting plugin GUID {260DF3E1-AC77-11D2-9E93-00C04F68BE44} ...
FriendlyName = Dither
Counting plugin GUID {28D9F1E0-6ECC-11D0-AEBC-00A0C9053912} ...
FriendlyName = Chorus
Counting plugin GUID {39224540-6F92-11D0-AEBC-00A0C9053912} ...
FriendlyName = Distortion
Counting plugin GUID {3F901A20-79BE-11D0-AEBC-00A0C9053912} ...
FriendlyName = Gapper/Snipper
Counting plugin GUID {54F29260-79B1-11D0-AEBC-00A0C9053912} ...
FriendlyName = Simple Delay
Counting plugin GUID {607682E0-6E21-11D0-AEBC-00A0C9053912} ...
FriendlyName = Reverb
Counting plugin GUID {7298A3E0-78EE-11D0-AEBC-00A0C9053912} ...
FriendlyName = Multi-Tap Delay
Counting plugin GUID {869419DD-501F-11D3-8CDC-00C04F6B8E4C} ...
FriendlyName = Track Noise Gate
Counting plugin GUID {8B7226EE-4584-11D1-B4CB-00A0C9270A10} ...
FriendlyName = Graphic EQ
Counting plugin GUID {8CB69A0A-10E8-11D2-9B89-00104B8D13C2} ...
FriendlyName = Track EQ
Counting plugin GUID {9E3E4540-8339-11D0-AEBC-00A0C9053912} ...
FriendlyName = Smooth/Enhance
Counting plugin GUID {A6A78627-D619-48BF-AD26-0C6B44B5C7D8} ...
FriendlyName = Resonant Filter
Counting plugin GUID {A8448720-96FD-11D0-AEBC-00A0C9053912} ...
FriendlyName = Parametric EQ
Counting plugin GUID {B97C0F22-196D-11D1-B99B-00A0C9053912} ...
FriendlyName = Time Stretch
Counting plugin GUID {B97C0F23-196D-11D1-B99B-00A0C9053912} ...
FriendlyName = Noise Gate
Counting plugin GUID {D616F3E0-D622-11CE-AAC5-0020AF0B99A3} ...
FriendlyName = Paragraphic EQ
Counting plugin GUID {D6802BA0-A056-11D0-AEBC-00A0C9053912} ...
FriendlyName = Vibrato
Counting plugin GUID {EB6213DB-08FF-4510-9F8D-3058B0ECE4C6} ...
FriendlyName = Pan
Counting plugin GUID {ED1B4100-93BE-11D0-AEBC-00A0C9053912} ...
FriendlyName = Pitch Shift
Counting plugin GUID {EE38CA88-D78E-4BFB-B05E-577892730C83} ...
FriendlyName = Volume
Counting plugin GUID {F09F6980-7845-11D0-AEBC-00A0C9053912} ...
FriendlyName = Flange/Wah-wah
Counting plugin GUID {F3B8E880-B4E0-11D0-AEBC-00A0C9053912} ...
FriendlyName = Graphic Dynamics
Counting plugin GUID {FDB0D300-6F82-11D0-AEBC-00A0C9053912} ...
FriendlyName = Amplitude Modulation
Counting plugin GUID {17CCA71B-ECD7-11D0-B908-00A0C9223196} ...
FriendlyName = Convertisseur en T/site-à-site
Counting plugin GUID {17CCA71B-ECD7-11D0-B908-00A0C9223196} ...
FriendlyName = Convertisseur en T/site-à-site
Counting plugin GUID {005FE3F8-1F86-437B-B98F-0A4FDD62C085} ...
FriendlyName = PG Five Band EQ
Counting plugin GUID {025FB77D-234B-48AA-A144-3E319BCF49F2} ...
FriendlyName = PG Distortion
Counting plugin GUID {2E2973E2-D3C3-43E3-842D-8B9E3165EF65} ...
FriendlyName = PG RTA
Counting plugin GUID {47397F9D-A460-4543-8287-F5EBD5F67C09} ...
FriendlyName = PG Guitar Amp
Counting plugin GUID {49BEE1AA-A415-4ABD-A984-8906043286D4} ...
FriendlyName = PG Flanger
Counting plugin GUID {4F58CE3B-C1C7-4A6A-97E8-6E66F46862F0} ...
FriendlyName = PG AutoWah
Counting plugin GUID {8010C341-6D4C-4390-B828-E4D246C3DDB2} ...
FriendlyName = VEGAS Wave Hammer Surround
Counting plugin GUID {9C5EB07B-D7E0-4D77-A9BF-018452F93B03} ...
FriendlyName = PG Reverb
Counting plugin GUID {9D441A77-7E63-4E02-8E57-BD944BBF524D} ...
FriendlyName = PG RingMod
Counting plugin GUID {A31E61FC-DB09-429F-9B69-1E5A2BFC61EB} ...
FriendlyName = PG PeakLimit
Counting plugin GUID {B1669C16-3A3D-4F07-A699-EFCA69B9DDD3} ...
FriendlyName = PG Echo Chorus
Counting plugin GUID {C1F400A0-3F08-11D3-9F0B-006008039E37} ...
FriendlyName = SampleGrabber
Counted 56 plugins successfully.
... 56 candidate plugins were counted.

If the number of plugins did not change since the last successful scan, this is an error-free end of the log.

----------------------------------------------------

What are the hardware spefications of the slower computer?

QuadCore Intel i5-3330 / 8Go RAM / Windows 10 Home / 4To HD + 512Go SSD

Thanks MusicStudent, tried that already but no luck with it

Other things I've also tried:

- Disabling all DX plugins using "InstalledCodec" from Nirsoft
- Renaming / Recreating 'Preferences' folder
- Tried switching to MME / WAS instead of ASIO audio driver (My soundcard is a Steinberg UR12)
- Applied last Bb Patch (build 715)

Still no luck ;(

Nevertheless after this long boot time Bb seems to behave normally...

Have you tried disabling everything running in the background? Things like anti-virus, anti-malware, cCleaner, etc, as well as disabling your Ethernet card via the device manager?

How about it you add the file safemode.txt to the Preferences folder to simulate factory settings?
Edit - Actually ignore that, I see you already tried it.

Does it make a difference if you add the file MaxPluginsToScan.txt to the bb folder, with a single line of text in it:
max=0

(Delete or rename this file after the test)

Also, does the slow bootup only happen if your computer has been idle for a while?

Hello

Did you sort this issue?

I had something similar. BIAB (on external HDD) would take up to 5 minutes to start and it was driving me crazy. After much hair pulling I found the culprit. I had to (temporarily) disable real time protection on WIN 10. Once I did that it starts as you would expect. The only thing is - I need to remember to disable real time protection each time I go to use BIAB. Windows will prompt you to turn on real time protection again and I do that after I have finished my session with BIAB.

Your problem might be different but this just may work for you too.

Thanks

Brendan

Thanks Bredan,
Actually, Windows Defender is not even active on my PC...

Thanks for your suggestions Andrew!

Having the MaxPluginsToScan.txt (with the one line you've suggested) in the bb folder does not change anything.

And, no, this problem does not happen when my computer has been idle for a while...

Yes MarioD, I did all that before posting...

I haven't read through all the posts so this may have already been mentioned. Just in case, though...

Have you checked that enable fast boot-ups is active?

Yes, that's also a good one Noel. But 'Fast bootups' is already 'on' on my system (by the way, ticking or not ticking this option doesn't seem to make much difference).

Thank all of you guys for all these suggestions:)

A question, how much free space do you have on the drive(s) that contains BiaB, RDs and RTs?

An almost full HD can slow everything down.

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.

You're right Mario, but I still have plenty of HD space on the drive on which I'm running Bb (more than 200 Go in fact)...

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!

Make sure the MaxPluginsToScan64.txt contains:
max=2

Or "max=0" or another number you are testing. If the MaxPluginsToScan64.txt file does not contain the proper contents, it will not control the number of plugins being scanned, and the MaxPluginsToScan64.txt will be erased.

Hi Blake,

I confirm I've entered the correct line in the MaxPluginsToScan64.txt file i.e.
max=2

Actually, I've also tried 'max=0' and some other combinations...

On each Bb bootup the file is automatically deleted and no change occurs in the plugin count.