#1154266 mpv: please stop complaining about missing pipewire

Package:
mpv
Source:
mpv
Description:
video player based on MPlayer/mplayer2
Submitter:
Oliver M. Schode
Date:
2026-11-19 12:49:01 UTC
Severity:
normal
#1154266#5
Date:
2026-11-18 06:39:58 UTC
From:
To:
Hi.

I'm still often not using Pipewire (PW) and thus don't have it installed
on those machines either, mpv is just configured to use Alsa. Note that
in Debian anyway, mpv thankfully does not depend on the entire PW kit,
only on libpipewire which in turn merely suggests PW. Spurious warnings
about "client.conf" missing were seen in older versions, though usually
only in syslog. I don't remember when but at some point those stopped
which made a lot of sense to me, the presence of PW should be easily
obtainable by other means. If it's not there, no use telling users about
missing config files they do not in fact miss. With 0.42.0-2 the trouble
has unfortunately returned, although now it's also printing (W+E) on the
terminal where mpv is running, "can't load config client.conf...", the
output in fact overlapping with hence garbling mpv's relevant stdout.
Which even though cosmetic is unacceptable and considered a bug.

Mpv isn't least renowned for its minimalism, it runs fine with nothing
available but alsa (and of course, with no audio), it should not
complain about optional components. At the very least we should have
some means or an option to silence this that's more specific and
conservative than --msg-level. What doesn't work is simply placing an
empty client.conf in $HOME/.config/pipewire.


Oliver

#1154266#10
Date:
2026-11-18 21:44:56 UTC
From:
To:
Hi Oliver

FWIW, this message is not from mpv. I also do not see any change
(compared to 0.41.0) in 0.42.0 that would change the order mpv tries
audio outputs. If you want to use alsa without the message from the
pipewire libraries while running the output detection, I would suggest
you to config alsa as the audio output to use.

Closing.

Cheers

#1154266#15
Date:
2026-11-18 21:44:56 UTC
From:
To:
Hi Oliver

FWIW, this message is not from mpv. I also do not see any change
(compared to 0.41.0) in 0.42.0 that would change the order mpv tries
audio outputs. If you want to use alsa without the message from the
pipewire libraries while running the output detection, I would suggest
you to config alsa as the audio output to use.

Closing.

Cheers

#1154266#20
Date:
2026-11-19 12:12:50 UTC
From:
To:
The noise on the command line is coming from stderr, should have been
obvious but wasn't, it's why it's interleaving the normal output, and
why in contrast to what I thought something like
--msg-level=ao/pipewire=no has no effect. So a workaround is to just
always run mpv with 2>/dev/null. That does what I'm asking for but is
clearly not ideal. And then it's still flooding my syslog: I'm used to
run mpv (very) frequently.

Moreover I found out there was a couple of similar bug reports over the
years, some against mpv, some against pipewire, although apparently not
in Debian. In effect however the issue at this time seems to boil down
to how Debian packages pipewire, providing the library without expected
baseline configuration, a practice not supported by upstream. Previously
users who don't run and prefer not to install pipewire could make use of
the package pipewire-audio-client-libraries, apparently filling some
gap, it's now transitional. I'm not sure whether mpv is even the right
place or whether the bug would better be filed against (lib)pipewire. If
you think so, please feel free to close, or if possible forward. Yet I
still feel like it should get noted somewhere.

#1154266#25
Date:
2026-11-19 12:47:23 UTC
From:
To:
Again, if you do not want the auto configuration to happen, force the
one you want to use, e.g.: mpv --ao=alsa (or you put that configuration
into your mpv config).

Cheers