KVR Audio

LeVzi · Post by **LeVzi** » Fri Feb 11, 2022 7:33 am

vurt wrote: Thu Feb 10, 2022 2:43 pmlittle boats

Is it bath time ?

Debutante · Post by **Debutante** » Fri Feb 11, 2022 7:35 am

Have to check which one works. R@ reverb vst2 is bogus/buggy and only in mono for some reason - vst3 is perfect

SHall1000 · Post by **SHall1000** » Fri Feb 11, 2022 9:52 am

Thanks for the useful input guys. I have started installing VST3s and was surprised to see half of them already in the sneaky common/steinberg folder already!

chk071 · Post by **chk071** » Fri Feb 11, 2022 10:06 am

Do you mean Program Files/Common Files/VST3?

That's the default VST3 folder.

jamcat · Post by **jamcat** » Fri Feb 11, 2022 10:26 am

I only install VST3 whenever possible. There’s only a few left that I still use that aren’t VST3 at this point.

To transition, install both versions and save your settings in your plugins’ proprietary preset format in your songs then swap the VST2 with the VST3 version.

The proprietary presets should load in the VST3.

SHall1000 · Post by **SHall1000** » Fri Feb 11, 2022 2:16 pm

chk071 wrote: Fri Feb 11, 2022 10:06 am Do you mean Program Files/Common Files/VST3?

That's the default VST3 folder.

That’s the one.

SHall1000 · Post by **SHall1000** » Fri Feb 11, 2022 2:18 pm

jamcat wrote: Fri Feb 11, 2022 10:26 am To transition, install both versions and save your settings in your plugins’ proprietary preset format in your songs then swap the VST2 with the VST3 version.

The proprietary presets should load in the VST3.

Thanks for this, I shall try it.

pljones · Post by **pljones** » Fri Feb 11, 2022 5:11 pm

Program Files/Common Files/VST3

is why I don't like VST3. I like having control over where software gets installed... One of my objections to Sforzando is that it doesn't let me control where it installs stuff... VST3 seems to erode this further, from what I've seen.

legendCNCD · Post by **legendCNCD** » Fri Feb 11, 2022 6:26 pm

Using 95-100% VST2 still. Maybe its Live 10 or some plugins, but it seems we get more problems still using vst3... lets see with Live 12 then.

jamcat · Post by **jamcat** » Sat Feb 12, 2022 2:22 am

Must be Live. I know Ableton came only recently to the VST3 party and it may not be complete.

VST3 support is fully and properly implemented in Studio One and has no issues.

My experience is VST3 plugins are much more stable. It could be that plugins with no VST3 option tend to be old or neglected and in need of compatibility updates.

SHall1000 · Post by **SHall1000** » Sun Feb 13, 2022 9:26 pm

Have been slowly moving over to VST3s and am a bit surprised that some devs don’t have all their plugins available yet, the HY-Plugins sequencers being an example. Two are available two aren’t.

chk071 · Post by **chk071** » Sun Feb 13, 2022 9:29 pm

Pretty sure that, now that Steinberg made official announcement that they'll discontinue VST3 support in Cubase, the last developers which didn't develop VST3's yet will hop on board. That have a big chunk of the market, so, you better make sure to get a piece of it.

Super Piano Hater 64 · Sun Feb 13, 2022 9:46 pm

SHall1000 wrote: Sun Feb 13, 2022 9:26 pm Have been slowly moving over to VST3s and am a bit surprised that some devs don’t have all their plugins available yet, the HY-Plugins sequencers being an example. Two are available two aren’t.

Sequencer plugins in general will have a very hard time with the VST3 format. I've heard that some of them are being rewritten as hosts (which is obviously a lot of work, but is at least a path forward) but in other cases there's just no hope unless Steinberg changes course and expands the API.

crickey13 · Post by **crickey13** » Mon Feb 14, 2022 8:21 am

I have an old laptop, so I'm probably gonna keep all the VST2 plugins for compatiblity reasons. I don't need constant updates anyhow and most of this stuff runs just fine and will continue to do so for the next decade anyways.

When I move on to a new computer, I will then install VST3 and CLAP stuff if it gains footing in the plugin world as a separate format. I'm not gonna fret about this for the time being. If St*inberg drops the nuke, I will simply go full offline, 90% of the stuff I own (including my DAWs as well) isn't C/R anyways.

benzene · Post by **benzene** » Sun Feb 20, 2022 1:30 pm

NI have released Kontakt with Apple M1 support, but only for the VST3 version. This is kind of setting a deadline on VST2 support at least for Apple machines, to last as long as Rosetta 2. This may well be years, but there are real signs of VST2 becoming unsupported with this, and also from Steinberg DAWs. Fair enough, can't keep supporting VST2 forever.

Personally I'm happy to run in Rosetta for now. But, I'd like to be ready to 'go native' in good time, not the day before Rosetta 2 is unsupported. Ableton doesn't offer a VST2-VST3 migration tool, so I want to move my projects slowly to VST3 over time so I don't have one big job switching my plugin instances over.

I just noticed Guitar Rig isn't available in VST3 format at all (just tried reinstall). Maybe it'll be released in VST3 at the same time as M1 support - who knows. So I'm slowly realising that there's not that much we can do while these changes are happening. Apple Silicon, and VST2 being phased out at the same time is no doubt tying up dev roadmaps and I suspect they're having to make some hard choices.

So maybe it's best to just crack on, and hope it all works out in the end! My main hope would be a VST2->VST3 migration tool in Ableton (as other DAWs provide), as this transition has suddenly become real with the M1 updates (see Kontakt).

Context - I don't really mind fixing up old projects if it comes to that, as this is not my day job. I'm more thinking of more "serious" working musicians who are going to find things not working down the line (though granted, could be a couple of years yet).

VST2 to VST3 migration strategy.