MuseScore 4 Pipewire still non-functional on the Linux
Hi,
The standard audio system on Linux is now Pipewire instead of Pulseaudio, and the older previous versions of MuseScore (2 and 3) do have a functional implementation of Pipewire connection (on top of initial Pulseaudio support). Some distributions of Linux (such as Arch and Gentoo) package MuseScore 4 with functional Pipewire connection, but there are distros (like Debian) that do not yet have MuseScore 4 which rely on the AppImage, which oddly still doesn't have support for Pipewire.
I think implementation of Pipewire support should be done for the MuseScore 4 AppImage, especially since older versions already have support for the new standard - it's odd for a newer version of the project to be less functional due to being somehow more outdated compared to older versions.
Comments
Update: Gentoo does not. I'm wondering how I got it working in Arch. This makes the case for looking into Pipewire support for Musescore 4 more valuable.
This issue going beyond the AppImage rules out a build error.
The solution of using Musescore 3 can be clunky for one reason or another, and I wish not for it to be made permanent.
Hello, here on archlinux, I struggled a lot with that.
What finaly worked, was to install
pipewire-alsa, restart the pipewire sessionsystemctl --user restart pipewire.serviceand restart musescore (that I got as an AppImage).(and now I still need to work on wayland and get decend rendering)
In reply to Hello, here on archlinux, I… by tristramg@gmail.com
That seems to make sense, I must have had that installed for completeness.
I've recompiled pipewire with the pipewire-alsa flag, which ends up being how that's done in gentooland, and the behaviour has now changed from no playback being possible; playhead not moving at all, nothing audible going on either with heard audio or on visual meters when clicking on notes; to now the playhead moving and audio being visible on the dB meters.
However, still the sound is still not audible. I ran mscore from terminal (
/usr/bin/mscore) and noticed:16:42:50.292 | INFO | main_thread | JackAudioDriver::open | sampleRate used by jack: 4800016:42:50.292 | WARN | main_thread | JackAudioDriver::open | Musescores samplerate: 44100, is NOT the same as jack's: 48000
I wouldn't know how to change this behaviour so that it matches the system sample rate rather than having to do it the other way around. [Edited for formatting]
In reply to That seems to make sense, I… by leylanator
I don't know if this is still an issue.
You don't need Jack for running this if you have pipewire installed. There is a comprehensive video here for your reference https://www.youtube.com/watch?v=3LpXu1-wvlA&t=408s
From my own experience, I can point out some things :-)
- see if you have .asoundrc installed or not.
- use Helvum to visualise your connections ( https://gitlab.freedesktop.org/pipewire/helvum ). It works better than Carla (with pipewire according to me).
- use also pw-top to visualise who is using pipwire (can be confusing at times)
- you can also start musescore with the 'pw-jack /usr/bin/mscore' . It replaced jack compatible libraries with pipewire ones.
Also i ran on Ubuntu 24.04 LTS (on an old mac 2013 btw). Check what pipewire you have installed. This is what I have pipewire/noble-updates,now 1.0.5-1ubuntu1 amd64 [installed,automatic]
I hope this helps,