I wouldn't go that far, but it does saturate the network bandwidth (my remote desktop session is very slow when it's downloading). But I could run other applications, including BFD3 standalone, during this time.
Posted on the kvr forum by Drew (from BFD Drums) - this seems to solve it:
Open Registry Editor
Navigate to: Computer\HKEY_CURRENT_USER\SOFTWARE\BFD Drums\BFD3
Check for these entries: FirstRun, fxp2inm_migration, and NeedScan
If you don’t have them all, create them. They should all be string types.
Set FirstRun to ‘No’ without quotes.
Set fxp2inm_migration to ‘migrated’ without quotes.
Set ‘NeedScan’ to ‘no’ without quotes.
This will stop BFD from nagging you about copying across old files.
I wish ?
My latest: install my free library (Crush), fire up bfd3 standalone and it gets picked up and runs fine. Add bfd 1 folder to scan...finds the expansion packs OK (eventually!) but Crush data has been lost.
I've just downloaded and installed my freebie pack - does anyone else find rescanning takes an age and "hangs" the application? It's been churning away for an hour now (6/12 core 3.7GHz machine, SSD and NVMe drives, 32GB RAM, so no slouch even if not absolutely cutting edge).
Ditto (ish): I get some/all of the BFD 1/2 packs, but none of the core BFD 1/2 content. Somewhat irritating, so if anyone has a suggestion...
The BFD 1/2 serial numbers don't authorise in the new license manager, so I'm stumped.
It's also a SynthEdit synth, and these can be problematic (especially ones using older SE toolkits) - from memory, they especially didn't like having "Use Multiprocessing Engine" enabled. So I'd first suggest turning that off:
If that solves it, then you're probably out of luck as you don't want to turn this off in general, and looking for a replacement is probably your best bet.
Mine is working (yeah, I know, that doesn't help you!) on every clip I've tried it on so far (random ones, not just vocals), so it's not fundamentally broken.
There's also differences and "differences": I don't think anyone would expect 2 DAWs to perform identically, so, say a 1% difference might be well within expected differences, and there will therefore inevitably be projects which are on the border, which would run OK in one and not in the other; a 50% difference, however, is a different matter and shows that *something* is up in at least one of the DAWs.
zip files are equally (if not more so) susceptible to corruption - a single bit *can* make a zip file unusable. At least with a straight copy, you may lose one wav file (and even then it may well import) but you're way less likely to lose everything. That's about the one downside of using bundles as Noel said earlier.
Oh, and wav files don't zip well, so it's probably a waste of time ?