Closed Seizure closed 2 weeks ago
As far as we know/can tell, this is only an issue for input source. We've now simply masked the high byte when input source is being returned, within the MonitorBoss impl code. Should be sufficient. Closing for now.
Some monitors will send garbage high bytes/duplicate the low byte. Some monitors will do this randomly after having worked just fine forever!
ddcutil has a method of determining when to ignore the high byte. What is it? We should probably do something comparable. Will require modification of all OS-specific code