hey everyone
i went to use my Cocktail expansion for the first time in a long while and noticed that BFD seems not to know that i have it.
can anyone suggest how i can get Cocktail back on the list of available kits? i’m able to use many of my BFD2-era expansions and core kits, so i don’t believe that its vintage is the problem (altho it might be…)
my impression that it ought to still be viable is supported by the fact that it is present in Set Up Content Locations, and is marked “Authorized…”
but BFD3 itself seems not to know that it’s there.
thanks!
ohhhh-kaaaaayyyy… here’s my workaround:
i copied the Cocktail content folder into my Documents directory and re-scanned. Cocktail kit pieces now show up in the BFD browser and appear in the filter categories as well.
i’ve seen this before: some things just want to live in Documents, even if i would rather not have them there. but – whatever works, i say!
That’s weird. I know in the past I’ve had issues with grooves and presets needing to be in a specific location, but not the actual expansions. I guess the good thing is it’s not like a 90GB library like DF, taking up space on your system drive.
yeah, right? naturally i would prefer that it live on my streaming drive, and i don’t quite understand why it was recognized, yet not “there.” but ok, 3.5 gig, i can be flexible.
What you could try is… leave the physical installation of the expansion on your main drive and copy it back to your external. In the LM, or software center, remove the path from the main drive and try adding it again, pointing to the external. See if it locates it this time. Perhaps it was just some weird, temporary bug? If so, then you can delete the expansion data from the main drive.
clever! now i wonder if an alias on the system drive would work… (but i’m guessing, ummm, no.)
Hmm… that’s another option. I’ve never tried that. The other obvious first choice would just be to restart the computer and see if that straightens out whatever got wonky. Another thing you could try is deleting the DataPaths.xml, in case it got corrupted.
The other obvious first choice would just be to restart the computer and see if that straightens out whatever got wonky.
i always power all the way down at night (call me old-fashioned, but…) – anyway i’m not sure restarting would iron it out.
i know from using Digital Performer that it can “see” aliases just like any other asset and goes right to the source file, but… that’s DP for ya.
the suggestion about DataPaths.xml is very interesting, please let me know where that file is located. the only thing that makes me nervous about that is that i put a bit of effort into restoring my access to some BFD2 kits that i adore (fibes!) and am reluctant to risk losing them. maybe tho, if i feel adventurous… i guess i could always just move the .xml file to another place and put it back if i get too far into the weeds?
users/Library/Application Support/BFD Drums/BFD3/DataPaths.xml
Definitely make a copy before deleting.
many thanks!
i would tend to move it to another location first rather than delete… keep the original but “de-activate” it. however i see the point that if it’s corrupt, then why use it…