Has anyone been able to run MuseScore 3.7 on MacOS?
I successfully downloaded MuseScore 3.7. It's an unsigned app so the first step was to register MuseScore 3.7 as an exception on my Mac, per Apple's instructions.
That allowed me to initiate a launch under MacOS 13.2.1 ... but then MuseScore 3.7 abended.
On reviewing the crash log Jojo noted the missing Qt library ”QtWebEngineCore”. He said it "Might be a bad packaging," but that would be hard to determine, as he doesn't have a Mac.
So I'm wondering: Is anyone successfully in running MuseScore 3.7 on MacOS. If so, how?
One proposed workaround is to launch MuseScore 3.7 from the Terminal command line with -w. That should prevent MuseScore from accessing the web, hence no need for that missing library.) I've tried an failed various ways of launching 3.7 from the command line, without success. Can anyone offer a command that works?
Another proposed workaround is to install Qt 5.15.2 on my system. I’d only want to install Qt if I’m going to start using it—and that seems unlikely anytime soon. All to say, I haven't tried this approach.
Anyone?
scorster
Comments
Did you try it like described in https://musescore.org/en/handbook/3/revert-factory-settings#instruction… ? Just using -w instead of -F?
Did you try staring Musescore by double-clicking a score file or draging a score file onto MuseScore ?
If that works you could disable the startcenter.
In reply to Did you try it like… by Jojo-Schmitz
On your advice I attempted to start 3.7 by dragging a score onto it provoked the same crash.
I'm in unfamiliar territory with the Terminal but tried that approach.
Don't know if I have the part after \ correct.
• Need a different file name?
• Need a space before 3.app?
• Since the handbook used a capital F I used a capital W:
JBs-mb-5:~ John$ /Applications/MuseScore\3.app/Contents/MacOS/mscore -W
/Applications/MuseScore\ 3.app/Contents/MacOS/mscore -W
dlopen error : dlopen(libjack.0.dylib, 0x0001): tried: 'libjack.0.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibjack.0.dylib' (no such file), '/Applications/MuseScore 3.app/Contents/Frameworks/libjack.0.dylib' (no such file), '/Applications/MuseScore 3.app/Contents/Frameworks/libjack.0.dylib' (no such file), '/usr/lib/libjack.0.dylib' (no such file, not in dyld cache), 'libjack.0.dylib' (no such file), '/usr/lib/libjack.0.dylib' (no such file, not in dyld cache)
dlopen error : dlopen(/usr/local/lib/libjack.0.dylib, 0x0001): tried: '/usr/local/lib/libjack.0.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/lib/libjack.0.dylib' (no such file), '/usr/local/lib/libjack.0.dylib' (no such file)
Unknown option 'W'.
Then I tried a lowercase -w:
-bash: /Applications/MuseScore3.app/Contents/MacOS/mscore: No such file or directory
In reply to On your advice I attempted… by scorster
It is lower case w
/Applications/MuseScore3.app/Contents/MacOS/mscore -wBut see https://github.com/Jojo-Schmitz/MuseScore/pull/93 and the artifacts that's going to build
In reply to But see https://github.com… by Jojo-Schmitz
And an additional hint I mentioned there...
In reply to But see https://github.com… by Jojo-Schmitz
Hi Jojo,
Thanks for all this!
I'm only casually familiar with Github. So I'm unclear.
Are you saying there's a pending build, or is there a current build of 3.7 for MacOS that addresses the issue in pull 93? If there's a current build, is there a link to the build zip file at the link you provided? Or can you post a direct link to build file?
Thanks!
scorster
In reply to Hi Jojo, Thanks for all this… by scorster
There's an articfact available from https://github.com/Jojo-Schmitz/MuseScore/actions/runs/4524440406
Edit: no longer available, but see below
In reply to There's an articfact… by Jojo-Schmitz
It works!!
Just one temporary glitch: Initially there was a prolonged hang at the MS 4 update advertisement dialog. Clicking OK wouldn't dismiss it and I couldn't do anything else. After about 20 seconds that rectified. And thankfully, since the second launch of 3.7 I can immediately dismiss the advertisement.
I was surprised that only the default plugins don't show in the Plugin Manager. 3.7 has its own plugin repository?
Again, thanks for all this Jojo!
scorster
In reply to It works!! Initially there… by scorster
Being a development build it expects the plugins in a different place, check the preferences
Edit: no longer the case, it now uses the same settings as 3.6
In reply to Being a development build it… by Jojo-Schmitz
Thanks. I pointed 3.7 Preferences>General>Plugins to the folder I use for 3.6. And that works!
In reply to There's an articfact… by Jojo-Schmitz
New artifact (using Qt 5.9) at https://github.com/Jojo-Schmitz/MuseScore/actions/runs/5289563906
Edit: no longer the above, but now at: https://github.com/Jojo-Schmitz/MuseScore/actions/runs/6855313675
Edit 2: feel free to ping me for updated versions
But also try the one from https://github.com/Jojo-Schmitz/MuseScore/actions/runs/5288485843, it uses Qt 5.15.2 but has some Mac specific compilation fixes
In reply to New artifact (using Qt 5.9)… by Jojo-Schmitz
Jojo where can I download a windows build of Musescore 3.7?
In reply to Jojo where can I download a… by dmusicman
Check the lastest build for the 3.x branch that is for Windows at https://github.com/Jojo-Schmitz/MuseScore/actions
In reply to New artifact (using Qt 5.9)… by Jojo-Schmitz
Now see https://github.com/Jojo-Schmitz/MuseScore/actions/runs/7709149398
In reply to Now see https://github.com… by Jojo-Schmitz
Thanks for your continuing efforts on this Jojo.
I downloaded MuseScore 3.7.0.7709149398 Devel.app and I'm sorry to report that MacOS Ventura (13.5.2) still gives the so called "damaged" alert.
I tried the instructions from appletoolbox.com
... but there was no Anywhere option in Privacy and Security >Security
I tried the next recommendation on that page, which was to ** Add The App As a Developer Tool** but:
a) when added MS 3.7 to the "developers" list identified it as MuseScore 4
b) double clicking MuseScore 3.7.0.7709149398 Devel.app still provoked the "damaged" alert
. . .
I also tried the first set of instructions from iboysoft.com but there was no Open Anyway button:
I did not try the Terminal options suggested by either website, and I'd rather postpone that until someone with more Terminal experience can confirm that it works and provide a list of possible caveats.
Thanks!
scorster
In reply to Thanks for your continuing… by scorster
Hello! Curious if you every got MS 3.7 working on macOS?
I'm running Sonoma 14.1. I've tried several different installations from GitHub, and I keep getting the "damaged" alert too.
In reply to Hello! Curious if you every… by jdaniel220
> @ jdaniel220 • I'm running Sonoma 14.1. I've tried several different installations [off of MS 3.7] from GitHub, and I keep getting the "damaged" alert too.
Sorry to hear that. I'm dead in the water here with the latest MS3.7 builds.
Early on, and though it was challenging to install, I eventually I got the March 26, 2023 MuseScore 3.7 version running on MacOS Venture 13.5.2:
MuseScore version (64-bit): 3.7.0.4524440406, revision: github-musescore-musescore-f3d36a3
Can't remember the steps off the top of my head, but it was from the advice in this thread.
Please keep us posted on your progress. I'd really like to be able to use the latest builds. Mine is nearly a year old.
scorster
In reply to Sorry to hear that. I'm dead… by scorster
Thanks for the info! I may try one of the earlier versions. I've been seeing elsewhere that the "damaged" file warning sometimes owes to security features on Mac, and you can experiment with turning off some of these protections and then open it. Not sure, but I'll keep trying.
Thank you!
In reply to Thanks for the info! I may… by jdaniel220
Check whether https://github.com/musescore/MuseScore/wiki/Downloading-and-running-tes… helps
In reply to Check whether https://github… by Jojo-Schmitz
thanks for your help! I did try the steps in the above link. It seems that I can run 3.6 builds going through the steps suggested. (All went just as described in the link--got an error message but ignored it, control-clicked the app icon to open it anyway and indeed it did open and run fine.)
However, it seems I can't run the 3.7 builds. I keep getting the error message and it just won't open...
In reply to Check whether https://github… by Jojo-Schmitz
I also tried the instructions in the link above.
Got the expected "damaged" alert. Then I followed the instruction to Cancel and Right-click>Open
Here on MAcOS Ventura 13.5.2 that provokes the same alert.
Thanks for staying on this.
These are Apple's official "consumer" instructions for this sort of situation:
https://support.apple.com/en-us/102445
But the Open anyway choice does NOT in my Security panel;
Apple's support page shows the Open Anyway option:
The following image shows Open anyway missing on my system. Maybe there's some Security setting that enables that security option?
scorster
In reply to I also tried the… by scorster
Does
xattr -c /path/to/MuseScore.apphelp?See also https://github.com/Jojo-Schmitz/MuseScore/issues/118
In reply to Does xattr -c /path/to… by Jojo-Schmitz
Jojo-Schmitz wrote> Does xattr -c /path/to/MuseScore.app help?
Yes. Thanks Jojo. Another step forward!
I ran the xattr-c terminal command on MacOS 13.5.2 and it successfully removes the quarantine attribute from MuseScore 3.7.x
So now MuseScore indeed opens and appears to operate normally, with one big exception: There's no playback:
• The playback controls are disabled (grayed out.)
• And the I/O>PortAudio menus are empty (in Preferences>I/O)
In reply to Jojo-Schmitz wrote> *Does… by scorster
Well, this doesn't seem to be related to notarization
In reply to Well, this doesn't seem to… by Jojo-Schmitz
Jojo-Schmitz wrote > Well, this doesn't seem to be related to notarization.
Correct. It appears I've hurdled the notarization issue.
Nevertheless less that previous post is related to the opening title: "Has anyone been able to run MuseScore 3.7 on MacOS?"
I'm a huge fan of your ongoing efforts and what you've accomplished in MuseScore 3.7 Evolution.
And I'm hoping someone can help with the Playback issue on MadOS. I'm certainly wondering if anyone else has encountered it. I've never had a I/O Preference issue on any previous installation.
In reply to Jojo-Schmitz wrote > Well,… by scorster
on MadOS Freudian slip? 😜
In reply to on MadOS Freudian slip? 😜 by Jojo-Schmitz
I am on "MadOS" (Sonoma) too, and I have the same problem (already reported in another thread)...
In reply to I am on "MadOS" (Sonoma) too… by johngreen
Thanks for the heads up. Is this the post?
https://musescore.org/en/node/342126#comment-1196746
scorster
In reply to Thanks for the heads up. Is… by scorster
Yep, that's the very one!
In reply to on MadOS Freudian slip? 😜 by Jojo-Schmitz
That's hilarious.
Yes Freudian. It's when you say one thing but mean your mother!
In reply to Well, this doesn't seem to… by Jojo-Schmitz
Any progress? The latest build still has the same issue...
In reply to Any progress? The latest… by johngreen
Just checked out the latest build (Treat svgz file as a vector image #2407).
Still no sound, BUT I found the following comment in the annotations:
build
No such keg: /usr/local/Cellar/portaudio
Would that possibly help to solve the sound problem on MacOS?
In reply to Does xattr -c /path/to… by Jojo-Schmitz
well I think I need grade level help, because I don't even know how to use Terminal properly. Here's the notice I get when I try the xattr-c workaround. I'm sure I'm missing something obvious...
In reply to well I think I need grade… by jdaniel220
There needs to be a space before and after the -c
In reply to There needs to be a space… by Jojo-Schmitz
thank you for your ongoing help. Unfortunately I just don't think 3.x is in the cards for me!
I was able to get it to run, but it took some digging, and I just use a Mac; I don't know a thing about them or computer programming in the least. I've listed the how-to's for each. For me it was #3 that worked. Report based on my system, which is Ventura 13.3.
There seem to be three levels of fix you can go for. This is the order I went in, which seemed least fiddly to most fiddly.
1) tell Mac OS to allow you to open apps from anywhere;
2) add the software as a "Developer Tool"
3) remove the quarantine flags from the software.
1) Tell Mac OS to allow you to open apps from anywhere.
System Settings → Privacy & Security: Security (near the bottom). Choose the radio button "Anywhere" for "Allow applications downloaded from".
Ventura's System Settings/Privacy & Security on my computer didn't already have that option, but there's a terminal workaround that will put that button there for you. Instructions are edited from from a website where learned this.
1. Quit out of System Settings if it is currently open.
2. Cut and paste this command into Terminal: sudo spctl --master-disable .
3. Press "return", enter password as prompted.
4. Return to System Settings. The option will now be there.
5. Try running MuseScore.
2) Add the software as a "Developer Tool".
Assuming you have installed MuseScore Evolution,
1. Go to System Settings/Preferences → Privacy & Security → Developer Tools (near bottom)
2. Use the " + " button to add MuseScore "Allow the applications below to run software locally that does not meet the system's security policy"
3. Try running Musescore again.
3) Use the "xattr" command to remove the quarantine flag from the MuseScore build that the system claims is damaged. The website where I got this advice recommends this as a last resort. It happens to be the one that worked for me.
1. Cut and paste this command into Terminal: xattr -r -d com.apple.quarantine
2. Enter the path to MuseScore. (Drag/drop the MuseScore's icon to Terminal's cursor does this.)
3. Press "return".
If Terminal says it's not allowed to do the operation, type "sudo", space and then repeat the syntax above with the pathname. It will then prompt you for a password. This is what I ended up doing, but now it runs on my computer.
In reply to I was able to get it to run,… by RickyChitarrone
Oops, and now I see JoJo dealt with this already. Ugh, I am such a noob.
In reply to Oops, and now I see JoJo… by RickyChitarrone
Hey that was a nice newly worded summary.
Say, are you able to get audio to play?
https://musescore.org/en/node/347226#comment-1229390
In reply to Hey it was a nice summary,… by scorster
I wish I got it to play. I got as far as the xattrib part of the thread (this very same one) and realized I wasn't emotionally ready to go back to terminal, especially on a guess that it might work. I'm too much of a novice—not even novice, really—when it comes to code-level things. If it's a proven solution to get the audio running (I'd love to hear where my errors are in the score, because it's lute tablature, not notes), I'd be all over it. So, did I miss anything? Is this solved? If not, are the geniuses at GitHub on it?
Oh man, you said "say" as an interjection in your note. I love, love, love it! It's like meeting Cary Grant on a message board. —R
In reply to I wish I got it to play. I… by RickyChitarrone
@RickyChitarrone,
Sorry, I didn't get the meaning.
In your MuseScore 3.7 Evolution, is audio device available or unavailable?
In reply to Oops, and now I see JoJo… by RickyChitarrone
@Jojo-Schmitz,
As a known issue and workaround for Mac users,
I think it would be better to describe about "run command xattr" on the MuseScore 3 Evolution Wiki.
https://github.com/Jojo-Schmitz/MuseScore/wiki
In reply to @Jojo-Schmitz, As a known… by knoike
I've link from it to here meanwhile
In reply to I've link from it to here… by Jojo-Schmitz
Hi Jojo, do you mean that you'd like me to post the solution on the Issues section for Evolution on GitHub? I apologize for being so thick about these things, but I can barely grasp what a wiki is or how to use one. I might end up being very clumsy about it, if that's okay.
Meanwhile, thanks for being such a great and patient advocate on this forum. Not to mention your programming gifts! Evolution saved my ability to continue work on a project while MS4 kept stalling my progress with various instabilities.
In reply to Hi Jojo, do you mean that… by RickyChitarrone
No, it is fine as it is for now
In reply to @Jojo-Schmitz, As a known… by knoike
Here are the steps I've taken to try to get MuseScore 3.7.0.10717483411 running on my Mac.
I downloaded MuseScore-3.7.0.10717483411.dmg for MacOS 13.5.2.
OS: macOS 13.5, Arch.: x86_64, MuseScore version (64-bit): 3.7.0.10717483411, revision: 495c4d4
After installation the MuseScore application (MuseScore 3.7.0.10717483411 Devel.app) is in my main applications folder (not my User Applications folder.) And as expected, double clicking the app provokes the "damaged app" alert.
To render the app viable—by removing the quarantine via a Terminal xattr -c command—I opened the Terminal utility and entered following at the Terminal prompt:
• John$ xattr -c (note that I included a space after the c
• then I dragged the MuseScore app from the applications folder to the Terminal window. That step added the directory path to the command, yielding this:
John$ xattr -c /Applications/MuseScore\ 3.7.0.10717483411\ Devel.app
• Then I pressed return
• I double-clicked tthe app to open it
Now there's no alert ... but the 3.7.10717483411 app never opens. when double-clicked
However, it opens if I drag a score onto its app icon. It appears to operate normally EXCEPT there's still no audio because no sound devices show in the MuseScore>Preferences>I/O>Port Audio>Device.
Please advise.
scorster
P.S. Sorry, I was under the impression that the QT reversion will allow this 3.7.0.10717483411 to play audio on MacOS.
In reply to Here are the steps I've… by scorster
BTW, originally I attempted an alternate solution by adding MS 3.7 to the Developers Tools list, as recommended above.
Two things struck me as odd:
1) In the Developer Tools panel I pressed the + button and chose MuseScore 3.7.0.10717483411. Afterwards I was returned to the Developers Tools panel, but didn't see MuseScore 3.7.0.10717483411 added to the list
2) I noticed MuseScore 4.4.1 listed Developer Tools. And I definitely did NOT add it to the Developers Tools list. Does MuseScore 4.4.1's installer change that setting??
In reply to Here are the steps I've… by scorster
No idea what '...Devel.app' might be?
Edit: ah, I see now, it is a folder inside the .dmg
In reply to No idea what '...Devel.app'… by Jojo-Schmitz
Sorry, I reworded my post to make it more clear.
Thanks for looking into this.
In reply to Sorry, I reworded my post to… by scorster
Pity, still no sound... So it isn't the Qt version apparently
Is it Apple silicone?
In reply to Pity, still no sound... So… by Jojo-Schmitz
@Jojo-Schmitz wrote
> Pity, still no sound.
I know. And I appreciate your attempts to get recent versions of MS3.7 working for MacOS AND all you do for MuseScore and MuseScore Evolution 3.7.
Regarding Apple Silicon, yes I'm on a M2 MacBook Air.
I wonder if others can get the latest 3.7 running on non silicon Macs. Hopefully someone will report back!
In reply to I was able to get it to run,… by RickyChitarrone
I'm a user of for Windows version, but I interested in this issue and its workaround.
I think that the workaround procedure you described seems like a good solution.
In particular, I'm interested in doing run command
"xattr -r -d com.apple.quarantine /path/to/MuseScore.app"
instead of
"xattr -c /path/to/MuseScore.app" .
After running this command, is your audio device available in MuseScore 3.7 Evolution ?
The recent version has a issue that the audio device is not available(not visible) from it.
https://musescore.org/en/node/347226#comment-1229390
In reply to I'm a user of for Windows… by knoike
Nice to meet you ( はじめまして！). Zannen nagara—unfortunately—I have not found a solution to make audio run in Evolution. Any discussion I've come across on the topic has been too technical for me to understand whether the solution is simply proposed or proven.
In reply to Nice to meet you ( はじめまして！)… by RickyChitarrone
Oops, I was not clear. That command is what made the Mac OS allow Evolution to be installed. It had no effect on the audio, which does not work on Mac for the time being.
In reply to Oops, I was not clear. That… by RickyChitarrone
こちらこそ，はじめまして！(Nice to meet you too!)
I see. Thank you for answering, it became clear.
It's unfortunate that the audio device doesn't work in your Evolution, but I'm glad too that you are able to get it working after much effort and try & error.
In reply to こちらこそ，はじめまして！(Nice to meet… by knoike
I might have come across a clue to why this version of Evolution doesn’t play audio. It does play just fine from the same install file on my old MacBook Peo running OS Mojave. Maybe it has to do with the later OS for Silicon/M1 chip architecture, which is what my main desktop computer is. I was surprised to hear it working on my laptop.
If you know that the Mac playback issue has been addressed in a later release of Evolution, please let me know. Otherwise this observation might provide a clue to the developers for resolving the problem.
In reply to I might have come across a… by RickyChitarrone
@RickyChitarrone wrote (parphrased) I might have come across a clue to why this version of Evolution doesn’t play audio. MS3.7 plays fine ... on my old MacBook Pro running OS Mojave. So maybe [the current 3.7 audio device playback glitch is due to] the later OS for Silicon/M1 chip architecture.
Wow. No one else has mentioned that MS3.7 runs on non M1 Macs under Mojave. Thanks for posting.
Hopefully you clue leads to unraveling this major and longstanding stuck point!
In reply to @RickyChitarrone wrote … by scorster
I just saw the thread that began on Sept 13. I simply put my info about its working entirely on an older Macbook with OS 10.14.6 (Mojave) where it seemed chronologically latest in this thread. But someplace it branched out, and this information I posted seems not to be part of the discussion. It might be a valuable clue to whoever is in a position to solve it. Where exactly along the line should I repost this info?