I don’t even think the developers know what is going, cause if they did we would not find ourselves wasting valuable time (and money) posting messages here.
Looks like my mistake was keeping the license manager open after downloading the files - it doesn’t tell you anywhere that this is the case but afterward once you get through to some form of support it is my fault because I didn’t shut down the license manager seconds after hitting the play button ???
What a pile of crap !! - seriously loosing patience here !! been at it since 21st of May it’s now the 6th of June heaven help anyone who is trying to make a living with this…
BFD3 doesn’t connect to anything on start-up. But License Manager uses some websites to check whether it has access to the internet. It needs to do this to make sure it can reach our servers.
Once the next version lands, most of everyone’s problems should disappear. Tomorrow, Tuesday latest.
On mac anyways, OSX.15.7, it sure looks like having the old license manager and the new one co-existing creates an issue, a vicious circle. I don’t have fxpansion licenses for anything else, but this is a Catch-22 for those who can’t just wipe the fxpansion LM.
Here, all systems are go and have been from day 2, after an infuriating failure of the keychain the better part of day 1. But it meant for me a wholesale purging of fxpansion software.
anyway, that’s water under the bridge.
quick question, does the current version run with no issue under Big Sur on intel?
I remember seeing in late April, the next update (4.1.11) will but I need to be sure, I’m going to create a Time Machine image on an HDD first, which is not trivial.
Yeah, once they get the current set of issues sorted out, that will be my next demand. I’m holding off on Big Sur specifically for BFD3. I’m pretty sure it’s my last piece of software that needs to be validated.
Well, Drew did say around April 26 the next update will, and 4.1.11 is def. that update.
my holdout other than this is NI Reaktor, which I have only seen reports of success with, but two or three cases is inconclusive to me. But, if BFD3 does work with no issue, that one can fail and worry about it another day, I don’t think i’ve used it in a year.
I don’t have all the issues reported here, I just have the automation map trip which may never change.
looking for that quote re: Big Sur I found my posts from the first day of 3.4, I was pretty pissed off but it worked after like a day and has worked since. works offline since 4.1.1, there are no basic functional troubles.
I had little luck on Win10 (20H2) moving to 3.4.0.24 - while it did run, I some of my paid-for kits were missing.
Luckily, I had BFD 3.3.latest plugin DLL from FXpansion still on my VST Plugins dir, so I just deleted the bfddrums.com version, and could use all my kits etc.
So tonight I said I’d see if there was a later version from bfddrums.com - and there is - 3.4.1.11.
However, now, I’m getting a crash dump every time I launch BFD - both Standalone and Plugin (and it takes Ableton down badly, have to kill it).
Looking at the dump created, Visual Studio tells me “The thread tried to read from or write to a virtual address for which it does not have the appropriate access.”
Guys - you seriously need to up your game here… Don’t build crap on top of crap! Rip the guts out of whatever is broken here, please! I’d rather see stuff breaking due to oversimplification, and subsequent fixes for edge cases, than breaking due to building crap on crap…
Hi, I thought maybe the dumps would have been useful, but as I try to attach the two files:
2021.06.07 2128_25 BFD3 Crash.dmp
2021.06.07 2128_25 BFD3 Crash.txt
I get this message from this site:
“Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, heic, heif, webp, bfddownload).”
Just to make the point again - Visual Studio tells me “The thread tried to read from or write to a virtual address for which it does not have the appropriate access.”
Trying to debug your DLL in Visual Studio - best I can get from the debugger without the symbol table is:
Unhandled exception at 0x00000001806F4C4F (BFD3.dll) in 2021.06.07 2128_25 BFD3 Crash.dmp: 0xC0000005: Access violation reading location 0x0000000000000000. occurred
I’ve also profiled BFD.exe in depends.exe (https://www.dependencywalker.com/) - same message:
First chance exception 0xC0000005 (Access Violation) occurred in “BFD3.DLL” at address 0x00000001806F4C4F by thread 1.
Good news - I got a new copy in my inbox this morning from Alexander in support - BFD3.4.2 - well done chaps, it connects it downloads and works stand alone and as a Pro Tools plugin ! Not tested in great anger yet but at least things are booting up and making noises. I took the opportunity of fitting a brand new SSD drive and moved all audio and groove files I could find scattered about into it - then asked BFD to only scan the new drive. So far all is good - many thanks for the tireless work you guys must have gone through ! Faith restored
