Musescore 3.6.2 crashes when opening score with Pipewire/JACK

• May 29, 2021 - 19:46
Reported version
3.6
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

Musescore 3.6.2 crashes when opening a score with JACK on Pipewire 0.3.28, see attached log.

Any idea of where I could look in order to debug this?

Attachment Size
log.txt 3.27 KB

Comments

• Jun 5, 2021 - 09:14

Same for me. At some point (months ago, and I lost the precise config file since then) I solved it by setting the sample rate explicitly to 48000Hz in Pipewire. Still, that does not say why Musescore crashes, as all other audio apps I use are working fine.

Starting musescore with --no-synthesizer does not crash, could be a workaround if you are only using MIDI. But it is not my case. https://musescore.org/en/handbook/3/command-line-options

I attached the Pipwire log file. I also tried to start musescore in debug mode --debug but it did not output any logs?? Documentation is not very helpful here.

Attachment Size
pw-log.txt 66.04 KB

Reply

• Jun 15, 2021 - 02:33

Here's the workaround:
If /etc/pipewire/pipewire.conf does not exist:
1. Create the folder /etc/pipewire
2. Copy the template file from /usr/share/pipewire/pipewire.conf to /etc/pipewire/pipewire.conf. It is not recommended to edit this file directly, but rather create a copy into /etc/pipewire.

Commands
sudo mkdir /etc/pipewire
sudo cp /usr/share/pipewire/pipewire.conf /etc/pipewire/pipewire.conf

if /etc/pipewire/pipewire.conf does exist:
1. Open the file in your favorite editor (with sudo/root permissions)
2. Uncomment the line: default.clock.rate = 48000
3. Save and restart computer.

General Notes:
Pipewire's default is 48khz, so explicitly stating the default shouldn't be necessary.

Reply

• Dec 10, 2021 - 19:02

Try to install package from snap/flatpack - works for me. Even with pipewire-replacement on manjaro. No clock rates helped me.

Reply