DDC input source value exceed maximum range stated #3797
Replies: 1 comment 4 replies
-
|
I don't think so, the display probably has a faulty firmware. Btw - does 18 work from Windows? Did you try getting capabilities using auto-detect from the DDC Features... menu or the CLI? |
Beta Was this translation helpful? Give feedback.
-
Nope 18 does not work from Windows either. Yes I have used auto detect from both DDC Features and CLI too. So it is most likely a firmware issue? 
|
Beta Was this translation helpful? Give feedback.
-
|
Yes. It is strange that the report does not work on macOS while works on Windows but the difference may be related to the different GPU implementation or maybe more retry times. |
Beta Was this translation helpful? Give feedback.
-
Is there a way to increase the retry limit on betterdisplay to get the ddc report? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you can generally try increasing communication timings and retry limits. You can also start the app from Terminal and add |
Beta Was this translation helpful? Give feedback.
-
I am running an innocn 27 4k monitor which has 2xDP, 1xHdmi and 1xUsb-c. After some testing, I have found that the following input values correspond in the following manner. USB-C:15, DP1:16, HDMI:17 and DP2 was not possible to be triggered at all. I tried using better display get DDC capabilities but got an error. So I turned to windows machine and used clickmonitorDDC to get a vcp report with DP2 plugged in. This was what I got below. The maximum range for input source is 18 but it shows present value as 50. I tried using the value of 50 to trigger in better display but it did not work. Is there a solution or workaround for this
Beta Was this translation helpful? Give feedback.
All reactions