![]() 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.
0 Comments
Leave a Reply. |