There are some synths only with VST2, no VST3 (Hybrid 3 was one I was think to get but it only is VST2). I know the VST3 is more new thing. I need to ask, is VST2 soon going to be same as 32bit and you can no use it anymore? VST2 same as 32bit and VST3 same as 64bit?
The price is not bad + it do sound very well. But I do not know if VST3 is very important thing?
https://www.thomann.de/gb/air_music_tec ... brid_3.htm
Problem if synth is only VST2?
-
- KVRAF
- 9546 posts since 6 Jan, 2017 from Outer Space
Not really a problem unless you have a host that does not support VST2...
Only programmers who create a new host and have not signed the license with Steinberg would do so (except for Avid, they are simply too ignorant to support any other format than their own...).
I guess it will need decades until that happens, and there are wrappers around already which would allow VST2 even in VST3 only hosts...
Only programmers who create a new host and have not signed the license with Steinberg would do so (except for Avid, they are simply too ignorant to support any other format than their own...).
I guess it will need decades until that happens, and there are wrappers around already which would allow VST2 even in VST3 only hosts...
-
- KVRist
- 297 posts since 3 Dec, 2009 from Cologne, Germany
VST3 and VST2 has nothing to do with wordlength of processing. Both can be for 32 or 64 bit hosts.
You should use VST2 with no problems on any host. VST3 only is the next level of VST implementation and supports more functionality.
I uses lot "VST2 only" instruments on Cubase 10.5 without issues - even Hybrid 3
You should use VST2 with no problems on any host. VST3 only is the next level of VST implementation and supports more functionality.
I uses lot "VST2 only" instruments on Cubase 10.5 without issues - even Hybrid 3
-
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
I don't think he/she was technically comparing or equating vst2/vst3 to 32/64 bits but rather that he/she is wondering if similar to how 32 bit plugins are becoming scarcer and also some hosts like Cubendo don't even work with 32 bit without some kind of bridge technology anymore, if he/she is to expect the same for vst2. Well that is how I interpret it anyway.
As you may know SB has discontinued vst2 completely and I don't believe any new developer can still legally create a vst2 plugin (since they won't legally have access to the sdk's required to make vst2 plugins).
I however think vst2 will still be around for awhile (my guess would be at least 3-5 years based on no inside information). I can't imagine any DAW host disallowing vst2 plugins before then.
My guess.
rsp
As you may know SB has discontinued vst2 completely and I don't believe any new developer can still legally create a vst2 plugin (since they won't legally have access to the sdk's required to make vst2 plugins).
I however think vst2 will still be around for awhile (my guess would be at least 3-5 years based on no inside information). I can't imagine any DAW host disallowing vst2 plugins before then.
My guess.
rsp
sound sculptist
-
- KVRian
- 629 posts since 15 Jun, 2017
Well....the way forward is VST3...introduced in 2008. Steinberg is very much pushing for that.....since 2013.
https://en.wikipedia.org/wiki/Virtual_Studio_Technology
https://www.steinberg.net/en/newsandeve ... -2504.html
For many reasons, many years later, VST2 is still very much alive. As is 32-bit. On the other hand, some developers are no longer (or no longer fully) supporting VST2. As some no longer support 32-bit. Especially for their new products.
As demand for VST3 will increase, as is the case for 64-bit, Developers will have to adapt or be left behind.
Anyway...
Should you still invest in VST2 plugins? VST3 does add functionality like flexible input/output (audio/MIDI) configuration. It depends on the specific plugin whether these new options are actually relevant/used. And legally...it is less complicated (free), which is good news to developers. Among them those who develop free and open source plugins. Generally, if you have a choice, go for VST3.
At Sweetwater they made this comprehensive PROS and CONS (and MYTHS) list
VST 2.4 vs. VST 3.0 – Who Cares? You Should.
https://www.sweetwater.com/insync/vst-2 ... es-you-do/
https://en.wikipedia.org/wiki/Virtual_Studio_Technology
https://www.steinberg.net/en/newsandeve ... -2504.html
For many reasons, many years later, VST2 is still very much alive. As is 32-bit. On the other hand, some developers are no longer (or no longer fully) supporting VST2. As some no longer support 32-bit. Especially for their new products.
As demand for VST3 will increase, as is the case for 64-bit, Developers will have to adapt or be left behind.
Anyway...
Should you still invest in VST2 plugins? VST3 does add functionality like flexible input/output (audio/MIDI) configuration. It depends on the specific plugin whether these new options are actually relevant/used. And legally...it is less complicated (free), which is good news to developers. Among them those who develop free and open source plugins. Generally, if you have a choice, go for VST3.
At Sweetwater they made this comprehensive PROS and CONS (and MYTHS) list
VST 2.4 vs. VST 3.0 – Who Cares? You Should.
https://www.sweetwater.com/insync/vst-2 ... es-you-do/
-
- Banned
- Topic Starter
- 26 posts since 5 May, 2020
This is what I did try to say, thank you. I think Hybrid 3 is older synth when it is only VST2 and it is cheaper price now then before.zvenx wrote: Fri May 15, 2020 1:17 pm I don't think he/she was technically comparing or equating vst2/vst3 to 32/64 bits but rather that he/she is wondering if similar to how 32 bit plugins are becoming scarcer and also some hosts like Cubendo don't even work with 32 bit without some kind of bridge technology anymore, if he/she is to expect the same for vst2. Well that is how I interpret it anyway.
As you may know SB has discontinued vst2 completely and I don't believe any new developer can still legally create a vst2 plugin (since they won't legally have access to the sdk's required to make vst2 plugins).
I however think vst2 will still be around for awhile (my guess would be at least 3-5 years based on no inside information). I can't imagine any DAW host disallowing vst2 plugins before then.
My guess.
rsp
-
- KVRAF
- 7660 posts since 2 Sep, 2019
It's not a problem yet but you just don't know what the future holds. (Well, actually, you do, and it includes MIDI 2.0...what it doesn't include is VST2.)
For me, it's really all about future-proofing, and the developer's commitment to their products and remaining relevant factors heavily into that. There are a lot of zombie plugins out there, and no VST3 support is a good way to spot them early.
There are some really good features that VST3 introduces, like window resizing, process suspension when there is no audio, dynamic management of I/Os and busses.
But some developers complain because VST3 removed MIDI CC handling from plugins (because that is something that should be handled by the host only, not the individual plugins, and VST3's MIDI implementation changes means that VST3 plugins will automatically work with high resolution MIDI 2.0.) But some developers are using this as an excuse to whine and not develop VST3 plugins. There were also some developers who said that DirectX was all you need and refused to support VST when it came out. Those developers and their plugins are extinct now.
VST2, just like DirectX, is obsolete and never coming back. A developer who hasn't started supporting VST3 —12 years after its introduction, 7 years after VST2 development and support ended, and 2 years after VST2 was removed from the VST SDK completely— is a developer who just isn't committed to, well... developing. Not a vote of confidence for their future viability at this point.
For me, it's really all about future-proofing, and the developer's commitment to their products and remaining relevant factors heavily into that. There are a lot of zombie plugins out there, and no VST3 support is a good way to spot them early.
There are some really good features that VST3 introduces, like window resizing, process suspension when there is no audio, dynamic management of I/Os and busses.
But some developers complain because VST3 removed MIDI CC handling from plugins (because that is something that should be handled by the host only, not the individual plugins, and VST3's MIDI implementation changes means that VST3 plugins will automatically work with high resolution MIDI 2.0.) But some developers are using this as an excuse to whine and not develop VST3 plugins. There were also some developers who said that DirectX was all you need and refused to support VST when it came out. Those developers and their plugins are extinct now.
VST2, just like DirectX, is obsolete and never coming back. A developer who hasn't started supporting VST3 —12 years after its introduction, 7 years after VST2 development and support ended, and 2 years after VST2 was removed from the VST SDK completely— is a developer who just isn't committed to, well... developing. Not a vote of confidence for their future viability at this point.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
-
- Banned
- 7624 posts since 13 Nov, 2015 from Norway
I never use vst3 anyway
EnergyXT3 - LMMS - FL Studio | Roland SH201 - Waldorf Rocket | SoundCloud - Bandcamp
-
- Banned
- 97 posts since 15 May, 2020
I only use VST3.
When people move the goal posts to make a point, there is no longer an original point to be made.
-
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
You said my thoughts but way more veraciously/vehemently than I ever wouldjamcat wrote: Fri May 15, 2020 3:21 pm It's not a problem yet but you just don't know what the future holds. (Well, actually, you do, and it includes MIDI 2.0...what it doesn't include is VST2.)
For me, it's really all about future-proofing, and the developer's commitment to their products and remaining relevant factors heavily into that. There are a lot of zombie plugins out there, and no VST3 support is a good way to spot them early.
There are some really good features that VST3 introduces, like window resizing, process suspension when there is no audio, dynamic management of I/Os and busses.
But some developers complain because VST3 removed MIDI CC handling from plugins (because that is something that should be handled by the host only, not the individual plugins, and VST3's MIDI implementation changes means that VST3 plugins will automatically work with high resolution MIDI 2.0.) But some developers are using this as an excuse to whine and not develop VST3 plugins. There were also some developers who said that DirectX was all you need and refused to support VST when it came out. Those developers and their plugins are extinct now.
VST2, just like DirectX, is obsolete and never coming back. A developer who hasn't started supporting VST3 —12 years after its introduction, 7 years after VST2 development and support ended, and 2 years after VST2 was removed from the VST SDK completely— is a developer who just isn't committed to, well... developing. Not a vote of confidence for their future viability at this point.
I believe they added midi cc back though cause a lot of people were complaining about it. (seems like you said, vst 2 was not suppose to have midi cc either but developers found work arounds that the consumer got accustomed to)
rsp
sound sculptist
-
- KVRAF
- 3506 posts since 12 May, 2011
I'm holding out for vst4.
And 256bit.
And 256bit.
-
- Banned
- 1792 posts since 8 Sep, 2019 from Calenberg
Yes, because I ONLY use AU plugins.
-
- KVRist
- 188 posts since 7 Dec, 2004
Hybrid 3 is a great synth, but as far as updates go... well... AIR has been promising updates to their entire line for at least 3 years now.JollyBoih wrote: Fri May 15, 2020 6:22 pm Any body knows Hybrid 3? You think this will get update + VST3 some day? It is from Air music if that is good and if they usually update they's synths?
The current VST2 version works fine for me, but I wouldn't hold my breath waiting for updates.
- Jay