I'm pretty sure that there was a lot of noise when DAWs were removing DX support (I didn't bother about forums at that time to remember). Predictions that DAWs will collapse, Nosferatu will wake up etcc_voltage wrote: Wed Jan 19, 2022 8:42 pm Still prefer vst2 where it possible, by various reasons. The only exclusion, Waves perhaps.
The news that the DAWs will force (?) to abandon (remove) the support of the VST2, it seems to me some kind of abnormality. In the near future, of course, I mean. Need check Steinberg forums what peoples say![]()
Cubase - Vst 2 vs 3
-
- KVRAF
- 1863 posts since 11 Apr, 2008
-
AdvancedFollower AdvancedFollower https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418780
- KVRian
- 1342 posts since 8 May, 2018 from Sweden
Most of those are still under active development, and will almost certainly have VST3 versions before 2024, with all issues ironed out. VST3 support isn't dropped from today, it's in 24 months. The good thing about a firm deadline is that some developers who have been putting it off for a long time might finally get around to it. Lennard for example has promised a VST3 version of Sylenth1 but never given a release date. Having worked in IT for 10+ years, I know one of the most effective ways to get developers to migrate to new frameworks etc. is to simply announce a date for when the old framework will be uninstalled from the production servers
Of course there are some concerning things on that list. It's doubtful NI will update older but still popular plugins like Massive (considering Massive X is the New Shiny), and the Lexicon stuff seems to be abandonware ever since Michael Carnes left the company years ago. GForce only focus on Mac these days so they probably won't spend any more time and money on Windows users. For smaller developers, it might also be a struggle, but then again, they have 24 months. There's always VST3 wrappers if you absolutely cannot live without one of those plugins.
Take a single oscillator, producing a drone. Send it to the wave shaper, altering the tone.
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care
- KVRAF
- 2473 posts since 25 Sep, 2014 from Specific Northwest
The big question is will Absynth finally see some NI love or is this the final nail in its coffin? It would be a pity to see it go as I always considered it the jewel in their crown.EvilDragon wrote: Wed Jan 19, 2022 7:38 pm NI is def coming out with VST3 of all their current portfolio.
I started on Logic 5 with a PowerBook G4 550Mhz. I now have a MacBook Air M1 and it's ~165x faster! So, why is my music not proportionally better? 
- KVRAF
- 24434 posts since 7 Jan, 2009 from Croatia
I don't know for sure, but without Brian around, it's probably safe to assume it's in life support mode.
- KVRAF
- 2629 posts since 16 May, 2004 from Soviet Union
This is definitely not the same (as well as plugin market at that time in general).pixel85 wrote: Wed Jan 19, 2022 10:05 pm I'm pretty sure that there was a lot of noise when DAWs were removing DX support (I didn't bother about forums at that time to remember).
And i think more or less major DX plugs they already had vst as well, ie deal not only in format removing (and project compatibility), but ability of run plugin too. While those plugs that were only in DX, I think they were in such a minority that it really didn’t bother anyone.
While there is so much of vst2 (incl bridged x32 things) wonderful stuff which i'm sure i'm will not want to lost ability to use in near future, nor in my lifecycle at all.
-
- KVRian
- 614 posts since 26 Jun, 2016
so.... until then for the plugins that do not have a vst3 version yet.
Metaplugin or Patchwork?
Is it possible for patchwork to load jbridged plugins?
Metaplugin or Patchwork?
Is it possible for patchwork to load jbridged plugins?