For reasons (my stupid mistake), I had to restore my Windows 10 C drive to an image from a week or so ago.
BFD 3 (latest VST 2 version) was unauthorised, which is fair enough, albeit annoying.
Authorising via the InMusic app seemed to work, although I needed to Deactivate then Activate again, and all my expansion packs say Activated now, but there are a lot of drums that show yellow triangles on which didn’t last week - some of them make sounds, some don’t. If I try to rescan the folders they are in, BFD3 just sits there and never seems to complete (I left it for about 6 hours overnight and it was still sitting there).
Any thoughts/suggestions?
I’m wary of going to the VST 3 version, not because of any aversion to VST 3, but because I believe I can’t have the VST 2 and VST 3 versions both installed concurrently, and the VST 3 version doesn’t migrate from the VST 2 version in existing projects.
Try removing all content paths and then adding them again. Any small hardware change, or using a cloned drive will trigger the authorization of your products again. Yeah, sometimes arbitrarily, it will hang when scanning content and you have to force-quit. I’m not sure where the file is on Windows, but if you still have trouble, you can try and track down the content paths preferences (not sure how it’s referred to on Windows) and trash that. Might be in App%Data/Roaming/BFD3, etc. Add your paths again.
I got it in the end thanks to your suggestions (although not directly but it pointed me in the right direction): the kitpieces file had references to some BFD (original!) drums with the same name as the BFD3 equivalents. I deleted the file and let BFD3 rebuild it and all works.
Now why it has worked for years despite previous reauthorisations but not this one…
FYI, in using Cubase I have had many vsts installed in both vst2 and vst3 for the same plugin. Some plugins install both, whether you want them to or not. Anyway, I haven’t had a problem selecting just the vst3 to insert. The vst2 hasn’t messed anything up.
There are many advantages to VST3. I would recommend switching to this format.
I did update to the VST3 version today - somewhat painful as the reauthorisation for some of the kits took ages!
I’d flag two issues with it:
Despite a new version of the VST 2 dll being installed at the same time, it doesn’t do the “replace with VST 3 version” that is supported, which surprised me (also means I have 2 VST 3s in my plug-in list unless I hide the VST 2 version - not the end of the world but a missed opportunity IMHO);
The authorisation on every insertion is sloooow and annoying (I’ve got a ~500Mb internet connection and it takes its sweet time); that’s on every project I open, even if I don’t close my DAW between loads (at least once per DAW session would have been OK); I’ve seen someone else mention this on the forum somewhere from memory - anyone know if this is being improved?