Has anyone been able to run MuseScore 3.7 on MacOS?

• Mar 26, 2023 - 07:04

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

• Mar 26, 2023 - 17:34

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

Reply

• Mar 26, 2023 - 17:29

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

Reply

• Mar 26, 2023 - 17:53

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

Reply

• Jun 16, 2023 - 12:51

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

Reply

• Feb 1, 2024 - 05:08

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.

      MuseScore 3.7.0.7709149398 Devel.app_.png

I tried the instructions from appletoolbox.com

      Allow apps downloaded from - Anywhere.png

... 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:

      Is Damaged - Open anyway button.png

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

Reply

• Feb 14, 2024 - 04:24

> @ 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

Reply

• Feb 14, 2024 - 14:12

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!

Reply

• Feb 14, 2024 - 19:12

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...

Attachment Size
Screenshot 2024-02-14 at 2.10.02 PM.png 93.03 KB

Reply

• Feb 14, 2024 - 19:57

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:

     Privacy and Security _ Open Anyway.png

The following image shows Open anyway missing on my system. Maybe there's some Security setting that enables that security option?

     Privacy and Security _ NO Open Anyway.png

scorster

Reply

• Feb 16, 2024 - 20:34

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)

MuseScore 3.7 MacOS Ventura preferences IO.png

Reply

• Feb 19, 2024 - 20:04

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.

Reply

• May 21, 2024 - 10:22

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?

Reply

• May 28, 2024 - 18:17

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.

Reply

• May 28, 2024 - 22:45

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

Reply

• May 29, 2024 - 19:15

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.

Reply

• May 28, 2024 - 22:46

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

Reply

• May 29, 2024 - 19:20

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.

Reply

Do you still have an unanswered question? Please log in first to post your question.