KVR Audio

BlackRooster · Post by **BlackRooster** » Tue Apr 15, 2025 10:11 am

Christian_D wrote: Sun Apr 13, 2025 8:02 pm Does this new version still use the wrapping system where it would wrap the AU, AAX formats?

No, it is single installers per format.

Calagan · Post by **Calagan** » Tue Apr 15, 2025 11:05 am

Does it uninstall automatically the previous all-in-one plugin format or do we need to do it manually?

telecharge · Post by **telecharge** » Tue Apr 15, 2025 11:10 am

Calagan wrote: Tue Apr 15, 2025 11:05 am Does it uninstall automatically the previous all-in-one plugin format or do we need to do it manually?

You'll need to do it manually.

zvenx · Post by **zvenx** » Tue Apr 15, 2025 12:54 pm

This has to be one of the worse installers ever.. at least on mac, haven't tried pc yet..
at the very least it should be in alphabetical order and include the manual as part of that installer.. to have to sort thru the installer's list for both the plugins you have licenses for and their manual, is too much for me..

and to top it all, after all these years waiting for vst3 not to have automatic plugin migration.. no, just no...
rsp

BlackRooster · Post by **BlackRooster** » Wed Apr 16, 2025 11:43 am

zvenx wrote: Tue Apr 15, 2025 12:54 pm This has to be one of the worse installers ever.. at least on mac, haven't tried pc yet..
at the very least it should be in alphabetical order and include the manual as part of that installer.. to have to sort thru the installer's list for both the plugins you have licenses for and their manual, is too much for me..

and to top it all, after all these years waiting for vst3 not to have automatic plugin migration.. no, just no...
rsp

Fair enough. We are sorry for not fulfilling your expectations. This framework migration has been quite a stunt for us.

We are adding your suggestions to our list of things to patch asap. Thank you!

zvenx · Post by **zvenx** » Wed Apr 16, 2025 12:52 pm

Thanks.
I did do the pc install eventually, at least there the manual is included and for the most part I believe it is alphabetically sorted which makes it easier to exclude the ones you don't have license for.

rsp

zvenx · Post by **zvenx** » Wed Apr 16, 2025 1:46 pm

Also why are you putting stuff here:
Can I move it to a more traditional place?
rsp

BlackRooster · Post by **BlackRooster** » Thu Apr 17, 2025 7:14 am

zvenx wrote: Wed Apr 16, 2025 1:46 pm Also why are you putting stuff here:
Can I move it to a more traditional place?
rsp

That is interesting - we did not see this behaviour before. Can you please contact helpdesk @ blackroosteraudio.com? We might have a bug here.

tappert · Post by **tappert** » Thu Apr 17, 2025 8:54 am

BlackRooster wrote: Wed Apr 16, 2025 11:43 am This framework migration has been quite a stunt for us.

Hi,

out of curiosity, is it an home made framework or something like JUCE?

dastewart · Post by **dastewart** » Fri Apr 18, 2025 11:26 am

Whoah?! I have plenty of BRA plugins and didn't realise they'd finally gone to VST3.

However, as somebody who never complained about VST2 I'm not sure where to be excited or not. Is there any particular advantage in migrating to the (potentially buggy) VST3 versions?

For info I'm a windows/Studio One user

Funkybot's Evil Twin · Fri Apr 18, 2025 4:56 pm

dastewart wrote: Fri Apr 18, 2025 11:26 am Whoah?! I have plenty of BRA plugins and didn't realise they'd finally gone to VST3.

However, as somebody who never complained about VST2 I'm not sure where to be excited or not. Is there any particular advantage in migrating to the (potentially buggy) VST3 versions?

For info I'm a windows/Studio One user

Steinberg is literally force-killing VST2. So it's only a matter of time when BRA and other devs will say, "hey, we can't distribute VST2 plugins any longer" and they're not supposed to be making new ones. So the entire industry is moving off of VST2 as a result.

It's in your long-term interests to start migrating to VST3 if you plan on opening projects you're working on today, years down the road. So, that should be reason enough for everyone to start migrating to VST3 or CLAP.

telecharge · Post by **telecharge** » Fri Apr 18, 2025 5:10 pm

Funkybot's Evil Twin wrote: Fri Apr 18, 2025 4:56 pm Steinberg is literally force-killing VST2.

The not-so-funny thing is Steinberg's Cubase is the only host that hangs when scanning my VST3s, and their US Support was absolutely useless.

Dialextremo2 · Post by **Dialextremo2** » Fri Apr 18, 2025 9:42 pm

tappert wrote: Thu Apr 17, 2025 8:54 am
BlackRooster wrote: Wed Apr 16, 2025 11:43 am This framework migration has been quite a stunt for us.
Hi,

out of curiosity, is it an home made framework or something like JUCE?

Hi, this is now using JUCE.

dastewart · Post by **dastewart** » Sun Apr 20, 2025 9:13 am

Funkybot's Evil Twin wrote: Fri Apr 18, 2025 4:56 pmIt's in your long-term interests to start migrating to VST3 if you plan on opening projects you're working on today, years down the road. So, that should be reason enough for everyone to start migrating to VST3 or CLAP.

Yeah, good point, I guess VST2 will disappear at some point so may as well move on to VST3 plugins that should be around for longer.

Downloaded the VST3 versions of my favourite BRA plugins.

Calagan · Post by **Calagan** » Tue May 20, 2025 9:22 pm

Am I the only one to have this issue ?
After this vst3 update, my sessions can't recall old vst2 instances of Black Rooster plugins. I can use the new vst2 versions without issue if I start a session from scratch but when I recall an old session, Live doesn't recognize the old vst2 versions I put a little bit everywhere, like if the new vst2 versions did have a completly different plugin ID compared to before.

I'm on Ableton Live 12.1.5 / MacOs Sonoma 14.7.6
Live doesn't even know what to recall and tells me "unknown plugin" with all my vst2 instances.

I must say, it's a HUGE issue not being able to recall old sessions !

Black Rooster -> VST3