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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: