Black Rooster -> VST3

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
RELATED
PRODUCTS

Post

I just checked my x86 folder and yes there are VST3s there. Didn't realise this was a thing so deleted them.

Post

The VST(2) installer also automatically installs 32-bit copies to the default "Steinberg" folder.

Black Rooster should really update their installer and give us options for formats and paths.

Post

Sound_Bear wrote: Sat Apr 12, 2025 11:48 pm Do the v3 VST installers for Windows still include 32-bit?
Yes, they do.
Black Rooster Audio
https://blackroosteraudio.com
Wuppertal, Germany

Post

BlackRooster wrote: Sun Apr 13, 2025 8:33 am
Sound_Bear wrote: Sat Apr 12, 2025 11:48 pm Do the v3 VST installers for Windows still include 32-bit?
Yes, they do.
Thanks. To clarify, since others are complaining about these: I appreciate and still use them.
Selling: Softube custom bundle; Zynaptiq Wormhole

Post

telecharge wrote: Sun Apr 13, 2025 5:10 am The VST(2) installer also automatically installs 32-bit copies to the default "Steinberg" folder.

Black Rooster should really update their installer and give us options for formats and paths.
Apart from taking a minute, are there any potential problems caused by manually moving the dll files to one's preferred folder? I've done this with several plugins because one of my most needed 32-bit hosts only allows for one plugin location to scan; never encountered any problems with that so far.
Selling: Softube custom bundle; Zynaptiq Wormhole

Post

jens wrote: Sun Apr 13, 2025 12:54 am
Sound_Bear wrote: Sat Apr 12, 2025 11:48 pm Do the v3 VST installers for Windows still include 32-bit?
Oh yes, good question - that's a royal PITA and a half...
Why? Apart from deselecting them during installation, what problems does it cause?
Selling: Softube custom bundle; Zynaptiq Wormhole

Post

telecharge wrote: Sun Apr 13, 2025 5:10 am The VST(2) installer also automatically installs 32-bit copies to the default "Steinberg" folder.

Black Rooster should really update their installer and give us options for formats and paths.
On Windows, there is a standardized registry key for VST2 plugins. It’s a shame that not everyone uses it.

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\VST]
"VSTPluginsPath"="C:\\Vstplugins\\64"


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VST]
"VSTPluginsPath"="C:\\Vstplugins\\32"
The folders and paths don’t have to be “C:\Vstplugins\etc” of course. They can be whatever the user sets them to.

The ‘VSTPluginsPath’ is checked by many installers to initialize the default installation path, and by many DAWs to locate the primary VST plugins folder.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP

Post

@BlackRooster Would be a good time to reset all trial licences.

Post

Sound_Bear wrote: Sun Apr 13, 2025 9:16 am
telecharge wrote: Sun Apr 13, 2025 5:10 am The VST(2) installer also automatically installs 32-bit copies to the default "Steinberg" folder.

Black Rooster should really update their installer and give us options for formats and paths.
Apart from taking a minute, are there any potential problems caused by manually moving the dll files to one's preferred folder? I've done this with several plugins because one of my most needed 32-bit hosts only allows for one plugin location to scan; never encountered any problems with that so far.
Not that I'm aware of. It's just an FYI for those who are concerned about such things -- pro or con.

BTW, deselecting 32-bit is not an option on Windows, if you didn't know.

Post

jamcat wrote: Sun Apr 13, 2025 9:43 am
telecharge wrote: Sun Apr 13, 2025 5:10 am The VST(2) installer also automatically installs 32-bit copies to the default "Steinberg" folder.

Black Rooster should really update their installer and give us options for formats and paths.
On Windows, there is a standardized registry key for VST2 plugins. It’s a shame that not everyone uses it.

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\VST]
"VSTPluginsPath"="C:\\Vstplugins\\64"


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VST]
"VSTPluginsPath"="C:\\Vstplugins\\32"
The folders and paths don’t have to be “C:\Vstplugins\etc” of course. They can be whatever the user sets them to.

The ‘VSTPluginsPath’ is checked by many installers to initialize the default installation path, and by many DAWs to locate the primary VST plugins folder.
Not sure if this is for me, Black Rooster, or KVR in general, but the problem here is that the installer doesn't honor that path. Is uses the Steinberg VST defaults.

Post

Confirmed re: VST2 installation path, and yes, it's not optimal, but no big deal.

I've noticed a change from v2 to v3 that might be good to know for one or two old-school DAW users: The plugins are now called up with an entry function "VSTPluginMain()". As far as I know, only very few VST2 plugins require this (maybe like 2 %, the main other ones I know of being Fuse Audio and legacy Pulsar Audio versions), so it usually goes unnoticed, but VAZ Modular (and possibly some other old 32-bit hosts) don't do this correctly, so one needs to use a wrapper like Blue Cat Patchwork or DDMF Superplugin/ Metaplugin to host these plugins. Again, no big deal, just sharing this detail here in case anyone encounters it unprepared.
Selling: Softube custom bundle; Zynaptiq Wormhole

Post

Sound_Bear wrote: Sun Apr 13, 2025 9:18 am
jens wrote: Sun Apr 13, 2025 12:54 am
Sound_Bear wrote: Sat Apr 12, 2025 11:48 pm Do the v3 VST installers for Windows still include 32-bit?
Oh yes, good question - that's a royal PITA and a half...
Why? Apart from deselecting them during installation, what problems does it cause?
right, I was talking about the plugins in the BR-folder that's in the "Program Files"-folder (Windows) which I had assumed are required (since at least in the past the BR stuff was shell-based).

But I just tried it and it's safe to simply delete the whole folder in its entirety, so it seems I could have spared myself the tedious task to manually delete every 32bit file in its dedicated sub-folder. :neutral:

Post

Does this new version still use the wrapping system where it would wrap the AU, AAX formats?

Post

telecharge wrote: Sun Apr 13, 2025 10:47 am
jamcat wrote: Sun Apr 13, 2025 9:43 am
telecharge wrote: Sun Apr 13, 2025 5:10 am The VST(2) installer also automatically installs 32-bit copies to the default "Steinberg" folder.

Black Rooster should really update their installer and give us options for formats and paths.
On Windows, there is a standardized registry key for VST2 plugins. It’s a shame that not everyone uses it.

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\VST]
"VSTPluginsPath"="C:\\Vstplugins\\64"


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VST]
"VSTPluginsPath"="C:\\Vstplugins\\32"
The folders and paths don’t have to be “C:\Vstplugins\etc” of course. They can be whatever the user sets them to.

The ‘VSTPluginsPath’ is checked by many installers to initialize the default installation path, and by many DAWs to locate the primary VST plugins folder.
Not sure if this is for me, Black Rooster, or KVR in general, but the problem here is that the installer doesn't honor that path. Is uses the Steinberg VST defaults.
It was meant for anyone it might be relevant to, Black Rooster chief among them, based on what people are saying here. :wink:
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP

Post

Calagan wrote: Sat Apr 12, 2025 4:24 pm Cool news !
I didn't receive the email yet, but it's definitely good news (I'm progressively getting rid of my vst2 installs).
Did anyone receive this email yet?

Post Reply

Return to “Effects”