However its just as likely you’ll get a couple of the same responses because resources are limited. If there is enough response it might make sense for stienberg to do the work to move them forwards. Its not a bad idea to start a thread on porting old 32 bit VSTs to 64 with a short specific list. Maybe asking for very specific VST’s that you use a lot and making a short list may be doable, but to ask for all isn’t realistic. SOmetimes it makes better sense to rewrite code than try to update it from 32->64bit because then you also can take advantage of newer API’s, processor features, etc that the legacy code would require what amounts to a rewrite anyway. So I would NOT count on tons of old VSTs getting updated, especially if they have been replicated with new versions. running a VM also can have problems with hardware I/O, especially if your old interface is FW. Trying to run an old OS in a VM is possible, but only for the OS skilled. I know you don’t want to hear that but its the best bad solution right now. Freeze it in time, keep it off the internet so it can’t auto update and then you can continue to open and update old projects. The solution which you won’t like, but for now is the only practical one : keep an old machine running with old OS / apps / plugins. Many in the video community have run into this same problem of old projects not working on new OS / App / hardware.
thankfully not hostage to subcriptionware to authorize to a remote server that doesn’t exist or won’t authorize (adobe). What you have really hit is the digital abyss. you have to really go through all the code because some weird things can happen when variables get promoted from int to long, etc, and lets leave it at that. its not a wave a magic wand, recompile and done thing. Including the old 32 bit plugin effects as 64 bit equivalents in Cubase 12 would be a huge sweetener.Ĭonverting code from 32 to 64bit is a significant task. Steinberg are clearly trying to encourage users to get into Cubase 12 with their latest “free” offers. Surely it is not a mammoth task to update these old plugins to 64 bit equivalents that can be used with legacy projects as well as new ones? Over the years Steinberg have invested a lot in the old 32 bit plugins. I want to, and need to raise the projects to Cubase 11/12 but then the 32 bit plugins get messed up, and almost impossible to replicate with new 64 bit plugins. (Cubase 7 is already getting a bit unstable). With the switch to windows 11 and the Steinberg announcement that they cannot guarantee versions older than Cubase 11 will work with windows 11 I am faced with the possibility that I may no longer be able to access these old 32 bit projects in their native Cubase version. I have over 200 projects going back more than 15 years that use 32 bit plugins.