Hey 
Just got a new Macbook Pro M1.
Wondering if anyone have tried it yet?
is everything running okay via Rosetta2?
Thanks in advance!
Anyone running Axoloti on Macbook M1?
jaffasplaffa
#4
Not sure I am not that code savy. But pretty much all other formats and apps I use on the M1 Mac needs to be build for this specific chipset, so I was just kind of assuming it would be the same with Axoloti. If it's not build for this specific chip they have to run in Rosetta2 mode.
Rosetta2 converts applications written for Intel chips in real time, so it works on silicon chips. Obviously that will have an effect on efficiency. Tried using Logic via Rosetta2 mode, so I could use plug ins made for Intel chips and it was not a good experience, it did not work super well. Of course Axoloti is a lot simpler, so probably not same issues.
jaffasplaffa
#5
Just did. The app opens. Did not test anything yet or connect the board, but the app opens
Since it is an Intel app it does run via Rosetta2, you can see that it says Intel next to the Axoloti app, if it was a M1 native app it would say Apple, like all the other apps:
But yeah, will test it out in the near future
janvantomme
#7
I've tried installing tonight and I can confirm that it works. I've got a test patch running on a board right now. Did run into a lot of these windows though when trying to compile a patch.
jaffasplaffa
#8
Thanks. Someone else already confirmed it working, via Rosetta2 layer. I guess better than nothing 
Anyway, have been caught up with VCV rack since I got this computer, so haven't really tried actually connecting the boards yet myself. Maybe sometime later I will
servandisco
#9
Is funny that Apple warns that others might want to see your personal information when they are the ones collecting info... : https://sneak.berlin/20201112/your-computer-isnt-yours/
thetechnobear
#10
theoretically, getting this to work natively should not be too difficult....
as others have pointed out, the axoloti code is all in java, so will work ok.
it does however use a number of other binaries , things like the arm compiler are already available (I use them for other projects on the M1, and install via homebrew). similarly libusb etc used for flashing are all available. (again Ive tested and are running fine)
the main "issue" is likely versions numbers have changed (and original older versions are unlikely to be available for m1) , but thats primarily just a matter of updating to what's available, and then configuration to correct paths etc.
of course, there is a possibility, that newer versions of things (like java) might introduce some quirks, as backwards compatibility is not always 100%.
there also may be new 'permissioning' issues with the newer macOS versions , though if its working under Rosetta2 I suspect thats ok.
some pointers on what's involved...
this is NOT a how-to...
just rough steps in case someone is interested in trying, and piecing it together.
it is not complete... nor tell you where you need to get the appropriate bits, that is all left for the explorer.
there are two ways you could potentially get a native build running...
a) use released axoloti code
install java jdk/jre for apple silicon.
grab the released axoloti code, and just use the jar (java code), and chibios then install things like the arm compiler manually, and point to it.
the scripts that axoloti uses have been made nicely generic, so changing paths is actually straightforward.
(in fact iirc, you point to your own runtime in the app)
b) build from GitHub
install java jdk for apple silicon.
the scripts are very generic, and there's some documentation.
basically Id expect build.sh to fail (or at best end up giving you an intel binary!), basically the platform script would need to be updated to point to new apple silicon versions of things like arm compiler, and libusb
really, what Im trying to say... is its a bit fiddly/time consuming (*) to sort out, finding the right things,
but I don't think there will be any major hurdles in getting it working.
in fact, Ive ported a few of my projects to M1 over the last year, and have generally its been pretty straightforward.
(*) unfortunately, I don't have time to do it at the moment, hence why Im posting, rather than just doing it