Musescore 3 on Apple M1 not playing the score
Hello there,
I'm using Musescore (version 3.6.2.548020600) on the new MacBook Air with M1 chip. My problem is that whenever I try to play a score it doesn't do anything at all. I've noticed that the playback commands are greyed out. I've tried to reinstall and initialize the program but that doesn't solve.
I guess it's some kind of a problem related to the emulation with Rosetta because I don't have this issue with the same version of MS running on my late 2013 iMac. But that is just a guess, I can't seem to find anything related to this problem.
What do you think?
Comments
> "I guess it's some kind of a problem related to the emulation with Rosetta"
It's not, there are already quite some users that run on M1s successfully.
Have a look at https://musescore.org/en/node/96811 for possible causes and proposed solutions
In reply to > "I guess it's some kind of… by jeetee
Thank you for the feedback. I've tried everything that is listed in the link and I've noticed that I can't choose any API or audio device from my I/O settings. I don't think that's related to the drivers though because any other program that I use recognizes Core Audio perfectly. What could it be?
In reply to Thank you for the feedback… by rossocarmine
You tried the PRAM reset? People often miss that one, but for Mac specifically that seems to be the most likely culprit.
In reply to You tried the PRAM reset? … by Marc Sabatella
I've heard that PRAM reset is not possible anymore with the introduction of the M1 chip, and PRAM/NVRAM will be automatically managed during the system shutdown. After all the option+command+R+P does nothing
same problem here. I can't fix it. If you solve this problem, plz write comment. help me
In reply to same problem here. I can't… by shinesunhn
See the replies bove and follow all of the suggestions given in the article that was linked. Follow each very carefully.
Hi again!
Just wanted to let you know that some time after the update to iOS Monterey, so without even expecting it, I've found the problem solved by itself. I really don't know what happened but the only thing I have changed since my last try was to update the operating system, that's for sure.
Just in case this helps someone,
thank you again for the replies