With Bluetooth 5.2 there is a new feature. We can connect several headsets according several persons can hear the song coming from VLC for example. I get two headsets connected with bluetooth kde management, but plasmoid-pa only offers to select one headset at the same time. Today, plasmoid-pa supplies an exclusive choice between two sinks. We need an inclusive choice according to select two headsets as sink for example.
I sent a bug report to pipewire team. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3230#note_1918090
Some background information: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3230 . This issue is mostly about being able to easily manage `module-combine-sink` from Plasma audio applet to output sound from one application to multiple sinks. I redirected the conversation here as pipewire-pulse has support for this module, thus it's only required to manage it from GUI.
A possible UX for this: Ctrl- or Shift-click (either in per-app menu or Devices panel) to add an output. If Ctrl+Shift are used together, remove the output from the combo. These targets can be managed using `slaves` property of the combine sink. Also, it'd be nice to set name according to targets, e.g. "WH-1000XM4 + Laptop Speakers". Please make sure to load combine-sink only when there're more than one output as well as removing it as soon as only one output is left. In case per-app menu will support that combine feature, exclude combine-sink nodes when Shift is held, we don't want them to be really deeply nested
> A possible UX for this: Ctrl- or Shift-click (either in per-app menu or Devices panel) to add an output. If Ctrl+Shift are used together, remove the output from the combo. That's a UX for power-users with keyboard and mouse. I mean, good luck exposing regular users to it, or using it on mobile/touch devices like Steam Deck.
This is almost certainly a duplicate of https://bugs.kde.org/show_bug.cgi?id=440536 and, I think, https://bugs.kde.org/show_bug.cgi?id=460857 essentially asks the same, too. I suggest closing this issue and adding any relevant information to #440536 instead.
Yep, good call. *** This bug has been marked as a duplicate of bug 440536 ***