Bitwig M1 native can read both arm and rosetta plugins side by side. Convenient. 
4 Likes
Thanks! After looking at that I stumbled across SIMDe, and with that repo I can just include their header files instead of the x86 ones and with some minor changes can compile and run rack natively on M1.
The other issue I ran into was Rack having special linker commands for modules that execute Lua… I just deleted them and linked normally.
I loaded the default Rack2 template at 768khz single threaded and the native build had a 28% decrease in CPU utilisation compared to Rosetta 2.
6 Likes
Interesting!
Maybe you could compare your findings with the try out that Patrick @heapdump did a while ago or V1.x?
And compare, if not merge the 2 efforts together?
I think he ran into some issues at that time that might be relevant for you.
1 Like
molto bene ! I’m starting to investigate on how to do FAT binary (both arch) plugin
1 Like
Upgraded now to 4.x,
that runs a lot smoother on M1 
1 Like
Yes haha, that was definitely an upgrade worthy!
in answer to my historic self , now that I have M1 Pro I mean. Rack 2 is running just fine inside Ableton as a VST. So chill out son.
1 Like
VCV Rack 2 runs actually much better on an M1-Mac than on a Mac with Intel-Iris-Graphics. Rosetta does a great job and I wouldnt expect large performance-Improvements on a native M1-version as there arent significant Improvements on the native Versions of Ableton 11 and Bitwig either.
1 Like
Just asking, is your M1 on Bigsur, or on Monterey?
Cause it is functioning properly here on Mac mini M1 Bigsur.
And for several other forum members too, with the same configuration.
The native Reaper version is quite a bit snappier and leaner on the M1 as is the Opera Browser, over the non-native variants. So there are gains to be had, though definitely not in all apps. No crashes worth worrying about here, stable and fast things are in general. Big Sur here though, I wait on Monterey until that shakes out the major niggles, and nothing there listed under the trumped improvements interests me at all, Only a faster OS 
I’m using Abelton via Rosetta no specific configuration or set up employed from me and various buffer sizes without issue. I have the M1 Pro 32gb Ram running Monterey.
The just chill comment was in jest to myself.
Could be a Monterey issue?
Well, I’m not having issues on Monterey
I’m thinking about an M1 mini, and use ableton. All the above makes it seem quite temperamental in Rosetta for a few users. AU is on the roadmap for vcv isn’t it? So i guess that will solve any issues as we’ll be able to run the M1 native ableton?
Also has Andrew said that M1 native vcv rack pro isn’t going to happen in v2.x?
Ok if you are using VCV Rack on Monterey successfully, then we can rule that out 
If it’s crashing every time you use it, which isn’t the case here on Monterey on a 2021 MBP, try uninstalling Rack, all plugins, then reinstalling. Any difference?
I’m since finding that while VCV plug-in will open in Ableton Live 11 running on Monterey M1 Pro it often crashes Ableton.
But it runs without any issues on Bitwig on same OS / M1 Pro etc.
mods: could we lock this thread? It has mutated way beyond its original intention, and the title is very misleading.
1 Like