https://bugs.kde.org/show_bug.cgi?id=454445
--- Comment #2 from John <ilikef...@waterisgone.com> --- (In reply to Zamundaaa from comment #1) > It would indeed be nice, sadly the driver doesn't currently expose that sort > of information to us. It's a known problem and will hopefully be tackled > soon™ with all the other color management stuff being worked on. However, I > fully expect it to still take a long while to be done. > Other than just waiting for that kernel fix, we could also > 1. roll our own automatic detection. Something basic should be pretty quick > to set up, although it may depend on us parsing more edid info (which I'd > like to avoid diving into until we can use libedid to take care of that for > us). Or > 2. remove the automatic option completely and always default to full rgb > range. Something like 98% of monitors and TVs out there have that and new > ones should all be full rgb range, so it likely wouldn't be that bad. > > Both have the problem that they can cause unexpected regressions for some > users with limited rgb TVs though... I would go with option number 2 as long as the users that have monitors and TVs that do not support the full range can still navigate to that control panel page and change it to limited. >From what I understand they should still be able to do that. As for the other option I understand and I would wait for the libedid too. If nothing could be done now, I completely understand. Thank you! -- You are receiving this mail because: You are watching all bug changes.
