I hope once the work to port to ARM is done for M1/Apple Silicon, that will pave the way for ARM Linux builds as well. I’d love to use a Pi as a headless VCV station.
I’m not sure this is the place to post this, but PurrSoftware Meander module has been built and tested for M1 ARM functionality. I do not plan to set up automated builds and distribution but will wait until VCV adds ARM builds to the library build chain and processes.
Until then, if you are willing to build Meander yourself, it should work. If there is a better topic to put this under, moderators feel welcome to move it.
So far things are working fine in my test builds. One peculiarity is that the VCV Rack 2.2.0 arm64 build installer requires Rosetta to be installed. It’s also a bit harder to test since there aren’t any macOS VM hosts that support OpenGL in the guest OS (that I’m aware of) so it requires dancing back & forth with symbolic links for the Rack2 folder.
But besides that, smooth sailing so far. It’s soooo nice to finally be able to get around the single-thread limitation of VCV2 on Arm Macs!
If you want to send a note to support letting them know, the diff below is the pkgbuild diff you need to generate a universal installer (independent of the underlying architecture of the installed assets) and that allows installers to run absent rosetta
I don’t know that it is anything official, but I also have run into it. I cannot get decent sound on my MacBook M1 Air unless I restrict the rack engine to 1 thread. Thankfully the machine handles all the patches that I throw at it using 48kHz, despite the limitation. Of course some patches can be run at higher rates.
I am salivating at the prospect of being able to use more threads. Not because I need more complex patches, but I’m dreaming of being able to run all my patches at 96kHz or higher, which can make a big difference with FM and wavefolding, etc. Time will tell if that dream becomes reality.
Yes, exactly this. Apple Silicon running VCV Rack 2 in Rosetta is limited to a single thread. Well, not technically limited—you can select as many threads as you like, but the performance only degrades with more cores. So I’ve had to get creative with fitting big patches into a single core’s worth of performance (which is quite a lot in the case of the M1 Max)
I wondered about that, too. But thinking about it, I think VST plugins each run on a single thread. I expect most plugins do. Just like with VCV each module runs on a single thread, even though VCV itself may run multiple threats.
Now I’m more curious - in what plugin environment may a single instance of VCV run with more than one thread?
Of course OP doesn’t say if they are running VCV stand alone, or as a plugin, so I may be jumping to conclusions.
