rockowitz

Also, when you hit the bug, what does **get-edid -b 10|parse-edid** show?

Yes, there have been changes in how the EDID is read, attempting to make it more efficient and robust. Apparently not. The problem can be seen at lines 676 and...

Commit 3808a0a is dated 11/2/2023. This recent commit is after the 2.0.0 release, so it can't be the cause of a bug that appeared in that release.

There is no central database of monitor feature definitions. Given the huge and expanding range of monitors, creating and maintaining one would be a hopeless task. The message "Feature definition...

@digitaltrails Just a quick note here to say that I may not have a quick solution. The underlying challenge is that there's no response packet that comes back when a...

@fionnb The issue of the benign but confusing messages was discussed on issue #348. As noted there the message indicates your monitor does not adhere to the DDC/CI spec when...

To disable the dynamic sleep algorithm, use option ***--disable-dynamic-sleep***. If that option is in effect, the sleep multiplier used is the value given on the ***--sleep-multiplier*** option, or 1.0 if...

@menkaur Does the problem persist with branch 2.0.2-dev? Does using option ***--disable-dynamic-sleep*** resolve the problem? Is it the case that the visible brightness of the monitor does not change, or...

I have a hunch as to how the dynamic sleep algorithm is causing **setvcp** failures and have hacked some code into branch 2.0.2-dev that should at least confirm the hunch....

@missonserch Your comment is unrelated to this issue. It has been moved to #396