The future of BFD license - a cautionary tale

Did you ever get a reply about this?

I got a full refund, finally.

1 Like

Me too, I feel sorry for the developers who get shifted from one company to the next and have dedicated a lot of their life to this product.
I like the product but it’s lack of VST3 plugin for my DAW is going to force me to dump, That’s down to management committing the required resources but it looks like from a customer view that InMusic have no track record in that regards.



Just to play devils advocate, isn’t it naive and foolish of DAW makers to drop support for VST2 when so much software doesn’t yet have a VST3 version?

Cakewalk’s bandlab has happily supported both VST2 and VST3 for quite a few years now so why are Cubase and other companies abandoning it?


Well, first off, Steinberg has announced the drop of VST2 support with more than a year’s warning, and even so, I would doubt the next Cubase will come out without VST2—although I for one certainly hope so!

In that sense, there’s plenty of time to either simply move your plugin to VST3 “as is” or actually take the opportunity to develop a meaningful upgrade to it.(obviously depending on funds).

That said, just like 32-bit, so will VST2 surely live on beyond the cutoff point via plugin “bridges” and/or loaders like BlueCat’s, metaplugin etc. Not to mention that there’s no reason you can’t have several Cubase versions installed, as many do for backwards compatibility.

But you can’t expect your software to be both moving forwards and constantly looking backwards. At some point you need to bounce your channels and move on (I mean, even VST3 plugins from a few years ago are now obsolete or have new versions).

In the sense that a move to a pure VST3 environment means a more stable DAW, better workflow and new features, I say the sooner the better. There’s not a single plugin that I can’t live without or can’t find an equivalent, but even if there was I would trade it in a heartbeat for a faster, more robust DAW.

Re Steve’s “devils advocate view” I would say by way of response VST 1 is not in general use anymore because operating systems and daws move on.

Vst2 has reached the end of the support cycle. Of course people can still use it if they want to stick with specific DAWs and Operating systems on older hardware, but time is not going to stand still. It BFD is to continue in development for use on latest hardware then VST3 support is essential at this time. If not the writing is on the wall and if I worked there as a developer I would be looking to move on.
As a user I want to keep moving forward as I don’t want to keep with old hardware and software.


1 Like

Steinberg discontinued the VST2 SDK in 2012/13, they gave developers many years to adopt VST3.

I don’t think there’s any functional reason to drop VST2, but I’m not gonna say it’s a surprise or unexpected (frankly I’m surprised it held on as long as it did).


Obviously if including VST2 compatibility causes issues and holds back development then that’s a different story. It’s such a shame as there’s still a lot of software out there that doesn’t have a VST3 version and perhaps never will.


Here goes, backed up everything set up inMusic account with same email.
BFD2 and presets for a decade of songs in logic , praying the replacement packs to mess with that!
Downloading LM…