Running Studio One V3.01 x64 on Windows 7

I've got all my Waves plugins cataloged with Shell2VST, but because there's a Waveshell in my VST3 folder, my Waves VST2 plugs don't show up in the "Folder" tab of the browser (except of course under vst3).

My primary DAW being Ableton, I don't generally bother installing VST3 but I do have some Fabfilter plugs in both VST2 and 3 that aren't having this problem, which makes me think it has to do with Shell2VST.

When I moved the Waveshell out of VST3 folder, my VST2 plugins appeared in the browser the next time I opened Studio One. Well worth it to me. I need organizational freedom from the stupid waveshell more than I need VST3. I just thought I'd share this in case anyone else has a problem with their Waves plugs not showing up in S1 browser.

 

You can disable support for the different plug-in types ( AU, VST2, VST3) in the Advanced Settings/Services settings. (there´s also an opion to show both vst2+3)
Also keep in mind that turning of VST3 support means, that you can't use the Melodyne integration anymore, because only the VST3 version of Melodyne is ARA compatible AFAIK.

besides that .. vst3 is a good thing..

http://www.steinberg.net/en/company/technologies/vst3.html


cheers

 

Just delete VST3 plugins for FabFilter Stuff.

 

Hey thanks for coming to help, but you misunderstand. The Fab ones actually seem okay. That's why I thought it might have to do with the shell2vst.

I don't especially even have a problem here. I moved the vst3 waveshell, problem solved. I just figured these circumstances can't be uncommon so this might help someone new to S1 v3 (like me).

 

LOL My bad. I'm actually mean Waves not fabfilter

 

The problem with deactivating VST3 support is that it will affect all the VST3 plugins, not just maybe some specific ones that you may wanna get rid of. Moving them somewhere else is a more flexible option. Also... VST3 maybe is a good thing, but probably more for Cubase. On my S1 regardless of V2 or V3, VST3 was always crashy, buggy, etc. Examples: factory presets not showing up, weird latency compensation, automation not working on some of them, crashing S1 suddenly with no error, etc. while VST2 versions had no problems.

 

i dont know about any other DAW But in Cubase VST 3 Are for Side Chaining they have a Side Chain Button on them

 

As a recent samplitude convert, I miss their plugin wrapper terribly. VST2 plugins have a sidechain input menu

 

Never had those problem with VST3 since V2. I think is more company fault than S1.

 

So i presume that 3rd parties didn't write their VST3 version of their plugins correctly? Then it's such a shame to even make the VST3 versions just so they don't miss that format in the specs list, for the sake of plugins "impression". The thing is that their VST2 versions worked flawlessly.
The devs i got problem with their VST3s were Fabfilter, Nugen, Waves, Izotope and a few others which i don't remember right now.

 

Those are exactly the plugins i use, plus Plugin Alliance and other stuff.
-Fabfilter i had a version from 2012 release and then 1 month ago updated to the lastes but still no problems.
-Waves, i think mine should come from r20, not updated to the latest since i had some problem with activation
-Izotope, Nugen and others are coming directly from sister site.

Have you tried to turn off the service you don't need from the option pannel? Could not work, but i spended some times to get the options that fits my needs (as for Windows).

 

The mostly VST3 plugins which crashed my S1 were from NuGen. I mentioned also Fabfilter because they (like other vst3 versions supporting devs) didn't supported the "factory" presets field next to the user's presets field:



While VST3 it misses that field:



Also, the same VST2 factory field presets are available in your face on other daws as well, if i press this "lines" button in Bitwig:



The factory presets shows up right in your face. That's what i've wanted.
To be able to use the presets in multiple daws, but without using the "Open/Load" button in the plugin's Menu each time for each presets as VST3 would've force me(fabfilter's scenario) when i could've actually have them all in the right field next to the user presets once i would've pasted my presets (the plugin's own format presets) in its factory presets folder then voila, everything in my face with no "open/load" each time.
Also, on these Plugin Alliance plugins, as you can see in the VSM-3's GUI there's no "Open/Load" menu either so if i would've work in S1, i would've been bound to save the presets only in the DAW's format and unable to use the presets in other DAWs such as my partner's LPX for example. As far as i know, Ableton doesn't support VST3 either.

 

I may agree with you, a universal format for preset that works in every daw will be cool. I'm thinking about FXP and FXB wich are already supported by some daws (cubase,s1,FL...). I can send a preset to a friend of mine who uses FL and he is able to open it.

For the menu thing, i honestly think that Plugin Alliance should have a standard bar for their plugin preset like Waves. So vst2 or vst3 can have their preset scrolling.

 

Late reply since previous post...

Discovering this fact too, from Studio One 3 (v3.1.1, 64-bit), Z3TA+ 2 (both VST2/VST3 are installed) appears as VST3 only (VST2 is hidden from VST2 plugins list). All FabFilter (both FX and Twin 2 synth) appear both in VST2 and VST3 lists.

Maybe internal names/headers/UIDs (between VST2 and VST3 version, for same plugin) are identical for Z3TA+ 2 (SO3 give priority to VST3), and different for FabFilter plugins.

I don't worry about this, however. I've searched about an option I've seen in SO3, but I remeber couple of minutes later, in fact I've seen this option in... SONAR Platinum preferences (some confusions in my old brain).

Of course, by deleting - or by renaming the .vst3 (eg "Z3TA+ 2.vst3" to "Z3TA+ 2.vst3disabled") it appears as VST2 (and no more as VST3).

Probably an useful article here, but touching XML files is risky, IMO (backup is your friend, however).

I'm using mainly VST3 for FX plugins, and VST2 only for instruments supporting "Program Change" MIDI events (even Bank Select like DUNE 2, AAS synths...). Unfortunately, Program Change and Bank Select (MSB/LSB) are unsupported (removed/ignored/filtered?) since VST3 specification thx to Steinberg...

 

Last edited: Jan 25, 2016

Perhaps an another VST3 limitation? (like ignored "Program Change" and "Bank Select" MIDI messages, as I've indicated in previous post just above).

Sometimes VST3 appears like a regression, I can understand the reason why some serious editors (like Ableton or Native Instruments) avoid VST3 for their products.

 

Last edited: Jan 25, 2016