-
Notifications
You must be signed in to change notification settings - Fork 16
Sleepy Pipewire #35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can't reproduce this one, but your log might have enough information to work from. Can you send a .qslog file with the problem reproduced? |
The log shows the node is bound and should be receiving volume changes. Does that set-volume actually do anything for you? |
Yes. |
Was able to reproduce with source |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Quickshell's pipewire service gives current volume only after linking any node to the default sink node.
My quickshell version:
quickshell pre-release, revision 67524f9d8e4ac5e09ea4427e11f2284e6a6f93fe, distributed by: Official-Nix-Flake
. I use quickshell config from this repo: https://github.com/SirEthanator/Quickshell-WIP. Here is the snippet:I start quickshell from niri's config spawn at startup. Then using commands like
wpctl set-volume @DEFAULT_AUDIO_SINK@ 0.1
producing no updates on pipewire default Audio node status.But when I connect something to default sink ports (launching pavucontrol, playing video using mpv, manually in helvum), setting volume gives expexted PwNode updates in quickshell.
Now at startup I run pw-loopback and kill it immediately, but I think that is just workaround for above unexpected behaviour.
If there any trace methods to find the root problem?
The text was updated successfully, but these errors were encountered: