-
Notifications
You must be signed in to change notification settings - Fork 38
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
AOC Q27P1B input source values #385
Comments
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. |
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. |
Could this feature be handled by a ddcutil user defined feature, would it be CNC?
|
I'm giving some feedback regarding the AOC Q27P1B monitor. It has four video inputs:
Unfortunately, its implementation of the VCP 0x60 is… well… unique. And it probably behaves similarly to other AOC displays.
It claims to support:
Full output of capabilities
But obviously it supports more values for VCP 0x60.
I also know this monitor is not yet added to any DDC database, because I get the Feature definition file not found: AOC-Q27P1B-9985.mccs message.
Limitations from my tests
I don't have any Windows system nor any way to sniff the I2C packets from a Windows system, so I cannot reverse-engineer it.
I don't have enough machines to feed both HDMI and DVI simultaneously to the display.
Given this is based on trial-and-error, there may be a few mistakes.
My findings
Here are my findings, based on trial-and-error:
x01
: VGAx02
: VGA (switch to)x01
a few seconds later.x03
: DVI (switch to)x04
: DVI (switch to)x0f
: DisplayPort (switch to)x10
: Doesn't workx11
: HDMI (switch to)x12
: Doesn't workx300
: DVI/HDMI (read-only)x301
: DVI/HDMI (read-only)0x301
, other times0x302
. I don't know the difference. Maybe it's related to the amount of connected devices.x302
: DVI/HDMI (read-only)0x301
, other times0x302
. I don't know the difference. Maybe it's related to the amount of connected devices.x305
: DisplayPort (read-only)To help me quickly test, I'm using this one-liner:
while read v ; do [ -n "$v" ] && ddcutil -v -d 1 setvcp 60 "$v" ; ddcutil -v -d 1 getvcp 60 ; done
Here's the full output log:
Full console output
System
Action points
Can this kind of info be added to some database somewhere?
Do you need any additional information?
See also
The text was updated successfully, but these errors were encountered: