I’ve asked this a few times and got no explanation but, if you’re BFD3 and expansions are all licensed and running fine and then you disconnect your WiFi, how then are they able to disable it?
They will need to access it so the only way I see how that could happen is if it were on a timer.
Yes they could disable BFD3 when you next try to update it but then you’d run the licence manager anyway so no issue there that I can see.
As Long as users were notified before hand and given a window in which to log in, like a week or 2 weeks at the end of a given month then that shouldn’t be too hard.
Like I said, I’m not in favour of it but it’s a whole lot better than iLok. I have no iLok products on my system and am keen to keep it that way.
Well it’s happening now where if you’re not online it doesn’t work, so same principle. Not difficult to program. I’d rather they spent that time programming a better product personally.
I’m not a huge fan of iLok, but I have enough iLok VST plug-ins to know it’s not a huge problem - none require a dongle, they’re all computer-authorised. One authorisation is less intrusive than once a week/month/year whatever the time schedule would be, I don’t care. I’ve paid for this software so stop checking up on me like some crim!
I’m not sure what this checking up on users is supposed to prove anyway. That people who have actually paid for the product aren’t doing what exactly?
That only happened as a result of us updating and installing the new licence manager and BFD3.4 , it’s not the same at all.
If I decide to take an internet hiatus for the next year or so (once the bug is fixed in the next build) I may miss all the lovely updates but they won’t be able to disable BFD3 unless as I said it’s on a timer.
Totally agree there, I’m quite baffled, if you’re using a pirated copy you probably bypass the licence manager anyway.
Which if there is an expectation of users being online, there will be, otherwise your point is ‘why does it matter if it phones home and nothing happens?’. If I update, and it expects me to be online in four weeks time, of course its got some sort of timer involved. Whats the point of the expectation otherwise.
Arguing with everyone and shoving your own speculation in there that you dont personally have a problem with isnt helping matters. Its not allaying fears, its just ‘i dont mind, neither should you’.
Arguing with everyone and shoving your own speculation in there that you dont personally have a problem with isnt helping matters. Its not allaying fears, its just ‘i dont mind, neither should you’.
[/quote]
**
Precisely. The only thing I am interesting is making the software work as it should so the developers can spend time improving it. At the moment I am stuck in 3.3. I would like to feel that I own a share in this software and that I can look forward to exciting developments. I have been looking at SD3 and have become less keen on it the more I have found out and heard. It occurs to me that I like the sound and flexibility of BFD3. I mix in Cubase and use a combination of 3rd party software to get the sounds I like. I want to continue to do this as I have done in the past working offline…
Steve,
If, following the update, they have decided to make periodic checks mandatory then code will be included to require a check in to keep the software working. No check in during a set timeframe and the software disables itself. iLok uses this for their Zero Downtime insurance (which is not mandatory)
The only problem I have, being disabled, is that I can go for up to three to four months at a time, through being ill, not being able to access my computer, and therefor the internet.
I’m not a big lover of iLok, but I use it (dongle, and computer licence) for all my Izotope stuff, so not a big problem if it went that way.
I’ve not updated yet, since migrating, I’m running ok for the time being, hopefully giving me a good window to get my new pc built and up and running.
I just hope all issues are solved quickly by those in charge and tested by the testers.
It seems the whole thing is in a bit of a mess at present and doesn’t hold good for the future (lets hope I’m wrong on that).
Thank you, at last some one has given me an explanation.
In a sense then, I think your explanation is a kind of timer which is as I’d thought.
And as I keep repeating, I think it’s a terrible idea, despite the fact that my DAW is always on line so I won’t be adversely affected.
But I would like to hear their reasoning behind it.
As some one else rightly pointed out, once you have you have licensed your copy of BFD3 and all your expansion kits that should be that. You should never be required to provide proof of the fact again.
Steve I do wish that you would not keep referring to the fact you are always online, so you won’t be adversely affected. Fine. However, it’s not helping to calm the debate. I get that this might not be an intentional issue, but it does seem less than competent for the roll out of BFD3.4 to be so beset with serious operational issues. Issues that I might add make the software un-useable for many of us.
I spend a lot of time recording and using BFD3. If I wanted to spend most of my time troubleshooting this software I would not have reverted to 3.3. I prefer to use my time making music and not doing unpaid beta work for inMusic. Given the rash of issues with the new version I am not tempted to try again. Especially considering the time it took me to get 3.4 to see all my expansions.
I know that you are a big supporter of BFD and have appreciated you during the days of Fxpansion for your help and advice.
There is a build in beta now that addresses expansion packs not being accessible when offline. Think we’ve got it now! Once it passes the beta team, it’ll go public.
Does it not work with the Legacy driver? Could you please give some more info. I have a Fireface 800 and was about to update since I’m on 1909 and am getting nagged a lot since it’s going out of support. Does 20H2 still allow Firewire?
I didn’t read this entire thread, so I don’t know if it was brought up or not. But another problem with the software needing to “phone home” to operate is, it means the software will only work as long as the “home” company continues to provide the mechanism. So if (or when) the company or its support goes away, so does your ability to run the software.
Yes. That is the major problem with this scheme. We’re only loaned our licenses for as long as the vendor says we’re allowed to use them. If we want to time-capule a machine and use it forever, using the current software and OS, we can’t.
