[LAU] Re: pipewire, wtf, part 2
Bengt Gördén <[email protected]>
| Newsgroups | gmane.linux.audio.users |
|---|---|
| Message-ID | <[email protected]> |
On 2026-01-01 13:19, Michael Jarosch wrote: > I guess I have to point out something… > > I'm not against pipewire. The main reason why I thought I should report > this on this list is that I wanna find out more about it before creating > a bugreport… > > Therefore I'm asking (for both of my issues): > > Does other people experience the same? > Is this a kind of misconfiguration (on linux-distribution level)? > Is this really pipewire's/wireplumber's fault? > Is this a bug? > > It's not about complaining, it's about making things better. I found 2 > issues which I think are not the way pro-audio-people want them to work. > So, if we don't raise our voice, it's no wonder our wishes are not being > heard… > > Please, help! :) Hi Mitsch, Can you share your configuration with pw-play as backend so I can try to replicate your problem? I have only used linux-show-player with Gstreamer. With Gstreamer there is no problem running audacious and linux-show-player at the same time and independent volumes. I am currently running the flatpak version of inux-show-player as the version in the opensuse repo crashes for some reason (probably wrong python version). PS. I had linux-show-player as a backup for a musical in 2023. Much more reliable than Qlab for macOS although, due to the license, I had to use Qlab as the first choice. -- /bengan _______________________________________________ Linux-audio-user mailing list -- [email protected] To unsubscribe send an email to [email protected]