Bug 480622

Summary:	Add a combined sink device so users can select multiple devices for output
Product:	[Plasma] plasmashell	Reporter:	Henning <boredsquirrel>
Component:	Audio in general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	aleixpol, isma.af, jan.selchow, nate, postix
Priority:	NOR
Version First Reported In:	5.92.0
Target Milestone:	1.0
Platform:	unspecified
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=464916 https://bugs.kde.org/show_bug.cgi?id=440536
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Henning 2024-01-31 20:00:57 UTC

An idea: It is said to be possible to create a pipewire device that basically merges multiple devices.

I dont know how this is done and all guides I found where not fitting (Fedora 39 KDE).

Idea:
- add a default combined sink
- add a toggle "select multiple" on the bottom next to "increase max volume"
- if checked, allow to put multiple devices into this merged sink, making output through multiple speakers, headphones etc. possible

I can imagine that this merged device may be prone to breakages, as IDs may reset. But I dont know yet and I imagine it could be annoying needing to re-apply the merge on ever reboot.

Specified App:
pipewire-libs-1.0.1-1.fc40.x86_64
pipewire-1.0.1-1.fc40.x86_64
vlc-plugin-pipewire-3-1.fc40.x86_64
pipewire-pulseaudio-1.0.1-1.fc40.x86_64
pipewire-alsa-1.0.1-1.fc40.x86_64
pipewire-jack-audio-connection-kit-libs-1.0.1-1.fc40.x86_64
kpipewire-5.92.0-1.fc40.x86_64
pipewire-jack-audio-connection-kit-1.0.1-1.fc40.x86_64
pipewire-gstreamer-1.0.1-1.fc40.x86_64
pipewire-utils-1.0.1-1.fc40.x86_64
qemu-audio-pipewire-8.2.0-2.fc40.x86_64

--- Software ---
OS: Fedora Linux 40.20240130.0 (Kinoite Prerelease)
KDE Plasma: 5.92.0
Kernel: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64
Compositor: wayland

--- Hardware ---
CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 5.7 GB
GPU: AMD Radeon Vega 8 Graphics
Video memory: 2048MB
Audio: Pipewire

Comment 1 Nate Graham 2025-12-09 19:34:25 UTC


*** This bug has been marked as a duplicate of bug 440536 ***