East West has finally released an M1-compatible version of their plugin “EW Spaces”
Also Kilohearts has recently updated their software and it works really well now with Cubase.
Time to switch over to M1 Native Mode after a year of waiting…or so I thought.
When I try loading older (Rosetta Mode) projects that use the Kilohearts snapin plugins, it gives me an error message, that the plugin was not found. Instead, I have to empty the insert slot and load the plugin once again - the M1 version of it seems to have a different namespace.
The same thing happens with the EW Spaces plugin, unfortunately.
Upon asking East West about the problem, I received the following response:
Update for Case 149277 - “EW Spaces II VST Namespace”
The issue with this is that they are two entirely different plugin files.
The Rosetta version of Spaces II that was loading up in Cubase would have been the regular VST, but the M1 native version that loads up in Cubase is the VST3
Unfortunately, this is Cubase’s decision not to allow regular VST plugins to show up in the M1 native functioning Cubase 12, so to load any old projects you would have to run it in rosetta, then new projects going forward could be M1 native (that or entirely re-instantiate and load up spaces plugins in each that are the VST3 version).
Can anyone at Steinberg elaborate why this is such a problem and why can’t we just load up our old projects without issues? Other plugins work fine, including “Phaseplant Synth” and OPUS - by the same software vendors who had to create two different VST files for the M1 compatibility to work properly.
Sounds to me both parties are kinda stuffing this onto each others plates here - is it possible to work together and fix this?
Thanks so much!