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 -
Replying to @marcan42 @ericmusicfan
DAWs might provide compatibility shims, but that takes extra effort and I bet it'll be a niche filled by others, much like how I can run Windows VSTs on Linux with LinVST (but poorly), and there is a performance cost.
1 reply 0 retweets 4 likes -
Replying to @marcan42
LMMS does it with wine. Although it's bad enough Apple dropping 32bit support and Ubuntu THINKING about dropping 32bit.
1 reply 0 retweets 1 like -
Replying to @ericmusicfan @marcan42
In order to do something like this, though, you need a layer that is aware of the ABI itself; it can't be done *generally* because there's no clean, common abstraction layer between things. Microsoft (and many others too) tried that with COM and nobody liked it.
2 replies 0 retweets 3 likes -
Replying to @let_mut_john @ericmusicfan
You need code that is aware of the *specific* interface on both sides (i.e. VST) and can convert data structures. And it'll still break if you have vendor extensions. It's not going to be smooth.
2 replies 0 retweets 4 likes
And since you're almost certainly going to be introducing a process boundary, that also adds overhead with context switching, and complexity over shared memory mappings. Some things might be actually impossible to do.
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.