Is the core library the same for BFD3.5 and BFD3.4.5.28?

[jancivil]

- you can only use it online, no more off line.

This is not true.

it checks product authorizations every time you load a project which takes longer than actually loading the project (smh)

Here if wifi is on it takes 30 to 40 seconds. With wifi off it doesn't do this. It says it does the check but it took like a second. The preset I loaded subsequently happened fast AF. The performance is actually stellar.

But for anyone that acquires this, know what you're doing, inMusic knows basically nothing about BFD Drums in my experience thus far. Ask somebody on a forum or that if stumped.

...
most definitely not working offline here and continues to take an excessive amount time to load. fyi, dedicated Win10 Pro production system which boots up and stays offline except for upgrade downloads [...]

Apologies, I should have said it works with no wifi HERE.

noting reports of successful installations elsewhere,

could be a combination of minor bugs and/or "synchronization/conflict" issues with previous installations but hard to tell what to expect without any deets on exactly what "authorization" process they're trying to enforce. still a wip...

Well, a bug means anyone with the same basic setup can replicate it. IME, a lot of people do not follow, or know of best practices as per installing libraries for it. So it's a corrolary of Sturgeon's Law, 90% of everything you hear is user error. I hsd 16 expansions and Core library comng in.
I have experienced not only zero "conflicts" but I didn't have to be proactive at all, literally all of it was automatic. I don't think that can be blamed on much else frankly. I guess that I can use it with wifi off could be down to OS. Don't tell inMusic about it, they might fix/s that.

I don't know anything except 2 or so years ago before beta was an idea Drew, the sort of chief here said the 'login had to happen by 90 days' sitch was probably going to be it.

[jancivil]

what I have from them works with no wifi.

Only the free ones do.

just taking ze piss, eh

---

Screenshot 2025-03-11 at 3.46.14 PM.png

---

makes no sense a plugin that uses iLok is going to need to be online, as iLok doesn't have to be.
the inMusic BFD3.5 thing is not normal, to my experience anyhow.

[BazJacuzzi]

+1 for ilok. People hate on it, but my god this just shows how much worse it can be.

[telecharge]

+1 for ilok

The most damning rebuke yet.

[jens]

makes no sense a plugin that uses iLok is going to need to be online, as iLok doesn't have to be.

They're iLok-dongle and Cloud, but sadly don't allow machine-authorization, so Pace needs an internet-connection indeed in order for them to work. There's other vendors who do it like this too, e.g. McDSP.

https://paceap.com/ilok-cloud/

[KIMCHRISTOPHER]

ilok cloud to me is the same as saying: "Hey, don't use my plugins anymore, okay? Don't be such a fool!"

Companies that prioritize anti-parasite protection over user experience are completely backward and stuck in time, and will obviously die at some point.

No matter how complex your protection system is, it can always be bypassed. So why not simplify it for everyone, a serial number linked to an email, a first check and that's it.

There are so many plugin options on the market today that, honestly, it's become too complicated, I'm stopping using them.

[paramita123]

After all the feedback here I ended up buying BFD 3.5, yay !
After half an hour play I can say it is not so hard to setup and overall positive.

Load time is slow at first but fine, then great experience for now.
I am collating a growing list of feedback on UI and UX, but overall BFD seems to be good value for money.
Expect a fairly comprehensive interface, this is not UJAM. Do your research, check out YT videos on 3.5.
Cheers to KVR friends for the great sharing.

[dlandis]

I went through all my snares (using only the "Snare On" setting) to find out which were exhibiting the buzz/roll not cutting off bug I was describing earlier. I am posting the results. I think these are fairly-to-very accurate but YMMV. I hope this helps. The idea is that if a snare has a "red x" on it, it has the bug. Some do seem to have it worse than others (the signature snare expansions are pretty bad, as are the Sleishman snares, which is a pity as I love these. It's probably why I noticed the bug so early.) There are indeed fourteen of these lists, so I may have to post twice. I'm hoping this helps someone (sorry for the length of the posts; just trying to be thorough.)

[dlandis]

Here's part 2:

[jancivil]

https://paceap.com/ilok-cloud/

I have around 400 activations, 0 on the cloud. I used to have wifi that never died, then I didn't and I had to buy a dongle. Yes, cloud activation will tend to mean wifi on

VSL support advised to not have wifi on on a machine networked via ethernet. Actually he said on either host or 'slave' but the context was cloud activation

[sonidomolino]

...
Well, a bug means anyone with the same basic setup can replicate it. IME, a lot of people do not follow, or know of best practices as per installing libraries for it. So it's a corrolary of Sturgeon's Law, 90% of everything you hear is user error. I hsd 16 expansions and Core library comng in.
...

totally agree, we swap projects on a regular basis which is why we're all over best practices and even our oldest systems (10+ years) run like champs. 24+Core expansions on the system here, everyone else is at least 12+. for the record, all issues resolved atm with real support from InMusic, loading and running as expected/hoped for and feeling a bit more positive for the first time since the original L/M disasters (jme). still some minor gui issues/improvements that would help, but starting to pull up older projects w/o any issues.

would be fine if the authorization check is skipped when offline as that's our default mode. only been online to update and debug which is why i was getting hammered with that every single time.

still need a clear statement on what the user can do to manage the authorization process. done a number of location sessions over the last few years which have lasted for weeks w/o reliable (if any) internet access. and totally screwed at least twice by "de-authorization" despite doing everything possible to set a known good start date.

and as a customer, still insisting on the right to use my considerable investment in the event of any disruptive business terms & conditions. kinda smh at how amazing the latest technology is only to be cut off at the knees by some clueless drm.

[jancivil]

I don't know except my own experience, here BFD3.5.0.49 does work offline. It feints "checking for login" IE., it can't, but it proceeds launching.

[sonidomolino]

here BFD3.5.0.49 does work offline

same actually, with Wifi/LAN disabled, would be fine if it stays that way. the old l/m does not run at all on my system, possibly a problem with a fairly recent Win10 update/MS VC++ redistributable, putting any further debug on hold, hoping for the best with 3.5 for now.

[jancivil]

I'm copasetic, it works here with no glaring issues at all, although using it in VE Pro is not happening, it will not undock and I need things to have independence from the mixer all the time. I confirmed Landis' snare bug on three (it was all three I checked) snares, all in that list.

[BazJacuzzi]

The snare drag issue predates 3.5. I distinctly remember it, and when I briefly rolled back after 3.5 I confirmed it's not working on 3.4 (can't say which snares, I only checked a few, it's possible more are broken now).

FWIW I'm back on 3.5 because some of my old projects wouldn't load after rolling back, but they all do on 3.5 (this is a different experience to a lot of people).

I haven't updated the library though, and I'm feeling like I won't given how badly the rest of this process has gone.