Open rosshardy opened 7 months ago
I think this is due to a second query too soon after the first. Adding a time.sleep(1) is a workaround, but it would be nice if maybe the library could handle this or provide better insight.
There are rate limits defined in the DDC-CI specification, on Linux these are adjustable: https://github.com/newAM/monitorcontrol/blob/6674ac35d2221013f4208d21284914b1f46aae78/monitorcontrol/vcp/vcp_linux.py#L35-L37
Those values should be enough as-is, but sometimes monitors need a little bit more time. Sadly in Windows these values are fixed; Microsoft is in the right here, but it does make workarounds like this necessary for some monitors :(
monitorcontrol --version
): 3.1.0Steps to Reproduce
The following python code errors:
Output: