#Cubase for macs code

As to why so many people have been slow to move on to VST3, the answer is simple and obvious.VST3 was not an improvement for most people. That is simply an abitrary decision being made by Steinberg to force people to move completely to VST3. There is no technical reason whatsoever why M1 Macs couldn't run VST2 plugins. Simple truth is that MANY people still rely and depend on VST2 plugins. This will be a factor for many people it sounds like, on the Mac ARM platform in a couple years from now. Yea this post belongs on that other thread for the people that chose or are choosing to leave Cubase. I’m not holding my breath, but it would still be disappointing to just get a new licensing system and more plugins in 2022.

#Cubase for macs code

They need to acknowledge the 500lb gorilla in the room: the legacy code base, and doing so may require forgoing backwards compatibility. They are in a position to leap ahead, but it will require more fortitude than they have demonstrated in quite a while.

Steinberg has been conservative in their updates for many years now. Now that DP has articulation maps (with delay compensation per articulation), I certainly hope expression maps get an update. Perhaps they will move toward a design language along these lines. I love the Dorico and Cubasis interfaces. I also think if Steinberg addresses the UI and incorporates Dorico in a substantive way, that will really push things forward.

With native Apple Silicon support, it could be a great workflow for more users. work far better with local instrument tracks (as opposed to VEP). Cubase seems to be steering users to host instruments internally.