[SOLVED] BFD3 Drums, VST2 plugin . . . export or freeze, instant crasho !

[noynekker]

Did the most recent Sonar update, Feb 2025.

I've been working on a project last week or so, and it has been totally stable. As soon as I add the BFD3 drums plugin, and try to do a freeze track or export to WAV, I get an instant Cakewalk crash, and a pop up screen appears which specifically mentions the BFD3 plugin. 

So, I tried doing a "Replace Synth", for another drum synth I have. This works fine when trying to do a freeze track or audio export.

I realize BFD3 is now an older VST2 plugin, but it is kind of a showstopper for me, as this has been a go to drum plugin for me.

Steps to reproduce:

Add BFD3 plugin as an instrument track to a brand new cakewalk project

drag some midi notes to a track

freeze the track (or export to audio)

Cakewalk crashes instantly

 

Edited March 3 by noynekker

[msmcleod]

Not seeing any issues here with BFD3 using those steps.

[Bristol_Jonesey]

BFD3 is fine for me as well. 

[noynekker]

Thanks guys for the replies . . . so I’ve clearly got some troubles with BFD3 on my end . . .  I’ll have to investigate.

[noynekker]

@msmcleod

So, how do I roll back to my previous Sonar version (30.12.0.004 - Dec 2024) . . . because I never had this BFD3 plugin issue with my last Sonar version.

I have the .EXE file for Dec 2024 version in my Downloads folder, can I just run that to roll back, or is it more complicated ?

[msmcleod]

4 hours ago, noynekker said:

@msmcleod

So, how do I roll back to my previous Sonar version (30.12.0.004 - Dec 2024) . . . because I never had this BFD3 plugin issue with my last Sonar version.

I have the .EXE file for Dec 2024 version in my Downloads folder, can I just run that to roll back, or is it more complicated ?

If the exe is the full installer (~500Mb) , then yes - if it's an update installer (~50Mb), then no... maybe @Jonathan Sasor can send you an installer for the previous build to check whether it is indeed a 2025.02 problem.  

Given that both myself and others are not having a problem however, my gut feel is that it's not the 2025.02 release.  It's more likely a Windows update or installing something else  has upset things.  If this is the case then rolling back probably won't make a difference.

I'd advise:

1. Use the Windows system file checker to verify that your Windows installation is ok:  run sfc /scannow in an admin power-shell ( Windows Key + X, then press A).
2. Ensure the latest VC++ redists are installed.  There's a link to a bundle of the latest MS VC++ redists here: 

 

[MIDInco]

On 2/18/2025 at 10:57 AM, noynekker said:

Did the most recent Sonar update, Feb 2025.

I've been working on a project last week or so, and it has been totally stable. As soon as I add the BFD3 drums plugin, and try to do a freeze track or export to WAV, I get an instant Cakewalk crash, and a pop up screen appears which specifically mentions the BFD3 plugin. 

So, I tried doing a "Replace Synth", for another drum synth I have. This works fine when trying to do a freeze track or audio export.

I realize BFD3 is now an older VST2 plugin, but it is kind of a showstopper for me, as this has been a go to drum plugin for me.

Steps to reproduce:

Add BFD3 plugin as an instrument track to a brand new cakewalk project

drag some midi notes to a track

freeze the track (or export to audio)

Cakewalk crashes instantly

 

I don’t use BFD myself(but, I have BFD3), so I can’t directly verify whether this issue is specific to BFD3, but I have experienced compatibility issues between Sonar and other VST plugins, so I understand how frustrating these kinds of problems can be.

I recently heard that BFD3 has been updated to support VST3. If you haven’t already, perhaps updating to the latest version might help resolve the issue, especially if it’s related to VST2 compatibility.

I really sympathize with how difficult and isolating it can feel when you're dealing with an unresolved issue. I’ve had similar experiences where I struggled to find solutions, so I understand how you feel. I hope you can find a fix soon, and I’m rooting for you.

[noynekker]

3 hours ago, MIDInco said:

I don’t use BFD myself(but, I have BFD3), so I can’t directly verify whether this issue is specific to BFD3, but I have experienced compatibility issues between Sonar and other VST plugins, so I understand how frustrating these kinds of problems can be.

I recently heard that BFD3 has been updated to support VST3. If you haven’t already, perhaps updating to the latest version might help resolve the issue, especially if it’s related to VST2 compatibility.

I really sympathize with how difficult and isolating it can feel when you're dealing with an unresolved issue. I’ve had similar experiences where I struggled to find solutions, so I understand how you feel. I hope you can find a fix soon, and I’m rooting for you.

@MIDInco . . . thanks for your reply. As far as I know BFD3 is still VST2 . . . you're probably referring to a recent BFD3 VST3 version that was put forth . . . but unfortunately it's just a player version, and doesn't have the powerful features of the full BFD drum set. We're all waiting for BFD4, which will be VST3, I've heard rumblings about it, but it's so long in development, and new owners, that it may never happen ?

[MIDInco]

On 2/24/2025 at 1:42 PM, noynekker said:

@MIDInco . . . thanks for your reply. As far as I know BFD3 is still VST2 . . . you're probably referring to a recent BFD3 VST3 version that was put forth . . . but unfortunately it's just a player version, and doesn't have the powerful features of the full BFD drum set. We're all waiting for BFD4, which will be VST3, I've heard rumblings about it, but it's so long in development, and new owners, that it may never happen ?

I have confirmed that the VST3 version of BFD3 has been implemented in the latest update. As a result, you can install the VST3 version of BFD3 (version 3.5) using the inMusic Software Center.

[noynekker]

20 hours ago, MIDInco said:

I have confirmed that the VST3 version of BFD3 has been implemented in the latest update. As a result, you can install the VST3 version of BFD3 (version 3.5) using the inMusic Software Center.

@MIDInco . . . thanks very much for the response !

You are correct, with very little fanfare (even on the BFD forum), there is indeed a VST3 version 3.5 available . . . you really have to go digging to find it, but it is there.

Thanks again for the info update!

[GBTBassist]

@noynekker - just checking if the VST3 solved the crash problem as its not clear from the thread?

 

Cheers

 

[noynekker]

52 minutes ago, GBTBassist said:

@noynekker - just checking if the VST3 solved the crash problem as its not clear from the thread?

 

Cheers

 

@GBTBassist . . . my main problem was related to many  BFD updates and reinstalls over many years, and a Novation controller software that added wrappers for all my plugins. BFD was placing DLL files all over the place on my computer, and I was having to add extra VST scan paths in Cakewalk preferences VST scanning for them to work . . . BIG mess !! (VST2 dll's in the VST3 folder, big no no) I spent a day deleting / moving BFD related DLL files around. Then I came across this new BFD3 VST3 version, which fixes the future, but I still like to open and tweak older projects which use the VST2 versions. There are some checkboxes in the VST area of Cakewalk preferences that I played with regarding VST3 Migration. I think I finally got lucky . . . old and new projects are loading properly again. BIG tip, BFD3 has a setting to  automatically load a preset when opening every time . . . turn that off ! Cakewalk's PRV view does not load the  drum name mappings like it used to, but I gotta move on and make some music, fix that another day (think it's a new BFD3 VST3 bug, half baked me thinks)

. . . since you asked, LOL

Cheers