Bug 280505 - multimedia/pipewire: no audio after 1.0.4 update
Summary: multimedia/pipewire: no audio after 1.0.4 update
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Gleb Popov
URL:
Keywords: needs-patch
Depends on: 272004
Blocks:
  Show dependency treegraph
 
Reported: 2024-07-30 10:58 UTC by Jan Beich
Modified: 2024-10-25 16:20 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (arrowd)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer freebsd_triage 2024-07-30 10:58:51 UTC
Regressed by ports b762a45031e7. WirePlumber like MediaSession needs spa-alsa for audio support or configured to use spa-jack.

$ exec dbus-run-session sh
$ daemon -f pipewire
$ ffmpeg -i /path/to/foo.mp4 foo.wav
$ pw-play foo.wav &
$ wpctl status
[...]
Audio
 ├─ Devices:
 │
 ├─ Sinks:
 │
 ├─ Sources:
 │
 ├─ Filters:
 │
 └─ Streams:
[...]

Note1: if wpctl is used with MediaSession (after reverting b762a45031e7) it'd show "PCM Sink" and "PCM Source" with associated volumes.
Note2: This port probably needs pkg-message to discourage new users from using PipeWire for audio until it gains OSS backend (like PulseAudio).
Disclaimer: I don't use PipeWire. Some of my ports require PipeWire but only for video (workaround for missing wlr-screencopy-unstable-v1 in Firefox/Chromium).
Comment 1 Gleb Popov freebsd_committer freebsd_triage 2024-10-25 16:20:04 UTC
> Disclaimer: I don't use PipeWire.

I don't use it either, so I have to idea what's the correct path forward for this issue. Does newly committed audio/pipewire-spa-oss improve things or it is completely unrelated to this PR?