Wondering how the Apple ARM transition is going to affect huge plug-in ecosystems, like DAWs and VSTs. This could go very poorly, with the effective loss of anything that isn't being actively developed and/or having to re-buy everything for ARM...
-
Show this thread
-
-
Replying to @ericmusicfan
I doubt Rosetta lets you mix native and emulated plug-ins in the same process. That is a generally unsolvable problem, especially if the ABIs aren't almost identical save for the instruction stream. And you wouldn't want to be using Rosetta on high performance DSP code anyway.
3 replies 0 retweets 12 likes -
This Tweet is unavailable.
-
Then I want to see their magic ABI adaptation framework, because I'm pretty sure that's an unsolvable problem generally. They might provide APIs to develop your own shim layers, but it's never going to just "magically work".
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
I just watched it and they don't say anything about that. In fact, they say the exact opposite. They say even Mac frameworks are running under Rosetta, which suggests they have no ABI shim layer *at all*, and instead adapt at the syscall layer. So it's even worse than I thought.
1 reply 0 retweets 0 likes
They talk about App Extensions, but those are out-of-process (e.g. AUv3). It's clear from that video that the Rosetta architecture boundary is the process boundary. VSTs are not out-of-process. There is nothing there at all about this being even possible to manually develop.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.