suddenly cannot choose a monitor profile in settings

Hi,

I've compiled from svn the newest source code (Version 1.1.0 (rev.: 1064834)).
While checking things I discovered that I cannot choose a monitor profile in the
settings anymore. It just says "Monitor Profile from System Settings" and the
pull down trigger does nothing.

With older versions (like beta5 oder beta6) this was working and I could select
my calibrated monitor profile.

Has this behaviour changed now?
Where can I check/change the system settings to be sure that digiKam uses my
profile?

TIA
Guenther


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Greenwood-2]

On Tuesday 22 Dec 2009 00:37:52 Guenther Erhard wrote:
> Hi,
>
> I've compiled from svn the newest source code (Version 1.1.0 (rev.: 1064834)).
> While checking things I discovered that I cannot choose a monitor profile in the
> settings anymore. It just says "Monitor Profile from System Settings" and the
> pull down trigger does nothing.
>
> With older versions (like beta5 oder beta6) this was working and I could select
> my calibrated monitor profile.

Mine is doing exactly the same thing, I'm running the 1.0rc version. What is strange is that on one machine it does it all the time but on another machine, disabling and then re-enabling colour management allows me to select my monitor profile. Both machines are running the same distro and the same versions of everything.

>
> Has this behaviour changed now?
> Where can I check/change the system settings to be sure that digiKam uses my
> profile?

I cannot find anywhere in system settings that allows me to select a profile. Nor can I find any reference to it in Google or by searching the KDE site.

I'm using KDE 4.3.4. I too would like the answer to this question.

Mark

>
> TIA
> Guenther
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:

> On Tuesday 22 Dec 2009 00:37:52 Guenther Erhard wrote:
> > Hi,
> >
> > I've compiled from svn the newest source code (Version 1.1.0
> > (rev.: 1064834)). While checking things I discovered that I
> > cannot choose a monitor profile in the settings anymore. It just
> > says "Monitor Profile from System Settings" and the pull down
> > trigger does nothing.
> >
> > With older versions (like beta5 oder beta6) this was working and
> > I could select my calibrated monitor profile.
>
> Mine is doing exactly the same thing, I'm running the 1.0rc
>  version. What is strange is that on one machine it does it all the
>  time but on another machine, disabling and then re-enabling colour
>  management allows me to select my monitor profile. Both machines
>  are running the same distro and the same versions of everything.
>
> > Has this behaviour changed now?
> > Where can I check/change the system settings to be sure that
> > digiKam uses my profile?
>
> I cannot find anywhere in system settings that allows me to select
>  a profile. Nor can I find any reference to it in Google or by
>  searching the KDE site.

So may be it has something to do with this:
http://www.argyllcms.com/doc/dispwin.html#I

It seems to go the same way as gimp and ufraw do it already. A dialog
to query currently set display profile would be fine anyway.

>
> I'm using KDE 4.3.4. I too would like the answer to this question.
>
> Mark
>
> > TIA
> > Guenther
> >
> >

Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

> > I cannot find anywhere in system settings that allows me to select
> >  a profile. Nor can I find any reference to it in Google or by
> >  searching the KDE site.
>
> So may be it has something to do with this:
> http://www.argyllcms.com/doc/dispwin.html#I
>
> It seems to go the same way as gimp and ufraw do it already. A dialog
> to query currently set display profile would be fine anyway.
>

Yes, that is possible, but "set | grep ICC" does not show any set
environment variable.

In my case I don't use dispwin - I use xcalib to load the calibration
profile at every startup of X11.

I second that: The possibility to choose a profile should still be
there. GIMP allows that too.

Guenther


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Guenther Erhard:

> > > I cannot find anywhere in system settings that allows me to
> > > select a profile. Nor can I find any reference to it in Google
> > > or by searching the KDE site.
> >
> > So may be it has something to do with this:
> > http://www.argyllcms.com/doc/dispwin.html#I
> >
> > It seems to go the same way as gimp and ufraw do it already. A
> > dialog to query currently set display profile would be fine
> > anyway.
>
> Yes, that is possible, but "set | grep ICC" does not show any set
> environment variable.

The data is not stored in environment variables but as property in
X11. For the dispwin tool the configuration is set in
~/.config/color.jcnf. My data is set as:

  "devices": {
    "display": {
      "1": {
        "EDID":
"0x00FFFFFFFFFFFF0015C37916010101010C0E0102681E1778EAA415A5544897250F5054BFEE000101010101010101010101010101010164190040410026301888360030E410000018000000FF004B353134333033340A20202020000000FD00374C183D08000A202020202020000000FC004C3336370A20202020202020200022",
        "ICC_PROFILE":
"/home/blablub/.local/share/color/icc/devices/display/eizo.icc"
      },
      "2": {
        "NAME": ":0.0",
        "ICC_PROFILE":
"/home/blablub/.local/share/color/icc/devices/display/dell-L.icc"
      }
    }
  }

If I load color profile (dispwin -L) the one for my current display is
loaded (here dell-L.icc) the eizo.icc I used with my old monitor.

>
> In my case I don't use dispwin - I use xcalib to load the
>  calibration profile at every startup of X11.

I don't know xcalib, but it must do something similar.

>
> I second that: The possibility to choose a profile should still be
> there. GIMP allows that too.
>
> Guenther
>
>

Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Greenwood-2]

On Tuesday 22 Dec 2009 09:16:41 Martin (KDE) wrote:

> Am Dienstag, 22. Dezember 2009 schrieb Guenther Erhard:
> > > > I cannot find anywhere in system settings that allows me to
> > > > select a profile. Nor can I find any reference to it in Google
> > > > or by searching the KDE site.
> > >
> > > So may be it has something to do with this:
> > > http://www.argyllcms.com/doc/dispwin.html#I
> > >
> > > It seems to go the same way as gimp and ufraw do it already. A
> > > dialog to query currently set display profile would be fine
> > > anyway.
> >
> > Yes, that is possible, but "set | grep ICC" does not show any set
> > environment variable.
>
> The data is not stored in environment variables but as property in
> X11. For the dispwin tool the configuration is set in
> ~/.config/color.jcnf. My data is set as:
>
>   "devices": {
>     "display": {
>       "1": {
>         "EDID":
> "0x00FFFFFFFFFFFF0015C37916010101010C0E0102681E1778EAA415A5544897250F5054BFEE000101010101010101010101010101010164190040410026301888360030E410000018000000FF004B353134333033340A20202020000000FD00374C183D08000A202020202020000000FC004C3336370A20202020202020200022",
>         "ICC_PROFILE":
> "/home/blablub/.local/share/color/icc/devices/display/eizo.icc"
>       },
>       "2": {
>         "NAME": ":0.0",
>         "ICC_PROFILE":
> "/home/blablub/.local/share/color/icc/devices/display/dell-L.icc"
>       }
>     }
>   }
>
> If I load color profile (dispwin -L) the one for my current display is
> loaded (here dell-L.icc) the eizo.icc I used with my old monitor.
>
> >
> > In my case I don't use dispwin - I use xcalib to load the
> >  calibration profile at every startup of X11.
>
> I don't know xcalib, but it must do something similar.

Now I'm even more confused. I have never heard of xcalib or dispwin.

I have a monitor profile for my monitor and I want Digikam to use it. What is all this config files and load at startup of X11 nonsense?

Mark

>
> >
> > I second that: The possibility to choose a profile should still be
> > there. GIMP allows that too.
> >
> > Guenther
> >
> >
>
> Martin
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:

> On Tuesday 22 Dec 2009 09:16:41 Martin (KDE) wrote:
> > Am Dienstag, 22. Dezember 2009 schrieb Guenther Erhard:
> > > > > I cannot find anywhere in system settings that allows me to
> > > > > select a profile. Nor can I find any reference to it in
> > > > > Google or by searching the KDE site.
> > > >
> > > > So may be it has something to do with this:
> > > > http://www.argyllcms.com/doc/dispwin.html#I
> > > >
> > > > It seems to go the same way as gimp and ufraw do it already.
> > > > A dialog to query currently set display profile would be fine
> > > > anyway.
> > >
> > > Yes, that is possible, but "set | grep ICC" does not show any
> > > set environment variable.
> >
> > The data is not stored in environment variables but as property
> > in X11. For the dispwin tool the configuration is set in
> > ~/.config/color.jcnf. My data is set as:
> >
> >   "devices": {
> >     "display": {
> >       "1": {
> >         "EDID":
> > "0x00FFFFFFFFFFFF0015C37916010101010C0E0102681E1778EAA415A5544897
> >250F5054BFEE000101010101010101010101010101010164190040410026301888
> >360030E410000018000000FF004B353134333033340A20202020000000FD00374C
> >183D08000A202020202020000000FC004C3336370A20202020202020200022",
> > "ICC_PROFILE":
> > "/home/blablub/.local/share/color/icc/devices/display/eizo.icc"
> >       },
> >       "2": {
> >         "NAME": ":0.0",
> >         "ICC_PROFILE":
> > "/home/blablub/.local/share/color/icc/devices/display/dell-L.icc"
> >       }
> >     }
> >   }
> >
> > If I load color profile (dispwin -L) the one for my current
> > display is loaded (here dell-L.icc) the eizo.icc I used with my
> > old monitor.
> >
> > > In my case I don't use dispwin - I use xcalib to load the
> > >  calibration profile at every startup of X11.
> >
> > I don't know xcalib, but it must do something similar.
>
> Now I'm even more confused. I have never heard of xcalib or
>  dispwin.
>
> I have a monitor profile for my monitor and I want Digikam to use
>  it. What is all this config files and load at startup of X11
>  nonsense?

Sorry Mark, this is no nonsens. for a colour managed environment you
have to calibrate and profile your monitor. Usually this results in a
icc or icm file.

The calibration stuff is loaded usually at login time. This sets your
Gamma curve (and colour temperature) to what you have set up your icc
profile to (I have a L-Star gamma and a colour temperature of about
6500K - my native display colour).

The profile stuff is done by the application (digiKam, Gimp or UFRaw).
So you have to either set it manually in every application or you can
use the system wide profile (which is the one you loaded at login).
This makes sure that red in sRBG is displayed ecactly as the same red
as in AdobeRGB or eciRGB (as long as they are in the available range -
called Gamut).

So If you want to use your Monitor profile reset all your monitor
settings to default. Install argyllcms (or xcalib) and load the icc
file at login (first time: dispwin -I /path/to/display.icc; next:
dispwin -L). Next you have to load the file as display profile in your
application.

Be aware: colour management does not improve the colour itself.

Next important step is to choose a working profile. Here you are free
to choose every profile you want, but without a hardware calibrated
monitor best use may be sRGB. AdobeRGB does not bring you more colour
if your Monitor is not able to show it (which most monitors can not).
Even worse: If you use 8-bit encoded RGB you loose some fine
granularity in the less saturated part of the image.

Conclusio: If you want to use 8-Bit RGB use sRGB (you avoid problems
if you print images or give them to others). If you want higher colour
range use L*-RGB and 16-Bit. But then you have to buy a hardware
colorimeter and a monitor which can display this colours reliably.
This will you cost you at least 1000 Euro for the monitor and 250 Euro
for the colorimeter.

Martin

>
> Mark
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Greenwood-2]

On Tuesday 22 Dec 2009 13:53:49 Martin (KDE) wrote:

> Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:
> > On Tuesday 22 Dec 2009 09:16:41 Martin (KDE) wrote:
> > > Am Dienstag, 22. Dezember 2009 schrieb Guenther Erhard:
> > > > > > I cannot find anywhere in system settings that allows me to
> > > > > > select a profile. Nor can I find any reference to it in
> > > > > > Google or by searching the KDE site.
> > > > >
> > > > > So may be it has something to do with this:
> > > > > http://www.argyllcms.com/doc/dispwin.html#I
> > > > >
> > > > > It seems to go the same way as gimp and ufraw do it already.
> > > > > A dialog to query currently set display profile would be fine
> > > > > anyway.
> > > >
> > > > Yes, that is possible, but "set | grep ICC" does not show any
> > > > set environment variable.
> > >
> > > The data is not stored in environment variables but as property
> > > in X11. For the dispwin tool the configuration is set in
> > > ~/.config/color.jcnf. My data is set as:
> > >
> > >   "devices": {
> > >     "display": {
> > >       "1": {
> > >         "EDID":
> > > "0x00FFFFFFFFFFFF0015C37916010101010C0E0102681E1778EAA415A5544897
> > >250F5054BFEE000101010101010101010101010101010164190040410026301888
> > >360030E410000018000000FF004B353134333033340A20202020000000FD00374C
> > >183D08000A202020202020000000FC004C3336370A20202020202020200022",
> > > "ICC_PROFILE":
> > > "/home/blablub/.local/share/color/icc/devices/display/eizo.icc"
> > >       },
> > >       "2": {
> > >         "NAME": ":0.0",
> > >         "ICC_PROFILE":
> > > "/home/blablub/.local/share/color/icc/devices/display/dell-L.icc"
> > >       }
> > >     }
> > >   }
> > >
> > > If I load color profile (dispwin -L) the one for my current
> > > display is loaded (here dell-L.icc) the eizo.icc I used with my
> > > old monitor.
> > >
> > > > In my case I don't use dispwin - I use xcalib to load the
> > > >  calibration profile at every startup of X11.
> > >
> > > I don't know xcalib, but it must do something similar.
> >
> > Now I'm even more confused. I have never heard of xcalib or
> >  dispwin.
> >
> > I have a monitor profile for my monitor and I want Digikam to use
> >  it. What is all this config files and load at startup of X11
> >  nonsense?
>
> Sorry Mark, this is no nonsens. for a colour managed environment you
> have to calibrate and profile your monitor. Usually this results in a
> icc or icm file.
>
> The calibration stuff is loaded usually at login time. This sets your
> Gamma curve (and colour temperature) to what you have set up your icc
> profile to (I have a L-Star gamma and a colour temperature of about
> 6500K - my native display colour).
>
> The profile stuff is done by the application (digiKam, Gimp or UFRaw).
> So you have to either set it manually in every application or you can
> use the system wide profile (which is the one you loaded at login).
> This makes sure that red in sRBG is displayed ecactly as the same red
> as in AdobeRGB or eciRGB (as long as they are in the available range -
> called Gamut).

Thanks for replying - I understand colour managemnt (or I thought I did) and I have an icc colour profile for my monitor. What I don't get is why I need to load it twice - once at startup and then again in Digikam. Logically and intuitively this implies to me that I am now getting the colour adjustments twice - once by the system once by Digikam - and that therefore the colours displayed will be wrong.

My monitor gamma and colour temperature is already factory calibrated to sRGB. What I used to do was simply select my working colour space (wide gamut) and my monitor colour space (sRGB) in digikam. Now I cannot do this.

This stuff is FAR too complicated. I had it working for me but now a software change has stopped that from working.

On a Mac I choose 2 profiles in the system settings and it's all done. On Linux it appears I need to be able to write a thesis on colour management. Why does it need to be so hard?

Mark

>
> So If you want to use your Monitor profile reset all your monitor
> settings to default. Install argyllcms (or xcalib) and load the icc
> file at login (first time: dispwin -I /path/to/display.icc; next:
> dispwin -L). Next you have to load the file as display profile in your
> application.
>
> Be aware: colour management does not improve the colour itself.
>
> Next important step is to choose a working profile. Here you are free
> to choose every profile you want, but without a hardware calibrated
> monitor best use may be sRGB. AdobeRGB does not bring you more colour
> if your Monitor is not able to show it (which most monitors can not).
> Even worse: If you use 8-bit encoded RGB you loose some fine
> granularity in the less saturated part of the image.
>
> Conclusio: If you want to use 8-Bit RGB use sRGB (you avoid problems
> if you print images or give them to others). If you want higher colour
> range use L*-RGB and 16-Bit. But then you have to buy a hardware
> colorimeter and a monitor which can display this colours reliably.
> This will you cost you at least 1000 Euro for the monitor and 250 Euro
> for the colorimeter.
>
> Martin
>
> >
> > Mark
> >
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:

> > Sorry Mark, this is no nonsens. for a colour managed environment
> > you have to calibrate and profile your monitor. Usually this
> > results in a icc or icm file.
> >
> > The calibration stuff is loaded usually at login time. This sets
> > your Gamma curve (and colour temperature) to what you have set up
> > your icc profile to (I have a L-Star gamma and a colour
> > temperature of about 6500K - my native display colour).
> >
> > The profile stuff is done by the application (digiKam, Gimp or
> > UFRaw). So you have to either set it manually in every
> > application or you can use the system wide profile (which is the
> > one you loaded at login). This makes sure that red in sRBG is
> > displayed ecactly as the same red as in AdobeRGB or eciRGB (as
> > long as they are in the available range - called Gamut).
>
> Thanks for replying - I understand colour managemnt (or I thought I
>  did) and I have an icc colour profile for my monitor. What I don't
>  get is why I need to load it twice - once at startup and then
>  again in Digikam. Logically and intuitively this implies to me
>  that I am now getting the colour adjustments twice - once by the
>  system once by Digikam - and that therefore the colours displayed
>  will be wrong.

It is not done twice. The first part fixes gamma, colour temp and
light (if set). It is done for all application using this monitor. No
colour adjustment is done at this stage. As your monitor is hardware
calibrated to sRGB this part may not be necessary but will nor harm.

The second part (done by the application) fixes colours only.

>
> My monitor gamma and colour temperature is already factory
>  calibrated to sRGB. What I used to do was simply select my working
>  colour space (wide gamut) and my monitor colour space (sRGB) in
>  digikam. Now I cannot do this.
>
> This stuff is FAR too complicated. I had it working for me but now
>  a software change has stopped that from working.

This seems to be a bug. You can go around this by loading the default
profile with dispwin and use the system default profile. (I can not
check this, as I am currently stuck to digiKam 0.9).

>
> On a Mac I choose 2 profiles in the system settings and it's all
>  done. On Linux it appears I need to be able to write a thesis on
>  colour management. Why does it need to be so hard?

It is not as easy as for a Mac but not that hard either. As I said
before, you need three steps:
- Install argyllcms
- at first time run dispwin -I /path/to/profile.icc
- at every login run dispwin -L

I have a script in /etc/kde/env called lcms.sh which runs dispwin -L
at every login and I am done. Gimp and UFRaw uses this profile
automatically. The main advantage: If I am on my second computer with
my old Eizo monitor I don't have to change anything (home directory is
on a NFS Server so I have the same settings on every host I log in).

>
> Mark
>

Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Greenwood-2]

On Tuesday 22 Dec 2009 14:56:20 Martin (KDE) wrote:

> Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:
>
> > > Sorry Mark, this is no nonsens. for a colour managed environment
> > > you have to calibrate and profile your monitor. Usually this
> > > results in a icc or icm file.
> > >
> > > The calibration stuff is loaded usually at login time. This sets
> > > your Gamma curve (and colour temperature) to what you have set up
> > > your icc profile to (I have a L-Star gamma and a colour
> > > temperature of about 6500K - my native display colour).
> > >
> > > The profile stuff is done by the application (digiKam, Gimp or
> > > UFRaw). So you have to either set it manually in every
> > > application or you can use the system wide profile (which is the
> > > one you loaded at login). This makes sure that red in sRBG is
> > > displayed ecactly as the same red as in AdobeRGB or eciRGB (as
> > > long as they are in the available range - called Gamut).
> >
> > Thanks for replying - I understand colour managemnt (or I thought I
> >  did) and I have an icc colour profile for my monitor. What I don't
> >  get is why I need to load it twice - once at startup and then
> >  again in Digikam. Logically and intuitively this implies to me
> >  that I am now getting the colour adjustments twice - once by the
> >  system once by Digikam - and that therefore the colours displayed
> >  will be wrong.
>
> It is not done twice. The first part fixes gamma, colour temp and
> light (if set). It is done for all application using this monitor. No
> colour adjustment is done at this stage. As your monitor is hardware
> calibrated to sRGB this part may not be necessary but will nor harm.
>
> The second part (done by the application) fixes colours only.

OK thanks, I understand that now.

>
> >
> > My monitor gamma and colour temperature is already factory
> >  calibrated to sRGB. What I used to do was simply select my working
> >  colour space (wide gamut) and my monitor colour space (sRGB) in
> >  digikam. Now I cannot do this.
> >
> > This stuff is FAR too complicated. I had it working for me but now
> >  a software change has stopped that from working.
>
> This seems to be a bug. You can go around this by loading the default
> profile with dispwin and use the system default profile. (I can not
> check this, as I am currently stuck to digiKam 0.9).
>
> >
> > On a Mac I choose 2 profiles in the system settings and it's all
> >  done. On Linux it appears I need to be able to write a thesis on
> >  colour management. Why does it need to be so hard?
>
> It is not as easy as for a Mac but not that hard either. As I said
> before, you need three steps:
> - Install argyllcms
> - at first time run dispwin -I /path/to/profile.icc
> - at every login run dispwin -L

This is one reason why I say it's hard. It's very non-obvious to someone like me how I get a script to run every time I log in. Also how am I supposed to know that I need this application called 'argyllcms'? It's not something you average user ever wants to take an interest in, or should need to know about - colour management is complex enough without having half the answer made up of random extra bits of software. From what I can see here there's a lot of work still to do to get Colour Management working usefully on Linux. I think I will just disable it for now.

Mark

>
> I have a script in /etc/kde/env called lcms.sh which runs dispwin -L
> at every login and I am done. Gimp and UFRaw uses this profile
> automatically. The main advantage: If I am on my second computer with
> my old Eizo monitor I don't have to change anything (home directory is
> on a NFS Server so I have the same settings on every host I log in).
>
> >
> > Mark
> >
>
> Martin
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> My monitor gamma and colour temperature is already factory calibrated to
>  sRGB. What I used to do was simply select my working colour space (wide
>  gamut) and my monitor colour space (sRGB) in digikam. Now I cannot do
>  this.
>
> This stuff is FAR too complicated. I had it working for me but now a
>  software change has stopped that from working.
>
> On a Mac I choose 2 profiles in the system settings and it's all done. On
>  Linux it appears I need to be able to write a thesis on colour management.
>  Why does it need to be so hard?

You're quite right about the system settings part here. Indeed, there should
be a tab in the system settings allowing you to specify a monitor profile.
This should then be loaded at start of X server and provided to application
via the X atom method outlined above.

_All this is outside the scope of digikam_

Digikam comes in when trying to find a monitor profile. If it finds one
specified by X, it will use it. I don't come up with a usecase where this
should not be done. Thus, the combo box is greyed out.

So the bug is twofold:
1) Distributions should package and install per default a tool to load a
monitor profile (argyllcms appears to be unpackagable though) and at least an
sRGB and an AdobeRGB-compatbible profile (if the Adobe profile package cannot
be installed per default due to license restrictions, dont know)
2) KDE system settings should provide the settings panel.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> Hi,
>
> I've compiled from svn the newest source code (Version 1.1.0 (rev.:
>  1064834)). While checking things I discovered that I cannot choose a
>  monitor profile in the settings anymore. It just says "Monitor Profile
>  from System Settings" and the pull down trigger does nothing.
>
> With older versions (like beta5 oder beta6) this was working and I could
>  select my calibrated monitor profile.
>
> Has this behaviour changed now?
> Where can I check/change the system settings to be sure that digiKam uses
>  my profile?

You'll find long explanations in the other answers. Short is: Digikam will use
the monitor profile provided by X.org, if one is set. (as requested by users
on this list)
I'll make the info button next to the combo box work in that situation, so you
can confirm.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> I'll make the info button next to the combo box work in that situation, so
>  you can confirm.

Please check current SVN if that works.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Marcel Wiesweg:

> > My monitor gamma and colour temperature is already factory
> > calibrated to sRGB. What I used to do was simply select my
> > working colour space (wide gamut) and my monitor colour space
> > (sRGB) in digikam. Now I cannot do this.
> >
> > This stuff is FAR too complicated. I had it working for me but
> > now a software change has stopped that from working.
> >
> > On a Mac I choose 2 profiles in the system settings and it's all
> > done. On Linux it appears I need to be able to write a thesis on
> > colour management. Why does it need to be so hard?
>
> You're quite right about the system settings part here. Indeed,
>  there should be a tab in the system settings allowing you to
>  specify a monitor profile. This should then be loaded at start of
>  X server and provided to application via the X atom method
>  outlined above.
>
> _All this is outside the scope of digikam_

Yes, this is definitly outside the scope of digiKam. But there are so
many myths about CM that sometimes it is good to draw a big picture.

>
> Digikam comes in when trying to find a monitor profile. If it finds
>  one specified by X, it will use it. I don't come up with a usecase
>  where this should not be done. Thus, the combo box is greyed out.
>
> So the bug is twofold:
> 1) Distributions should package and install per default a tool to
>  load a monitor profile (argyllcms appears to be unpackagable
>  though) and at least an sRGB and an AdobeRGB-compatbible profile
>  (if the Adobe profile package cannot be installed per default due
>  to license restrictions, dont know) 2) KDE system settings should
>  provide the settings panel.

At least Fedora 11 has an argyllcms package, so it must be packagable.

Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Greenwood-2]

On Tuesday 22 Dec 2009 18:34:01 Martin (KDE) wrote:

> Am Dienstag, 22. Dezember 2009 schrieb Marcel Wiesweg:
> > > My monitor gamma and colour temperature is already factory
> > > calibrated to sRGB. What I used to do was simply select my
> > > working colour space (wide gamut) and my monitor colour space
> > > (sRGB) in digikam. Now I cannot do this.
> > >
> > > This stuff is FAR too complicated. I had it working for me but
> > > now a software change has stopped that from working.
> > >
> > > On a Mac I choose 2 profiles in the system settings and it's all
> > > done. On Linux it appears I need to be able to write a thesis on
> > > colour management. Why does it need to be so hard?
> >
> > You're quite right about the system settings part here. Indeed,
> >  there should be a tab in the system settings allowing you to
> >  specify a monitor profile. This should then be loaded at start of
> >  X server and provided to application via the X atom method
> >  outlined above.
> >
> > _All this is outside the scope of digikam_
>
> Yes, this is definitly outside the scope of digiKam. But there are so
> many myths about CM that sometimes it is good to draw a big picture.
>
> >
> > Digikam comes in when trying to find a monitor profile. If it finds
> >  one specified by X, it will use it. I don't come up with a usecase
> >  where this should not be done. Thus, the combo box is greyed out.
> >
> > So the bug is twofold:
> > 1) Distributions should package and install per default a tool to
> >  load a monitor profile (argyllcms appears to be unpackagable
> >  though) and at least an sRGB and an AdobeRGB-compatbible profile
> >  (if the Adobe profile package cannot be installed per default due
> >  to license restrictions, dont know) 2) KDE system settings should
> >  provide the settings panel.
>
> At least Fedora 11 has an argyllcms package, so it must be packagable.

Yeah there's an argyllcms package in Ubuntu too. So far however I haven't found an sRGB monitor profile that it can load without reporting some kind of error :(

I agree that this is outside the scope of Digikam, however it's a discussion topic that is only ever likely to come up on this kind of list. So how do we make it move outside this list and into the hands of the people who can solve it? This seems to me to be where the organisation around KDE ought to be able to make a difference. But can it?

Mark

>
> Martin
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:

> On Tuesday 22 Dec 2009 18:34:01 Martin (KDE) wrote:
> > Am Dienstag, 22. Dezember 2009 schrieb Marcel Wiesweg:
> > > > My monitor gamma and colour temperature is already factory
> > > > calibrated to sRGB. What I used to do was simply select my
> > > > working colour space (wide gamut) and my monitor colour space
> > > > (sRGB) in digikam. Now I cannot do this.
> > > >
> > > > This stuff is FAR too complicated. I had it working for me
> > > > but now a software change has stopped that from working.
> > > >
> > > > On a Mac I choose 2 profiles in the system settings and it's
> > > > all done. On Linux it appears I need to be able to write a
> > > > thesis on colour management. Why does it need to be so hard?
> > >
> > > You're quite right about the system settings part here. Indeed,
> > >  there should be a tab in the system settings allowing you to
> > >  specify a monitor profile. This should then be loaded at start
> > > of X server and provided to application via the X atom method
> > > outlined above.
> > >
> > > _All this is outside the scope of digikam_
> >
> > Yes, this is definitly outside the scope of digiKam. But there
> > are so many myths about CM that sometimes it is good to draw a
> > big picture.
> >
> > > Digikam comes in when trying to find a monitor profile. If it
> > > finds one specified by X, it will use it. I don't come up with
> > > a usecase where this should not be done. Thus, the combo box is
> > > greyed out.
> > >
> > > So the bug is twofold:
> > > 1) Distributions should package and install per default a tool
> > > to load a monitor profile (argyllcms appears to be unpackagable
> > > though) and at least an sRGB and an AdobeRGB-compatbible
> > > profile (if the Adobe profile package cannot be installed per
> > > default due to license restrictions, dont know) 2) KDE system
> > > settings should provide the settings panel.
> >
> > At least Fedora 11 has an argyllcms package, so it must be
> > packagable.
>
> Yeah there's an argyllcms package in Ubuntu too. So far however I
>  haven't found an sRGB monitor profile that it can load without
>  reporting some kind of error :(

Yep, that must be the case. As most sRGB defines a working space type
you need a device definition type. Here you have to use the monitor
profile you used previously.

>
> I agree that this is outside the scope of Digikam, however it's a
>  discussion topic that is only ever likely to come up on this kind
>  of list. So how do we make it move outside this list and into the
>  hands of the people who can solve it? This seems to me to be where
>  the organisation around KDE ought to be able to make a difference.
>  But can it?

so may be a whish at b.k.o?

>
> Mark
>

Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Dienstag, 22. Dezember 2009 schrieb Martin (KDE):

> Am Dienstag, 22. Dezember 2009 schrieb Mark Greenwood:
> > On Tuesday 22 Dec 2009 18:34:01 Martin (KDE) wrote:
> > > Am Dienstag, 22. Dezember 2009 schrieb Marcel Wiesweg:
> > > > > My monitor gamma and colour temperature is already factory
> > > > > calibrated to sRGB. What I used to do was simply select my
> > > > > working colour space (wide gamut) and my monitor colour
> > > > > space (sRGB) in digikam. Now I cannot do this.
> > > > >
> > > > > This stuff is FAR too complicated. I had it working for me
> > > > > but now a software change has stopped that from working.
> > > > >
> > > > > On a Mac I choose 2 profiles in the system settings and
> > > > > it's all done. On Linux it appears I need to be able to
> > > > > write a thesis on colour management. Why does it need to be
> > > > > so hard?
> > > >
> > > > You're quite right about the system settings part here.
> > > > Indeed, there should be a tab in the system settings allowing
> > > > you to specify a monitor profile. This should then be loaded
> > > > at start of X server and provided to application via the X
> > > > atom method outlined above.
> > > >
> > > > _All this is outside the scope of digikam_
> > >
> > > Yes, this is definitly outside the scope of digiKam. But there
> > > are so many myths about CM that sometimes it is good to draw a
> > > big picture.
> > >
> > > > Digikam comes in when trying to find a monitor profile. If it
> > > > finds one specified by X, it will use it. I don't come up
> > > > with a usecase where this should not be done. Thus, the combo
> > > > box is greyed out.
> > > >
> > > > So the bug is twofold:
> > > > 1) Distributions should package and install per default a
> > > > tool to load a monitor profile (argyllcms appears to be
> > > > unpackagable though) and at least an sRGB and an
> > > > AdobeRGB-compatbible profile (if the Adobe profile package
> > > > cannot be installed per default due to license restrictions,
> > > > dont know) 2) KDE system settings should provide the settings
> > > > panel.
> > >
> > > At least Fedora 11 has an argyllcms package, so it must be
> > > packagable.
> >
> > Yeah there's an argyllcms package in Ubuntu too. So far however I
> >  haven't found an sRGB monitor profile that it can load without
> >  reporting some kind of error :(
>
> Yep, that must be the case. As most sRGB defines a working space
>  type you need a device definition type. Here you have to use the
>  monitor profile you used previously.

Argh, forget that. I mixed input and display type. Sorry for the
confusion.

Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

> > It is not as easy as for a Mac but not that hard either. As I said
> > before, you need three steps:
> > - Install argyllcms
> > - at first time run dispwin -I /path/to/profile.icc
> > - at every login run dispwin -L
>
> This is one reason why I say it's hard. It's very non-obvious to someone
>
> like me how I get a script to run every time I log in. Also how am I
> supposed to know that I need this application called 'argyllcms'? It's
> not something you average user ever wants to take an interest in, or
> should need to know about - colour management is complex enough without
> having half the answer made up of random extra bits of software. From
> what I can see here there's a lot of work still to do to get Colour
> Management working usefully on Linux. I think I will just disable it
> for now.
>

You don't need to install argyllcms if you have already an ICC profile
for your monitor (e.g. created with a spyder hardware tool under Windows
or MAC).

You just need your *.icc or *.icm file and copy it to a directory. Then
you can load it with "xcalib /path_to_file/monitor.icc" at the start of
X11 (e.g. put a script into ~/.kde/autostart). For this you just need to
install xcalib which is a no-brainer (rpm for different distros are
available).

What makes me angry is that before this software change was made the
installation of argyllcms was not always necessary. With xcalib and
selecting the profile in digiKam prefs it worked perfectly. Now everyone
has to go through the hard way until the distros implement an easy
solution. :-(

Why is it not possible to override the behaviour?

Guenther

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> What makes me angry is that before this software change was made the
> installation of argyllcms was not always necessary. With xcalib and
> selecting the profile in digiKam prefs it worked perfectly. Now everyone
> has to go through the hard way until the distros implement an easy
> solution. :-(
>
> Why is it not possible to override the behaviour?

I dont understand this. Does xcalib set the X atom or not? If not, you can
choose your profile manually. If it does, it's already selected in digikam.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

> > Why is it not possible to override the behaviour?
>
> I dont understand this. Does xcalib set the X atom or not? If not, you can
> choose your profile manually. If it does, it's already selected in digikam.

If it is working that way I'd have no problem. But unfortunately it is
not:

http://www.gmx.de/mc/9JV8lGQjbZ8l19ZBMKwQR25fTlipna

The screenshot was made with Version 1.1.0 (rev.: 1065259) Using KDE
4.3.4 (KDE 4.3.4) "release 2".

Guenther


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users