Skip to content
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

Experimental option --skip-ddc-checks #345

Closed
rockowitz opened this issue Oct 23, 2023 · 1 comment
Closed

Experimental option --skip-ddc-checks #345

rockowitz opened this issue Oct 23, 2023 · 1 comment

Comments

@rockowitz
Copy link
Owner

Branch 2.0.2-dev has an experimental option, -skip-ddc-checks. It is valid only if the display is selected by its bus number (option --bus) and only for commands getvcp and setvcp. Because it is experimental, it is listed only by option --hh, not --help.

If specified, ddcutil initialization does not check if DDC communication is working, and does not check that the monitor reports unsupported features as per the DDC/CI spec, For any "reasonable" monitor, these checks should never fail. The downside is that either of these things is not true, it's unclear how the getvcp or setvcp command will fail.

For ddcutil invocations getting and setting a single feature, this significantly reduces the number of DDC operations. In a GUI invoking ddcutil repeatedly there's no point to making these checks on every call, and the option may make widgets such as sliders perceptively faster.

As this feature is experimental, comments positive as well as negative are valuable. The option will be kept only if it actually proves useful.

@rockowitz
Copy link
Owner Author

This option was made non-experimental as of release 2.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant