VST2 v VST3 kit piece names

Steve63 · August 4, 2025, 5:03pm

I reported a bug back in November last year, but have realised that it’s not really a bug.

It’s actually Steinberg who have dropped the ability to display kit piece names in the piano roll.

This wouldn’t be such an issue if BFD3.5 included a VST2 version, then I would have a choice.

Currently, I’m sticking with BFD3.4. A) because not having kit piece names in the PRV is a game changer for me. And B) because there are no new features in 3.5 that could make me forgo having kit piece info in my piano roll.

I don’t know if the devs at Inmusic are able to address this failing, or if Steinberg themselves need to fix it, but I really wish someone would.

Steve.

marceli7 · August 4, 2025, 7:57pm

That’s a plot twist!

So… No need to wait for new version. I hope old vst2 version will work forever.

I am on Reaper, Windows version.

Steve63 · August 4, 2025, 8:25pm

I hope old vst2 version will work forever.

As long as BFD2 and BFD Eco are running under the old fxpansion licence, there is hope for BFD3.4.

That said, we’re talking about inbrands, who seem to show little regard for their product, or its user-base.

Steve

CHASER · August 5, 2025, 9:06am

EDIT:
Multiple Posts made during “Waiting for Approval” Process.

_______________________________________________________________________________

There is a VST2 included for BFDv3.5 …

Steve63 · August 5, 2025, 3:32pm

That’s odd, I don’t remember seeing an option to install VST2 when I installed it.
I’ll have to have another look.

Thanks for the heads up.

Steve

Fender_Bender · August 5, 2025, 8:11pm

What in the file info tells you that it is VST2 and not VST?

Steve63 · August 5, 2025, 8:14pm

Is that for me or Chaser?

I’m going to have a hunt to see if the VST2 .dll installed elsewhere, but I don’t recall seeing the option to install to a different folder when I installed it.

If it did install, it didn’t install to the Cakewalk VST folder.

Will have to wait until Thursday though.

Steve

SF_Green · August 5, 2025, 9:25pm

I have 3.5 installed as a VST2 also. That folder is my VST2 folder

SF_Green · August 5, 2025, 9:26pm

Also this in the Cubase Plugin Manager:

SF_Green · August 5, 2025, 10:14pm

But you will have to have re-enabled VST2 plugins to see it:

CHASER · August 5, 2025, 10:46pm

I highly doubt you’ll find any of the original Vst1 floating around..
I may have something on an the old Win machine..(Sony Laptop..350mhz 512kb RAM..10GB HDD..High End - for year 2000).

EDIT:
I found one from 1998..it is also .dll

1996 VST1 was an open source Sandbox released by Steinberg for Developiong VST..
1999 VST1 was replaced with..VST2 and it became the Industry Standard.
2008 VST3 was Introduced.

VST2 for Windows has always been a .dll file..(Dynamic Link Library) since it became the Industry Standard…
VST2 for mac has always been .vst (supposedly cross platform with Windows)

VST3 has always been .vst3.

Win = dll(Vst2) or .vst3
macOS (Intel) = .vst (Vst2) or .vst3

.vst (Vst2) is Not compatible (Rosetta) with Apple Silicon macs and Steinberg never developed a VST 2 SDK written in ARM64 for Apple silicon

As far as Future Development of VST…
I am a member of the The MIDI Association.
In 2020 MIDI 2.0 was adopted and as of last year 6 MIDI-CI (Compatibility Inquiry) Profiles were Voted/Adopted.
The past year has been focused on Drums which there will now be (2 )Drum Profiles…so there are a total of (8) New MIDI Profiles.

MIDI-CI DEFAULT DRUM NOTE MAP

Which is based on what everyone is currently using since the 1980’s.
Note there is now a Recommended Pan Position for each Instrument.

and

MIDI-CI DRUM PERFORMANCE PROFILE

This is designed specifically for Electronic Drum Kits and will allow direct communication with Drum Software.

It is past due as it was to be voted on/adopted in July 2025..

I suspect after it is Adopted and should be the last of the MIDI-CI Profiles you may see Steinberg release a VST4 SDK within the next couple years or possibly sooner.

There isn’t any literature or Documents..I only have 1 Video..

MIDI 2.0 DRUM PROFILES

If you want to follow what is going on with VST3..here is the Developer Portal

SF_Green · August 5, 2025, 11:20pm

I just checked BFD 3.5 VST2 and VST3. Neither can Create Drum Map from Instrument

I also checked BFD 2 and it still has the option to create drum maps.

From Cubase Help:

To import your drum map settings to an instrument track, the track has to be routed to Groove Agent SE or to another drum instrument that supports drum maps.

So it looks like it was BFD Drums/InMusic that dropped support for drum maps looking at this statement and the fact that neither BFD3 version works, but BFD2 does.

SF_Green · August 5, 2025, 11:41pm

Hi Chaser. When you click the link for the video, a message appears saying it’s unavailable. Clicking the YouTube icon takes you to the YouTube start page.

Steve63 · August 6, 2025, 6:03am

@Chaser Your quite right, there is a VST2 version.

So the issue with the kit piece names no longer appearing in the PRV is a problem with BFD3.5 and nothing to do with VST3.

That’s good to know.
Now I can whinge at the devs team for not fixing it after almost 9 months.

Every version I have owned from BFD2, BFD Eco and BFD3, have all supported this feature.

It’s bordering on a game changer for me.

Steve