@dragsquares said:
It's my understanding that the reason VEPro works is low-level code, directly addressing hardware - which when it was originally written was Intel. Now that Apple Silicon is here, and it's a completely different hardware platform and architecture, it's got to be like writing the whole thing from zero. Maybe the M-series CPU's don't deal with these direct calls as well. That's all beyond me. But I think of this like a team of developers writing an entirely new app that has the goal of enterprise-level reliability and the greatest efficiency and speed possible. How long would one say that should take? Especially if they have other things that people are clamoring for.
Some folks are acting like the folks at Vienna don't care about users' feelings about this. Of course they do. But they can't do anything about those big feelings except put out the best product they can, and for our part we can maybe not act like our feelings trump reality.
The problem here is conjecture. You're just as guilty of it as anyone who thinks that VSL don't have good reasons to have put Apple Silicon first in terms of support. You do not know why and neither do we.
One thing, IMO it's a travesty and poor business move that they did not release Apple silicon native versions of the VST, MAS, and AU VEP plug in at the least. This wouldn't require low level code etc. and would make it possible for Cubase users to actually use their DAW along with an Intel PC or Mac server, or even VEP in Rosetta using the native VST in Cubase. I can't think of a rational excuse this didn't happen.
