Helpful ReplyVST vs. VST3 Plug-ins

Page: 12 > Showing page 1 of 2
Author
BbAltered
Max Output Level: -88 dBFS
  • Total Posts : 137
  • Joined: 2014/10/11 11:03:47
  • Status: offline
2016/02/02 17:33:23 (permalink)

VST vs. VST3 Plug-ins

Hello.  What is the difference between VST and VST3? 
 
Some of my plug-ins (Z3TA+ and Rapture Sessions) appear in my Plugin Manager in both VST and VST3 versions.  Which version should I use?  Is there an advantage to using the VST3 version over the VST version?  (I am thinking that once I figure out which version I will use, I will hide the other version.)   
 
Thanks.
#1
Zargg
Max Output Level: 0 dBFS
  • Total Posts : 10666
  • Joined: 2014/09/28 04:20:14
  • Location: Norway
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/02 18:36:04 (permalink)
Hi. I seem to remember reading that VST3 is less resource hungry. And has better coding, if I understand correctly. But that is where my (lack of) knowledge ends. Other will know better.
All the best.

Ken Nilsen
Zargg
BBZ
Win 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII
Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
 
#2
Zargg
Max Output Level: 0 dBFS
  • Total Posts : 10666
  • Joined: 2014/09/28 04:20:14
  • Location: Norway
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/02 18:38:41 (permalink)
Ps. I use VST3 exclusively instead of the VST2 version. You can tell SONAR to exchange VST2 for VST3 if available under Preferences (P), Vst Settings. 
 

Ken Nilsen
Zargg
BBZ
Win 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII
Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
 
#3
davec69
Max Output Level: -87 dBFS
  • Total Posts : 178
  • Joined: 2014/11/15 03:43:21
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/02 20:52:41 (permalink)
You can find information on VST3 here:
 
http://www.steinberg.net/en/company/technologies/vst3.html
 
For me, the main 2 points are improved performance, and dynamic allocation of inputs.  No more mono and stereo plugins to mix up.  VST3 determines whether the source is mono or stereo.

Toshiba P75-A7200 Laptop
Intel i7-4700MQ
16GB RAM
2 x 1TB Hybrid Drives
Windows 10
Sonar Platinum (Last Update)
Cakewalk Bandlab (Latest Update)
Roland Quad Capture (Bios 1.04 / 1.52 drivers)

#4
BbAltered
Max Output Level: -88 dBFS
  • Total Posts : 137
  • Joined: 2014/10/11 11:03:47
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/02 23:03:16 (permalink)
Hello.  Thanks Dave and Zargg for your helpful replies.  So I will do a little reading on VST3.
#5
dcumpian
Max Output Level: -34 dBFS
  • Total Posts : 4124
  • Joined: 2005/11/03 15:50:51
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 08:17:55 (permalink)
The other difference is that VST3 will eventually replace VST2, so that's where you're going to want to invest. VST2 is on its way out. However, at this somewhat early stage, not every DAW is VST3-ready, and some that are still run into issues with VST3 plugins because the plugin developers are still learning. It is good to have both, for now, so if the VST3 doesn't work correctly, the VST2 may.
 
Regards,
Dan

Mixing is all about control.
 
My music:
http://dancumpian.bandcamp.com/ or https://soundcloud.com/dcumpian Studiocat Advanced Studio DAW (Intel i5 3550 @ 3.7GHz, Z77 motherboard, 16GB Ram, lots of HDDs), Sonar Plat, Mackie 1604, PreSonus Audiobox 44VSL, ESI 4x4 Midi Interface, Ibanez Bass, Custom Fender Mexi-Strat, NI S88, Roland JV-2080 & MDB-1, Komplete, Omnisphere, Lots o' plugins.    
#6
Sidroe
Max Output Level: -55.5 dBFS
  • Total Posts : 1954
  • Joined: 2010/11/10 18:59:43
  • Location: Macon,Georgia
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 08:30:12 (permalink) ☄ Helpfulby joden 2016/02/03 11:02:10
Some people have already started having problems with the Sampletank 3 VST 3 plug, or so I have heard. I know mine was kind of buggy so I switched over to the vst 2 version and never had a problem.

Sonar Platinum, Sonar X3e, Sonar X2a , Sonar X1 Expanded and 8.5.3 (32 and 64 bit), Windows 10 on a Toshiba P75-A7200 Laptop with i7 @ 2.4 quad and 8 gigs of RAM and secondary WD 1 Tb drive, Windows 10 desktop, Asus i5 @ 3.2 quad, 12 gigs RAM, 1 Tb drive, 1 500 gig drive, MOTU 24io, 2 Roland Studio Captures, Saffire 6 USB for laptop, Soundtracs Topaz Project 8 mixer, Alesis Monitor 2s, Event BAS 20/20s, Roland Micro-Monitor BA-8s, and 45 years worth of collecting FX, Mics, Amps, Guitars, and Keyboards!
#7
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
  • Total Posts : 26036
  • Joined: 2006/09/17 11:23:23
  • Location: Everett, WA USA
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 09:01:35 (permalink) ☄ Helpfulby Mesh 2016/02/03 09:17:04
VST3 plugins are not more efficient. In all likelihood you will experience exactly the same performance with either VST2 or VST3. Developers maintain a common code base for both, with 99.9% of the internal code being identical. The idea that VST3 is more efficient stems from its feature for shutting off a plugin when there is no data coming in. However, plugins have always had that ability if the developer chose to implement it. 
 
VST2 is not going to stop working due to obsolescence. Some new products, in particular those from Steinberg/Yamaha, will only be available as VST3. But as long as the host supports the VST2 standard, your VST2 plugins will continue to work. Eventually, vendors may decide to stop developing new VST2 plugins just to simplify things for themselves. Eventually, VST3 may be the only choice for new products. But even then, your existing VST2 plugins will still work.
 
To answer the original question (what is the difference between VST and VST3?), they are two versions of a written specification describing how hosts (DAWs) and plugins (VSTs) communicate with one another. That's it. It does not dictate how plugins work internally.
 
VST3 does add some new capabilities, mostly relevant to soft synths, such as support for multiple MIDI ports that can be switched on the fly. There is a myth that only VST3 plugins can use external sidechains, but that only applies to Cubase users. We've been doing it in SONAR for more than a decade, long before the advent of VST3.
 
Being a new standard, many developers have hit snags while adapting to it. Consequently, many newly-reported bugs turn out to apply only to the VST3 version of a plugin. When that happens, you can simply revert to the VST2 version and carry on.


All else is in doubt, so this is the truth I cling to. 

My Stuff
#8
Sanderxpander
Max Output Level: -36.5 dBFS
  • Total Posts : 3873
  • Joined: 2013/09/30 10:08:24
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 09:17:44 (permalink)
Importantly, the automation menu in Sonar is much better organized for VST3s. You can find each parameter by category instead of long random lists of 128 parameters. That is, if the synth manufacturer took advantage of the categorization options.
post edited by Sanderxpander - 2016/02/03 09:31:16
#9
BbAltered
Max Output Level: -88 dBFS
  • Total Posts : 137
  • Joined: 2014/10/11 11:03:47
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 09:30:41 (permalink)
Hello.  Thanks guys, for the interesting and enlightening discussion. 
#10
joden
Max Output Level: -65 dBFS
  • Total Posts : 1263
  • Joined: 2007/09/22 17:03:46
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 10:49:25 (permalink)
Sidroe
Some people have already started having problems with the Sampletank 3 VST 3 plug, or so I have heard. I know mine was kind of buggy so I switched over to the vst 2 version and never had a problem.


 Agree totally !
#11
Shambler
Max Output Level: -75 dBFS
  • Total Posts : 783
  • Joined: 2010/07/06 05:20:19
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 11:06:54 (permalink)
U-He recommended not using VST3 version of their synths, issues with forgetting which sounds were selected when reloading and a few others...still not sure if this has been addressed.
 
http://www.kvraudio.com/forum/viewtopic.php?f=31&t=398532&sid=c0341ebcdb87929d4001b78a9d0ac408

SONAR Platypus on Win10 64bit.
Studio One Pro / Cubase Pro 9.5...just in case.
8GB i7-2600 3.4GHz Gigabyte  Z68XP-UD3P
Geforce GTX970
Focusrite Scarlett 18i20 2nd Gen
Prophet 12/Rev 2/Virus Snow
Zebra2/DIVA/NI Komplete 10
#12
Bristol_Jonesey
Max Output Level: 0 dBFS
  • Total Posts : 16775
  • Joined: 2007/10/08 15:41:17
  • Location: Bristol, UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 11:11:12 (permalink)
Shambler
U-He recommended not using VST3 version of their synths, issues with forgetting which sounds were selected when reloading and a few others...still not sure if this has been addressed.
 
http://www.kvraudio.com/forum/viewtopic.php?f=31&t=398532&sid=c0341ebcdb87929d4001b78a9d0ac408


Sounds like Rapture Pro!

CbB, Platinum, 64 bit throughout
Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
#13
ston
Max Output Level: -71 dBFS
  • Total Posts : 965
  • Joined: 2008/03/04 12:28:40
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 11:29:25 (permalink)
Steinbork shot the pooch, the fox, kicked them both into a tri-cornered cocked hat and then ended with a flourish of ballsing it right up when they came up with VST3.  A nightmare for developers; badly designed, poorly architectured, and more prone to issues (i.e. than 2.4) due to this overly complex nature (both for host and plugin authors).  You do get some fancy new bells and whistles, but really not much more than you can do with VST 2.4 already.  For example, in 2.4 you might have dedicated mono- and stereo- plugins, but in 3, a single plugin can automagically configure itself depending on the nature of the channel it's dropped into.  Not that much of a big deal and certainly not worth the considerable extra development overhead.
 
My VST3 folder is empty.
#14
Paul P
Max Output Level: -48.5 dBFS
  • Total Posts : 2685
  • Joined: 2012/12/08 17:15:47
  • Location: Montreal
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 11:42:35 (permalink)
 
And vst3's have to go to the C drive.  What kind of an improvement was that.
 
 

Sonar Platinum [2017.10], Win7U x64 sp1, Xeon E5-1620 3.6 GHz, Asus P9X79WS, 16 GB ECC, 128gb SSD, HD7950, Mackie Blackjack
#15
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 11:57:29 (permalink) ☄ Helpfulby stickman393 2018/04/19 03:37:43
It solves the "where is my dll" problem. A frequent subject posted here. Of course, the spec is just a recommendation about the location of the plug-ins. All Cakewalk DAWs which host VST3 will load them from anywhere and for those strictly interpreting the spec, there are directory junctions.
#16
ChristopherM
Max Output Level: -56 dBFS
  • Total Posts : 1921
  • Joined: 2006/08/18 14:31:42
  • Location: UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 12:54:46 (permalink)
Apart from the U-He health warning, the biggest practical issue that I have come across is that by default, preset formats are different between VST2 and VST3. So if you cut across to the VST3 version, because it's all shiny and new, you suddenly find that your extensive library of presets is junk. This seems to be the case with Voxengo, for instance. Where the vendor uses a proprietary format, they apparently can sidestep the problem: FabFilter for instance seems to use the same format of preset.
 
BTW, I was a little surprised to find that Rapture Pro has no VST2 and comes as VST3 only.
#17
Sanderxpander
Max Output Level: -36.5 dBFS
  • Total Posts : 3873
  • Joined: 2013/09/30 10:08:24
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 12:57:36 (permalink)
FabFilter and Waves VST3s are great, I use them all the time.
#18
pwalpwal
Max Output Level: -43 dBFS
  • Total Posts : 3249
  • Joined: 2015/01/17 03:52:50
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 13:04:43 (permalink)
U-He health warning was from 2013 ;-)

just a sec

#19
ChristopherM
Max Output Level: -56 dBFS
  • Total Posts : 1921
  • Joined: 2006/08/18 14:31:42
  • Location: UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 13:17:34 (permalink)
... but as late as September 2015 the very same thread in which Urs 'fessed up his concerns was still active on U-He's own forum. As far as I know, Urs has still not given his VST3s a proper endorsement. I may be wrong about that. of course, because I don't slavishly follow the pronouncements of developers.
#20
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 13:26:05 (permalink)
ChristopherM
BTW, I was a little surprised to find that Rapture Pro has no VST2 and comes as VST3 only.

RPro includes both VST2 and VST3 formats
#21
ChristopherM
Max Output Level: -56 dBFS
  • Total Posts : 1921
  • Joined: 2006/08/18 14:31:42
  • Location: UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 14:55:52 (permalink)
scook
 
RPro includes both VST2 and VST3 formats

... and I'm surprised to hear that, because I came to my conclusion when I realised that I couldn't find a VST2 version of it, and so I took a look at Cake's own Product page about it and saw there that it says "NOW AVAILABLE IN VST3 | AU | AAX" and nowhere on the site does it seem to mention any other flavour of VST. So I gave up looking for it. Although I am not doubting what you say, Steve.
post edited by ChristopherM - 2016/02/03 15:09:31
#22
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 15:08:44 (permalink)
I believe you may be looking at the Mac info, for details see http://www.cakewalk.com/P...re/System-Requirements
The VST2 version is used by the stand alone minihost. The default path to both the dll and minihost is "C:\Program Files\Cakewalk\Vstplugins\Rapture Pro"
 
edit: fixed link
post edited by scook - 2016/02/04 04:19:22
#23
Bristol_Jonesey
Max Output Level: 0 dBFS
  • Total Posts : 16775
  • Joined: 2007/10/08 15:41:17
  • Location: Bristol, UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/03 16:52:49 (permalink) ☄ Helpfulby pentimentosound 2016/02/05 08:47:45
Christopher, where are you looking for the VST2 version?
 
If you're only looking in Sonar's media browser it might not be visible, depending on what you've got set here:
 


CbB, Platinum, 64 bit throughout
Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
#24
ChristopherM
Max Output Level: -56 dBFS
  • Total Posts : 1921
  • Joined: 2006/08/18 14:31:42
  • Location: UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/04 03:52:41 (permalink)
Steve: your link returns a colourful Page Not Found, but I had found the reference exclusively to VST3 simply by using the Products pull-down at the top of Cake's home page. I confess I didn't spend too much time researching it but just put 2 and 2 together and made 4 (or rather I couldn't see 2 at all but could see 3). I can see the dll lurking next to the mini-host now, but I am not seeing it in Plugin Manager, although it lies in one of my scan paths (along with umpteen other CW VST2s that are available). I don't have the time to delve deeper into this mystery today, regrettably.
 
Jonesy: I have left both of those boxes unchecked, because experience tells that typically any such glib automation methods often work fine most of the time, but when they occasionally get it wrong, the mess outweighs any advantage. Hmm ... sorry ... I must be in an atypically cynical frame of mind today: I'll be better after breakfast, I promise.
 
#25
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/04 04:15:13 (permalink)
the link above is fixed
#26
Bristol_Jonesey
Max Output Level: 0 dBFS
  • Total Posts : 16775
  • Joined: 2007/10/08 15:41:17
  • Location: Bristol, UK
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/04 04:22:24 (permalink)
ChristopherM
Jonesy: I have left both of those boxes unchecked, because experience tells that typically any such glib automation methods often work fine most of the time, but when they occasionally get it wrong, the mess outweighs any advantage. Hmm ... sorry ... I must be in an atypically cynical frame of mind today: I'll be better after breakfast, I promise. 



 
No need for apologies, but it does explain why you are seeing both the VST2 & VST3 versions

CbB, Platinum, 64 bit throughout
Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
#27
benjaminfrog
Max Output Level: -81 dBFS
  • Total Posts : 477
  • Joined: 2006/11/05 12:26:57
  • Location: Minneapolis
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/04 07:54:13 (permalink)
It may also be worth noting that, unless a fix has gone in since the last time I checked, FX Chains do not play well with VST3 plugins.

SONAR Platinum
Windows 10 Pro x64
ASRock Z97 Pro4
i7-4790K 4.0GHz
32GB RAM
Intel® HD Graphics 4600
RME Fireface UFX
http://www.sewardsound.com/
#28
Noel Borthwick [Cakewalk]
Cakewalk Staff
  • Total Posts : 6475
  • Joined: 2003/11/03 17:22:50
  • Location: Boston, MA, USA
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/04 20:58:14 (permalink)
VST3 and VST2 are different plugin authoring standards. Its really a misnomer that its called VST3 since its not even close to being the same thing as VST2.
VST3 has a more modern design for software development but it abandoned a few more traditional mechanisms for MIDI data. There is no notion of MIDI SYSEX or controller events in VST3 for example. Its replaced by generic parameters. There are a few new extensions in VST3 such as built in mechanism for having client server based plugins, and for multiple MIDI output ports.
For most practical purposes VST2 and VST3 plugins work and sound the same and almost all vendors have a lowest common denominator implementation of VST3. IOW only VST2 compatible capabilities are available for the vast majority of VST3 plugins.

Noel Borthwick
Senior Manager Audio Core, BandLab
My Blog, Twitter, BandLab Profile
#29
Paul P
Max Output Level: -48.5 dBFS
  • Total Posts : 2685
  • Joined: 2012/12/08 17:15:47
  • Location: Montreal
  • Status: offline
Re: VST vs. VST3 Plug-ins 2016/02/04 21:44:06 (permalink)
Noel Borthwick [Cakewalk]
There are a few new extensions in VST3 such as built in mechanism for having client server based plugins, ...

 
That'll take us to a whole new level of having to be online and logged in.
 
 

Sonar Platinum [2017.10], Win7U x64 sp1, Xeon E5-1620 3.6 GHz, Asus P9X79WS, 16 GB ECC, 128gb SSD, HD7950, Mackie Blackjack
#30
Page: 12 > Showing page 1 of 2
Jump to:
© 2024 APG vNext Commercial Version 5.1