Feature-Request: pipewire module #933
Comments
|
Or maybe if anyone has gotten anything to work they could post here? Even with pipewire-pulse installed, the pulse module doesn't work, which surprised me. |
I find out it is working if you restart waybar |
|
For me, waybar-pulseaudio works fine with |
|
If pipewire-pulse isn't exposing the bluetooth info in the same way as native PulseAudio, I think that's PipeWire's bug (or missing feature). That said, a native PipeWire module is probably still a good idea to get access to things like latency data that could be useful in a status bar, but wouldn't be available in the PulseAudio compatibility layer. |
Hmm... not sure what's different with my setup. For me, the module has been empty since I switched to pipewire-pulse. https://github.com/pkulak/dotfiles/blob/master/.config/waybar/config |
|
Make sure your PipeWire version is up to date I guess? PipeWire is under heavy development, and regularly gets new features and fixes. Latest is 0.3.20, and the only issue I'm seeing is Waybar isn't showing Bluetooth info. |
|
I had to rebuild Waybar-git after installing pipewire-pulseaudio on FC33, but works fine for volume display and control after doing so. |
|
Anyway we have |
works fine for me |
Doesn't work for me. Always shows 100% volume whatever the real volume is and does not adjust the volume on scroll. |
Yes, since 0.3.21 (or even 0.3.20) waybar works without restarting it. Keep this open if you want to support it natively, otherwise you can close it. Thanks! |
0.3.23, doesn't work (and never did) |
|
I'm on pw 0.3.23 too, works fine for me (and has for weeks). |
|
On waybar 0.9.7 pulseaudio module works normally with pipewire. |
|
On pipewire 0.3.28 and waybar 0.9.7, Waybar wouldn't launch otherwise |
|
I found out that pulseaudio module doesn't like the pipewire-pulse daemon restart and stops working after that. |
default source/sink probably got fucked check to make sure personally for me, the headphones icon sometimes shows and sometimes doesn't, especially when selecting different codecs. Usually always shows up with aptX [HD] codec, but only sometimes shows with SBC and AAC codecs (selected in pavucontrol). A native pipewire module would be quite nice and would at least be a step in not being forced to use a Pulse server |
This problem only appeared when restarting pipewire-pulse. And since pipewire became stable enough I don't need to restart it from time to time, this is not a problem.
For me it never showed. Even when I used pulseaudio. |
For me, reloading Sway (which also relaunches Waybar) fixed it. When restarting pipewire, it did freeze like that, but unfroze after a reload |
Of course it did. Why wouldn't it? I start waybar as systemd user unit, so for me restarting waybar is a matter of |
|
Why close this issue? Is it fixed? I don't see anything like that in waybar code. |
|
|
|
@Alexays Why close this issue? Is it fixed? |
|
@mizzunet better to use |
|
I commented here to point out my desire for a native pipewire module (i.e. not using pipewire-pulse) |
|
This issue probably shouldn't have been closed. This hasn't been fixed, I use waybar with a different wm than sway, and there's no easy way to simply reload it, and I don't feel like hacky workarounds are the right solution. The volume indicator often freezes when I enable EasyEffects, for example, killing and relaunching waybar seems to be the only temporary fix I've found so far. |
|
I use PipeWire, but don't use WirePlumber, so this is useless for me. |
Ngl I actually laughed when I saw all those thumbs down. I don't know if you are joking or not so I'll just tell you that wireplumber is a tool to manage pipewire my dude. So, yes, wireplumber is in fact not useless for you. |
|
No, wireplumber is uselesss for me. I use pipewire-media-session to manage my pipewire daemon. |
Pipewire-media-session is succeeded by wireplumber. Media session is the example implementation. I would very highly recommend moving to it (it's 2 lines in your config) |
|
I won't install wireplumber because it requires lua-5.4. If it lowered it's requirements to lua 5.1, I'd consider it, but that's unlikely. Or if LuaJIT supported Lua 5.4, which is even less likely. So, I'll stick with media-session until I'm forced to move. |
This reasoning makes zero sense. 5.3 is supported by WirePlumber. Lua 5.3 is halfway to being a legal adult. You've had 9 years to switch... and something tells me @Alexays isn't gonna bend to the will of one random kid who cares so deeply about getting a 1% performance boost on an 18 year old version of a programming language. (sidenote: newer versions of Lua are faster than 5.1 with LuaJIT) |
|
I'm not talking about performance here. I just don't want to have anything to do with Lua versions higher than 5.2. The reasoning was stated multiple times by Mike Pall (the developer of LuaJIT). Here for example. In short - the design is awful. I'm appaled that WirePlumber developers decided to support only Lua 5.3+ while most opensource projects still support 5.1. That's why I don't want to install it. |
|
The Lua design being "awful" has nothing to do with WirePlumber. You sacrifice nothing by installing a 9-year-old version of Lua. I'm not entirely sure why this is the hill you choose to die on, especially considering I highly doubt @Alexays or any other maintainers want to support a media session that has explicitly been stated to be experimental and not for general use. |
|
No need to support media-session. I only ask to support pipewire. |
That's a very dangerous notion, no matter what follows this. |
As far as I remember it needs a media session for this. Pipewire relies on the media server architecture.
I disagree. A programming language you never use that takes up a couple megabytes doesn't cost you anything unless you're absolutely fighting for every byte of space. |
Pipewire itself needs it, yes. The software that talks to pipewire via it's native protocol - doesn't. Wireplumber module circumvents the use of pipewire native protocol by talking to the wireplumber itself through DBus.
Okay.
Who said anything about cost? |
May you please add PipeWire support?
The text was updated successfully, but these errors were encountered: