Visual Display Unit virtual control panel
https://github.com/digitaltrails/vdu_controls
vdu_controls is a virtual control panel for externally connected VDUs (visual display units). Controls are included for backlight brightness, and contrast. vdu_controls uses the ddcutil command line utility to interact with external displays via VESA Display Data Channel (DDC) Virtual Control Panel (VCP) standards.
- Sources inherited from project utilities
- Devel package for openSUSE:Factory
- Links to openSUSE:Factory / vdu_controls
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:redwil:15.4/vdu_controls && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000124 124 Bytes | |
vdu_controls-2.0.2.tar.gz | 0003238151 3.09 MB | |
vdu_controls.changes | 0000015058 14.7 KB | |
vdu_controls.spec | 0000004837 4.72 KB |
Revision 28 (latest revision is 31)
Michael Hamilton (mchnz)
accepted
request 1167503
from
Michael Hamilton (mchnz)
(revision 28)
- Version 2.0.2 * Added a *refresh* annotation suffix for use with VCP-codes which cause multiple changes. * Make manual adjustment of the ambient Light Level more accurate and responsive. * Updates are sent to the VDU as sliders are dragged (rather than only on release). * Fix exception on monitors that return invalid/unexpected combo-box VCP values. * Fix exception on monitors with blank VCP value descriptions. * When refresh is pressed, only auto adjust ambient brightness if auto-brightness is enabled. * Don't automatically refresh on error, eliminate popup dialog loops. * Eliminate deadlocks when exceptions occur. * Cleanup the initialisation of the ddcutil-service connection. * Add more caveats and limitations to the documentation. * Fix manual ambient light slider when light meter is uninitialized. * Promote Simple-Non-Continuous values whose metadata exceeds one-byte to two-byte Complex-NC.
Comments 5
Is this the officially maintained package? https://github.com/digitaltrails/vdu_controls?tab=readme-ov-file#installing links to https://software.opensuse.org/package/vdu_controls but it's not available in Factory according to https://software.opensuse.org/package/vdu_controls (despite https://software.opensuse.org//download.html?project=utilities&package=vdu_controls mentioning it).
No, it's only an experimental package - which basically means it's been accepted as experimental, I had to apply for that. But builds is not curated/vetted by anyone official, they just have to pass through the automated build process.
I need to submit it to factory if it's going to be official, then there's some kind of lengthy approval/legal process that kicks in.
There is now an official package in factory: https://build.opensuse.org/package/show/openSUSE:Factory/vdu_controls
The factory package is available as a Tumbleweed official package: https://software.opensuse.org/package/vdu_controls
@mchnz great news :)
Thanks for all the help with this. I'm now wondering whether I should also submit ddcutil-service, my D-Bus front end to libddcutil - https://build.opensuse.org/package/show/home:mchnz/ddcutil-service
When the new/pending vdu_controls 2.0 is configured to use ddcutil-service, DDC access is up to 10 times faster, the UI feels much snappier. (https://build.opensuse.org/package/show/home:mchnz/vdu_controls).
It's possible Sanford Rockowitz, the author of ddcutil, will pick up and distribute the service, but it may take some time to sort out the details.