INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 INSTALL
INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 SOFTWARE
INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 CODE
INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 PLUS

INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 PLUS

This is why we had Kontakt, MAssive X, all of the Arturia FX plus ins and Spark, updated to run in Rosetta.

INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 CODE

Mostly, developers need the AU code to be ready for Big Sur and Catalina before it for their AU's to work in Rosetta, if they don't they do not work in Rosetta. The Sound Toys issue according to them is a PACE iLok issue, so somehow running DP in Rosetta to validate the plug ins is making them work when you switch to native DP11 again, and it does seem to me tied to that same issue. My iOS AUv3 copy of Moog Model 15 loads into native DP11just fine. AU really only got a naming convention you can see with AU3, which is capable of running iOS plug ins on M1. As an end user there's not really any way to know what is AU1 or 2. So you're essentially correct, old AU's do not work in Rosetta, AU's coded with the latest v2 spec do. (also v2 is subsection of the v3 spec, so its not like starting over, maybe?) Some devs like Valhalla/Fuse Audio/Waves (yeah I know Waves!) got to it right quick and their whole lines are already M1 Native. The Au v3 spec is 5 years old, but I'd guess its a combination of compliers and old/new source. Also works on iOS (which is one of the reasons for AU v3)Įvery single problem plugin I've had on my M1 Max is a AU v2 compiled plugin. Awesome!ĪU v3 compelled as a Universal Binary - works on OS 12, Apple Silicon, no translation, Intel OS 12 only ( never checked a UB in OS 11, they may work, I dont know if the UB format is OS 12 only). (Ala Soundtoys plugins for me-yay!)Īu v3 compelled for Intel works on OS 10.12-x, OS 11, OS 12, Intel and Apple Silicon, with the Intel versions translated with Rosetta for AS Native apps like DP, Logic. The work around for some of these are (and not all and I don't know why) to open the Native app like DP in Rosetta (Get Info checkbox) rescan the plugins and once they validate, switch the app back to native. AU = Audio UnitsĪU v1 compiled for Intel - Works on OS 10, not on OS 11 or OS 12 in IntelĪU v2 compiled for Intel-works on OS 10.x -OS 11 Intel, also works in OS 12, translated by Rosetta, if the app hosting them is also translated by Rosetta -otherwise they fail validation. I don't know this to be 100% true, YMMV, a lot, but this is how it seems to span out for me with 300+ plugins. I would bet that Mainstage intentionally is prevented from using Rosetta for most things, because it's a live performance app, and Apple don't want the tech support calls. Some developers have not gotten that far along. Notice the part, 'updated to the latest AU spec', not all AU's are working in Rosetta, the reason that Kontakt can is because NI updated it specifically to be able to run in Rosetta. because it's not running natively.Īudio Units if they are updated to the latest AU spec can run in Rosetta in a native DAW like DP11, because Apple built in that ability. It has nothing to do with the VST to MAS plug in, it's very obviously native.ĭP running in Rosetta can run non native VSTs etc. I run plenty of native VSTs in native DP11. In order to use VST2 plugins you need the wrapper and in order to use the wrapper DP must itself be running in Rosetta. I believe the issue is that DP’s “VST2 to MAS Wrapper” is not AS native (and maybe can’t be). If a non AS native plug-in is AU format it will use Rosetta as needed without DP itself running under Rosetta. I believe it only applies to VST2 plugins. But, this doesn’t apply to all non AS native plugins. Not all that excited about going the VEP route, but it is a fallback position that is good to know can work.įirstly, to answer your question, DP must be in Rosetta to both scan and use the plugins in question. I'll spend the required time when Apple Silicon makes its entrance at Rancho Bohemia.īut I'll be keeping my 5,1 around for sure.

INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 INSTALL

DP11 on a fresh install of Mojave didn't make the machine happy either, so I abandoned that effort for now. GUI slowdowns annoy, even running DP10.13, and I find myself pushing the 12 core to its limits pretty regularly.

I get plenty of work done on my 5,1, but run up against its limitations quite often.

INSTAL THE LAST VERSION FOR WINDOWS MAINSTAGE 3 SOFTWARE

When we get a desktop M1 Pro/Max, as I anticipate will take place within the next few months, I will be looking at the software side of the equation very carefully and seriously considering taking the leap of faith the move to a completely new CPU/GPU architecture entails. That said, I'm excited to move into a new realm of performance. As the M1 reportedly just matches my 12 core 5,1 in terms of overall horsepower, I'm holding off on a move to Apple Silicon, especially given the software considerations Michael and others have noted.

Instal the last version for windows MainStage 3