AOC Q27P1B input source values about ddcutil HOT 3 OPEN

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 file not found: AOC-Q27P1B-9985.mccs" indicates that you have not created a local feature definition file for the monitor. See User Defined Features.

I suggest that you add your findings to the wiki page Notes on Specific Monitors or perhaps add a new page for AOC displays. This is also an appropriate location for people to report feature definition (mccs) file they have created.

from ddcutil.

I've made this situation worse by making ddcutil-service treat SNC features strictly - after the fix for digitaltrails/vdu_controls#84, I discard the high byte.

Sanford: do you have anything to add on whether it's a good idea to generally discard the high-byte of SNC features? Discarding the high-byte fixes the SNC case where the high byte contrans a "junk" value (as in the ddcutil-service issue), but it seems that this is an example where the high-byte contains useful info.

My current proposal for ddcutil-service and vdu_controls is to allow a special qualifier in the vdu_controls metadata that would result in a flag being passed to ddcutil-service so that it returns both bytes of a particular SNC feature.

from ddcutil.

Could this feature be handled by a ddcutil user defined feature, would it be CNC?

MFG_ID       AOC
MODEL        AOC Q27P1B
PRODUCT_CODE 12345
MCCS_VERSION 2.2
FEATURE_CODE 60  Input selection
    ATTRS NC RW
    VALUE 01 VGA
	VALUE 02 VGA (switch to)
	VALUE 03 DVI (switch to)
	VALUE 04 DVI (switch to)
	VALUE 0f DisplayPort (switch to)
	VALUE 11 HDMI (switch to)
	VALUE 300 DVI/HDMI (read-only)
	VALUE 301 DVI/HDMI (read-only)
	VALUE 302 DVI/HDMI (read-only)
	VALUE 305 DisplayPort (read-only)

from ddcutil.