(for many years now).Ĭakewalk by Bandlab, by default, hides VST 2 plugins that have a VST 3 version, and things work quite well for me. Well, existing VST2 plugins will continue to work, for years, and while I am saddened by some 32-bit plugins I loved, mostly freeware, that just either do not run, or are unstable in 64-bit hosts (even with Bit-Bridge or J-Bridge), I am actually enjoying a very stable environment, with 64-bit VST 2 AND VST 3 running in Windows 10. I guess it will be the 2nd huge loss of plugin resources for us when VST2 is goes away, not all plugins will be updated to VST3 (especially the free ones and the ones of small manufacturer). Why do I speak of authorization? A week ago one of my systems failed and until today I am fighting with authorization and other recovery! Though it is a pity, because I like more and more the plugins that have a simple, straightforward authorization and most of them are old ones (but there are some exceptional developers also nowadays). Even me do not use them anymore to avoid the organisational trouble. In my first sentence I mentioned good plugins and I know a couple of extraordinary, exquisite 32-bit plugins (most free). I know, there are those ones that conjure not to use 32-bit anymore! But if you use additional hosts like SoundForge 11 or Audacity. Like that, for years many of us have to deal with 3 to 4 plugin versions at the same time (32-bit vst2/3, 64-bit vst2/3) caused by the Steinfrog's dictatorship. But I am sure that the advantages do not outweigh the disadvantages, especially for the users (audio engineers, musicians). I have a long list of disadvantages for VST3 compared to VST2, maybe there are a few technical advantages, too. IMHO it is a shame that so many really good plugins are more and more disused, because the fxxxing Steinbergs always change the concept.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |