You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to request a feature for SwayOSD that allows it to operate in a UI-only mode, without relying on backend control. This would be particularly useful for scenarios where brightness or audio control is managed through external tools or scripts.
Use Case:
I use ddcutil to control my monitor's brightness, as it does not appear under brightnessctl. In such cases, I want to:
Execute a script to adjust the brightness.
Use SwayOSD to display the UI with a specified brightness level, without direct integration with the backend.
This functionality could also extend to other controls, such as audio volume or mute/unmute states.
Proposed Solution:
Introduce a UI-only mode where SwayOSD:
Accepts external inputs (e.g., brightness level or volume) via command-line arguments or an API.
Displays the corresponding UI without attempting to interact with the backend.
I don't know if you're still interested in this but I had this same problem and ended up making my own OSD. I tried approaching this one, but it just felt way too tightly coupled to specific backends or implementations like pactl. (it's WIP but it works for me, so) https://github.com/ansxor/wayland-osd
You run the server and then use the client like the following to change brightness:
wayland-osd-client brightness 50
I also include a Wireplumber monitoring program for output audio devices that uses the same CLI if you use that.
I don't know if you're still interested in this but I had this same problem and ended up making my own OSD. I tried approaching this one, but it just felt way too tightly coupled to specific backends or implementations like pactl. (it's WIP but it works for me, so) https://github.com/ansxor/wayland-osd You run the server and then use the client like the following to change brightness:
wayland-osd-client brightness 50
I also include a Wireplumber monitoring program for output audio devices that uses the same CLI if you use that.
I would like to request a feature for SwayOSD that allows it to operate in a UI-only mode, without relying on backend control. This would be particularly useful for scenarios where brightness or audio control is managed through external tools or scripts.
Use Case:
I use ddcutil to control my monitor's brightness, as it does not appear under brightnessctl. In such cases, I want to:
This functionality could also extend to other controls, such as audio volume or mute/unmute states.
Proposed Solution:
Introduce a UI-only mode where SwayOSD:
Example:
Benefits:
Thank you for considering this enhancement!
The text was updated successfully, but these errors were encountered: