Mixer and synthesizer in my View menu is greyed out, and playback wont work on MS3

• Jan 3, 2020 - 01:04
Reported version
S3 - Major

No playback, Mixer, synthesizer and play panel are greyed out, portaudio drop downs in i/o menu are empty. My machine runs macos 10.15.2 Catalina.


In reply to by Jojo-Schmitz

I checked that I installed all the SoundFont, tried all of the https://musescore.org/en/node/96811, none of them works: gave my MS3 all the disk permission, reverted to the factory setting, reinstalled MS3 and soundfonts, Restarted the Audio and MIDI Devices, reset the PRAM/NVRAM like the link suggested, my computer does not have touch bar, i really don't know what else i can do here to make it works. So plz help me! Thanks

In reply to by Jojo-Schmitz

Anything new on this ? I had some hope for a fix, as ONE TIME (!) i launched Musescore and had everything working.. Then I checked, I had the same version as before... So it seems to randomly work, but one time on like more than 200 launches..

Type Functional Graphical (UI)
Reported version 3.3 3.5

I started having this problem this morning. Yesterday it worked. I have tried resetting to factory defaults, restarting the audio engine and installing the latest version and updating the soundfont file. From reading another thread I entered these commands:

$ /Applications/MuseScore\ 3.app/Contents/MacOS/mscore -F
dlopen error : dlopen(libjack.0.dylib, 1): image not found
dlopen error : dlopen(/usr/local/lib/libjack.0.dylib, 1): image not found
$ /Applications/MuseScore\ 2.app/Contents/MacOS/mscore -F
-bash: /Applications/MuseScore 2.app/Contents/MacOS/mscore: No such file or directory

I am running macOS Catalina 10.15.6.

Attachment Size
Screen Shot 2020-08-19 at 7.50.08 am.png 37.85 KB

I am still getting the problem. It is intermittent. Some days it appears and some days it doesn't. Sometimes resetting the NVRAM helps and sometimes it doesn't.

At the moment it does not work. When I run MuseScore by opening a file I get the following error in the system console.

xpcproxy[810]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

Close and restart , the next error message.
xpcproxy[926]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

If I open MuseScore with no open file there is no message. But then when I create a new empty score this error:

xpcproxy[1274]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

In reply to by cohenjonathan

to add: following this error, musescore immediately crashes on attempting to open. hence is unusable. this seems to be 100% reproducible, and happens not only w musescore 3.5 but also musescore 3. doesn'tr hapen with musescore 2.3.2. (but that older version won't open scores I had previously been working on in later versions, so I'm a bit flummoxed at the moment.)

I want to make sure you have tried starting MuseScore from the command line using the -F (capital F) to start MuseScore. If so, explain what happens when you start MuseScore normally.

mh ? What don’t you get ?
The issue has something to do with Handling portaudio under Catalina yeah.
It’s the only one of all my music software that hasn’t passed the update correctly, I’m not gonna try downgrading and thus having to reinstall/reconfigure 150Gb+ of software/VSTs/etc.. for one small soft.
Is it clearer ?
Now if you don’t have anything that can help me on working around this issue, don’t bother writing on this thread ty ;)

In reply to by Jojo-Schmitz

Do you really think Apple is gonna do something about PortAudio not being able to get through mac os updates ?..
I mean all my softwares went wrong after update, from Photoshop to VLC, Cubase, etc..
They all shortly released updates and everything was fine again. Catalina was a major fuck up update, ok, but Musescore has to adapt, thinking the other way around could be a solution is just living in an unicorn world.

Regression Yes No

Not a regression as far as I can tell. Or can you? Then name the version that doesn't have the issue.

Indeed we're looking for ways to reproduce this

In reply to by Jojo-Schmitz

Yeah sorry it's a regression inherited from this sh^$`ù OSX update.
So I might have found something.

I was checking for the 100th time every settings I could, then I remembered something : I have this setup where I have sometimes 2 audio cards up and running together.
To use them together, i configured an "aggregated device" in this utility called "Audio & MIDI Setup" (sry if the translation is not perfectly correct, I'm french).
It worked perfectly before Catalina, not causing trouble to any app, but I had never tried deleting it since I had my troubles with Musescore... So I did, and it seems to have solved my problem. For now at least, as I know I had some periods of time where Musescore works again for a few days. I restarted my computer and Musescore a few time, the playback seems to be up again, and I even have the correct devices in I/O menus !

Yay !!..for now ? :)

In reply to by fredbrault

Some news on reproductibility.

Sometimes when I turn back on my mac from sleep, the playback fails again, and the only thing that can be done is reboot and hope for it to be back.

I tried to write down the reboot behavior :

What I've noticed is that if I tick "re-open all apps when rebooting" and I have other sound apps on like logic, ireal, etc, most of the time it will fail. (9 out of 10 reboots, playback still doesn't work)
It will also fail most of the time if I don't tick it (8 out of 10 here)
I have more chance of getting a lucky reboot if I close all apps except musescore, then reboot and tick the "reopen apps" ( only 3 fails to launch playback on 10 reboots).

From my point of view, it looks like musescore doesn't like if it's not the first app to grab audio driver or sth like that..

I don't even know if that is interesting for you, but it's all I can do ..