Project

General

Profile

Feature #11312

Pressing the "set screen profile" button in Lighttable should provide informations about the current monitor profile

Added by Niccolò Belli over 3 years ago. Updated over 3 years ago.

Status:
Triaged
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
11/14/2016
Due date:
% Done:

20%

Estimated time:
Affected Version:
git master branch
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I'm currently having some issues with colord and I would like to know which profile Darktable gets for my monitor, especially if it gets it from xatom or colord. Clicking on the "set screen profile" should provide me some basic informations (like the profile name) about the automatically detected screen profile. Currently I can see the profile name only if I manually selected a profile, but not if it's set to "system profile". Hovering the mouse on "system profile" could reveal the profile name, or you could write it between parenthesis after "system profile". Either way it would be a very useful diagnostic information for everyone.

Associated revisions

Revision 0d64677a (diff)
Added by Tobias Ellinghaus about 3 years ago

cmstest: Fix broken logic for some cases

We used to query the wrong profiles for some multi monitor setups.
Thanks to Graeme Gill to help me figure out how to do this properly.
Not all possible cases are tested but it should be much better than
before.

Related to bug #11312 and might potentially be a fix for bug #10453.

History

#1 Updated by Christian Kanzian over 3 years ago

I do not know if this meets your needs, but you can start following binary in a console for more Info on monitor profiles:

darktable-cmstest

More about that can be found here:
https://www.darktable.org/usermanual/ch03s02s10.html.php

#2 Updated by Niccolò Belli over 3 years ago

I knew that one, but it doesn't really help me because it doesn't explicitely say which profile is darktable using:

$ darktable-cmstest
darktable-cmstest version 2.0.7
this executable was built with colord support enabled
darktable itself was built with colord support enabled

eDP1    the X atom and colord returned different profiles
        X atom: _ICC_PROFILE (1168 bytes)
                description: XPS 13 9343
        colord: "(none)" 
                description: (file not found)

DP1-1   the X atom and colord returned the same profile
        X atom: _ICC_PROFILE_1 (0 bytes)
                description: (none)
        colord: "(none)" 
                description: (file not found)

DP1-8   the X atom and colord returned the same profile
        X atom: _ICC_PROFILE_2 (0 bytes)
                description: (none)
        colord: "(none)" 
                description: (file not found)

Better check your system setup
 - some monitors reported different profiles
 - some monitors lacked a profile
You may experience inconsistent color rendition between color managed applications

#3 Updated by Tobias Ellinghaus over 3 years ago

  • Affected Version changed from 2.0.7 to git master branch
  • % Done changed from 0 to 20
  • Status changed from New to Triaged

I agree, it should be put somewhere in the GUI. For the time being you can start darktable from a terminal like this:

darktable -d control | grep "color profile"

#4 Updated by Niccolò Belli over 3 years ago

$ darktable-cmstest
darktable-cmstest version 2.2.0rc0+82~g0989d9b
this executable was built with colord support enabled
darktable itself was built with colord support enabled

eDP1    the X atom and colord returned different profiles
        X atom: _ICC_PROFILE (1168 bytes)
                description: XPS 13 9343
        colord: "(none)" 
                description: (file not found)

DP1-1   the X atom and colord returned the same profile
        X atom: _ICC_PROFILE_1 (0 bytes)                                                                                                                                                                                                                     
                description: (none)                                                                                                                                                                                                                          
        colord: "(none)"                                                                                                                                                                                                                                     
                description: (file not found)                                                                                                                                                                                                                

DP1-8   the X atom and colord returned the same profile                                                                                                                                                                                                      
        X atom: _ICC_PROFILE_2 (0 bytes)                                                                                                                                                                                                                     
                description: (none)                                                                                                                                                                                                                          
        colord: "(none)"                                                                                                                                                                                                                                     
                description: (file not found)                                                                                                                                                                                                                

Better check your system setup                                                                                                                                                                                                                               
 - some monitors reported different profiles                                                                                                                                                                                                                 
 - some monitors lacked a profile                                                                                                                                                                                                                            
You may experience inconsistent color rendition between color managed applications
$ darktable -d control | grep "color profile" 
[color profile] we got a new screen profile `XPS 13 9343' from the xatom _ICC_PROFILE (size: 1168)

As I suspected it gets the color profile from the laptop's monitor (which is even turned off) instead of the right external monitor (DP1-1). Also when I move the darktable window from one monitor to another it doesn't change the color profile. Should I open another bug report?

#5 Updated by Niccolò Belli over 3 years ago

My fault, my monitors profiles got deleted for some reasons. I reinstalled them and it seems to work flawlessly now.

#6 Updated by Niccolò Belli over 3 years ago

How lucky, I found not one but two bugs in both colord-kde and dispwin (X.org _ICC_PROFILE atom). I will get them fixed upstream but since they report two different profiles I still don't know which one darktable is using :)

[color profile] we got a new screen profile `U2515H #1 2016-09-25 18-25 D6500 2.2 M-S XYZLUT+MTX' from the xatom _ICC_PROFILE_1 (size: 728468)
[color profile] colord gave us a new screen profile: '/home/niko/.local/share/icc/U2515H #1 2016-09-25 18-25 D6500 2.2 M-S XYZLUT+MTX.icc' (size: 2815280)

It should definitely report something in the GUI about which profile is currently used.

#7 Updated by Tobias Ellinghaus over 3 years ago

What is the colord-kde bug? I was in contact with the author about supporting xatoms for multi screen setups in colord-kde a while ago and even though I had a (basically) working patch it was rejected. So I would be interested in a link to the bug report.

#9 Updated by Niccolò Belli over 3 years ago

Do you have any link to further discussions about your patch?
Graeme Gill (dispwin's creator) thinks that it may be colord messing things up.

#10 Updated by Tobias Ellinghaus over 3 years ago

Well, about colord-kde it was just that by default it doesn't set the xatom of the monitors other than the first one. Regarding the mails exchanged with Graeme I am not sure at all that darktable-cmstest is doing the right thing. I already asked him about that on the OpenICC list but got no reply so far.

Also available in: Atom PDF

Go to top