| Summary: | Allow playing a stream on multiple arbitrary outputs | ||
|---|---|---|---|
| Product: | [Plasma] plasma-pa | Reporter: | Mircea Kitsune <sonichedgehog_hyperblast00> |
| Component: | general | Assignee: | David Rosca <nowrep> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | 89q1r14hd, fernandommuniz, kde, kde, kortrax11, major-mayer, me, nate, nicolas.fella, philippe.roubach, plasma-bugs, postix, rerupersonal1+kde, sonichedgehog_hyperblast00, yes456 |
| Priority: | HI | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=464916 https://bugs.kde.org/show_bug.cgi?id=480622 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Audio settings screenshot | ||
Yeah, fair enough! Has the team given any thought to this? I'm seeing it's still a limitation in 5.23.3. Any hope of seeing a solution for 5.24 perhaps? I found this open issue after a trip that I wanted to send audio to two bluetooth headsets. Would be very useful indeed. +1 vote There's a setting for creating a virtual output device that sends it to all outputs. Not very nice UX though. "This is something Pulseaudio allows but the KDE interface for it doesn't" got any documentation on that? Last time I checked pavucontrol only had the same virtual output device setting that we have, no individual control. Where is that setting? I cannot find anything to create a virtual output device. This is most likely a problem surrounding pipewire not having support implemented in kde for multi-output devices. KDE DEVS: please see this website. module-combine-sinks is what we are looking for here. It is marked as supported! https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Migrate-PulseAudio#module-combine-sink (In reply to kortrax11 from comment #7) Thanks for this information. That sounds like a big limitation in Pipewire itself. Until there's a solution for it, the interface could probably be adjusted to support this for PulseAudio without making it too weird for Pipewire users: PA remains the default over PW on most distributions as far as I'm aware, whereas I'm assuming the later will also get this limitation lifted before it's considered fully stable to use. (In reply to Mircea Kitsune from comment #8) > (In reply to kortrax11 from comment #7) > > Thanks for this information. That sounds like a big limitation in Pipewire > itself. Until there's a solution for it, the interface could probably be > adjusted to support this for PulseAudio without making it too weird for > Pipewire users: PA remains the default over PW on most distributions as far > as I'm aware, whereas I'm assuming the later will also get this limitation > lifted before it's considered fully stable to use. There is a solution for it. It is called module-combine-sink and its included in pipe wire! The website claims that it’s usage is exactly the same as pulseaudio’s *** Bug 457758 has been marked as a duplicate of this bug. *** PipeWire itself is natively able to route the same stream to multiple sinks, so if plasma-pa (or plasma-pw) gained the ability to talk PW API, it should already be able to do that without combine sink. The point of the combine sink is that the current PA API does not allow for this, so instead a new virtual device needs to be created that combines multiple other sinks and can then be chosen as the default sink in existing PA tools such as plasma-pa. *** Bug 457758 has been marked as a duplicate of this bug. *** Will Combine-Stream from pipewire will help implement above feature. . https://www.phoronix.com/news/PipeWire-0.3.65-Released *** Bug 460857 has been marked as a duplicate of this bug. *** *** Bug 470046 has been marked as a duplicate of this bug. *** *** Bug 470339 has been marked as a duplicate of this bug. *** Can we maybe get an update on this issue if it will ever be implemented? It seems like Pipewire is the way to go in the future and playing music to two Bluetooth headphones simultaneously is already doable either by CLI or by some advanced applications like Helvum (see also https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2636#note_1507319). But it would be of course much better to have a convenient UI in the Plasma settings somewhere that would allow doing something like this without being an expert. >> But it would be of course much better to have a convenient UI in the Plasma settings somewhere that would allow doing something like this without being an expert.
Yes helvum is for a techie person.
*** Bug 496210 has been marked as a duplicate of this bug. *** |
Created attachment 140476 [details] Audio settings screenshot SUMMARY This issue was brought up to me by someone close who is a streamer, to whom I suggested trying the KDE version of our Linux distribution of choice. They like the DE with the exception of a very frustrating issue: As a streamer they need to do advanced audio mixing, which involves having an application output to multiple audio devices. This is something Pulseaudio allows but the KDE interface for it doesn't. Currently they use Pulseaudio Volume Control to work around this limitation. The problem as can be seen in the attached screenshot is that every audio device is a radio button and not a checkbox: You must pick one active device but cannot select multiple. Pulseaudio itself lets you do this, it's just this interface that does not. Could the developers please consider a method to resolve this and allow picking multiple audio inputs / outputs? Thank you. STEPS TO REPRODUCE Simply go to System Settings - Hardware - Audio to see this. OBSERVED RESULT You can select just one active audio device applied to all applications. EXPECTED RESULT It would be very helpful if we were able to enable multiple output devices for sound to be piped through, ideally per-application if possible. At the moment Plasma users need tools like PAVUControl to do this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro OS KDE Plasma Version: Plasma 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION We're aware of the setting to create a unified audio output from all devices. They clarified that isn't a good solution: They don't want the audio to go to all local outputs automatically, only certain devices of choice.