4.5.1 no sound with pipewire 1:4.1 on Debian testing
I think I'm probably on my own with this, but I'm asking here in case anyone else has experience with troubleshooting Musescore Studio on Debian testing or can explain anything more about the implementation of pipewire. The attached files leave me nonethewiser.
Does anyone know how I can get more useful output from either musescore or pipewire?
Most Debian maintained applications work ok, but I notice Audacity is also complaining, so this isn't a specific musescore problem, however, I need to gather information in order to get help from Debian devs.
It would help if musescore provided more UI configuration options. Preferences > Audio & MIDI > Audio device only offers "System default", most apps give a choice of ALSA, Jack, Pulseaudio etc, which would be useful either for troubleshooting or working around the problem.
The mixer responds as if musescore is playing, so it's clearly the external plumbing which is at fault here.
It all worked perfectly well running pulseaudio through Jackd, but reverting is not at all easy or desirable.
I'm wondering whether building from source would give the opportunity to point musescore to the correct place? I guess there's only one way to find that out!
| Attachment | Size |
|---|---|
| MuseScore_250402_141607_log.txt | 32.48 KB |
Comments
I have read this - it's mostly out of date by the looks https://wiki.debian.org/PipeWire
And 4.5.2 nightly build just locked up my machine.
I probably need to understand these QT errors first.
In reply to And 4.5.2 nightly build just… by timflatus
The logs are flooded with those errors on all Linux systems, with or without pipewire.
In reply to The logs are flooded with… by graffesmusic
The logs are way to verbose to be useful IMHO
In reply to The logs are way to verbose… by Jojo-Schmitz
Either errors are logged to be fixed, or they are not logged at all and ignored. This is just messy.
Are all of these also logged in Windows, or is this only a Linux thing?
In reply to The logs are flooded with… by graffesmusic
OK, so I'm not on my own with the QT problems at least.
FYI: the MuseScore_250402_235057 log contains no info relating to sound because I wasn't even able to load a score!
Does nobody have any idea how to get better diagnostics?
Looks like my only option is to back out of Pipewire entirely and go back to Pulseaudio :(
Ych a fi.
In reply to OK, so I'm not on my own… by timflatus
Start from cmd line with -d (debug) switch maybe.
(i use Pulseaudio ...)
In reply to Start from cmd line with -d … by graffesmusic
Thank you.
I just purged Pipewire and everything works again.
I'll leave this here until Debian fix their Pipewire problems as this is bound to bite someone else in future.