https://bugs.kde.org/show_bug.cgi?id=525112
Bug ID: 525112
Summary: Allow overriding the system monitor profile (and
per-screen profiles) for built in hardware calibrated
monitors
Classification: Applications
Product: digikam
Version First 9.1.0
Reported In:
Platform: Other
URL: https://www.asus.com/displays-desktops/monitors/proart
/proart-display-pa27ucge/
OS: macOS
Status: REPORTED
Keywords: multiscreen
Severity: normal
Priority: NOR
Component: ColorManagement-Profiles
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Summary:
On macOS the Color Management → Profiles → Monitor profile control is locked to
“Monitor Profile From System Settings”. That may be correct as a default but on
a hardware managed display set to Adobe RGB, this defaults to sRGB which is
wrong. The net result is I cannot have a colour managed workflow with Digikam
on Mac without an override feature and neither will anyone else with a hardware
calibrated display like mine. The key difference here is that I don't create a
profile with e.g. a colormunki and put that profile into the colour profiles
section against the display - there is no colour profile and as such I must set
it to none (mine just lists the monitor model and that is set to none instead).
Why System Settings is not enough:
Hardware-calibrated ASUS ProArt (PA27UCGE) with ProArt Calibration. Calibration
patches are affected by the live macOS display path (e.g. Night Shift on the
same screen produced a bad LUT; it had to be off and run again). ColorSync must
therefore remain the device profile (PA27UCGE), which has no colour management
- not a working space such as Adobe RGB (1998).
digiKam then inherits that device profile, or sRGB if the EDID profile has been
dropped. I cannot tell digiKam “convert photos to Adobe RGB” without changing
ColorSync, which would invalidate the hardware calibration loop.
On Linux this is not a problem because the same app lets me choose the monitor
ICC independently of the compositor. Dual-boot / shared library makes the
mismatch obvious.
Also: two PA27UCGE screens. The info button shows digiKam has picked one system
profile for the whole app (wrong screen has happened here and on 509534). There
is no per-output override.
Requested behaviour:
1. Keep “use system profile” as the default (current greyed-out behaviour).
2. Add “Override” and a profile picker, as on Linux.
3. Prefer per-screen overrides (or at least follow the screen the window is
on).
4. On macOS, if an override is set, tag the window/backing store with that
colour space so ColorSync does not convert again.
Related: 509534 (system profile lock / wrong screen). That is not a duplicate
of the override request.
--
You are receiving this mail because:
You are watching all bug changes.
