suddenly cannot choose a monitor profile in settings

[Marcel Wiesweg]

> > 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:

There is indeed something mysterious going on.

I did "dispwin <profile>" and digikam detected there was a system profile
detected, but the atom was empty. In this case, digikam will now ignore this.

Then I did "dispwin -I <profile>" and the atom was set, as well properly in
the info dialog.

Use "xprop -root  | grep ICC" to check that the _ICC_PROFILE atom is indeed
set. With current SVN, digikam will only use non-empty data from X.

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

> There is indeed something mysterious going on.
>
> I did "dispwin <profile>" and digikam detected there was a system profile
> detected, but the atom was empty. In this case, digikam will now ignore this.
>
> Then I did "dispwin -I <profile>" and the atom was set, as well properly in
> the info dialog.
>
> Use "xprop -root  | grep ICC" to check that the _ICC_PROFILE atom is indeed
> set. With current SVN, digikam will only use non-empty data from X.
>

"xprop -root  | grep ICC" does not output anything after xcalib
profile.icc. Then I tried "dispwin -I <profile>" and "dispwin
<profile>", but the result is always the same: no atom set. The profile
is loaded correctly using both tools.

The interesting thing is that after I've played with these different
methods of loading a monitor profile digiKam enabled the profile
selection again (shot9.png in the shared folder):

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


Guenther

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

[Milan Knížek]

Guenther Erhard píše v So 26. 12. 2009 v 13:04 +0100:

> > There is indeed something mysterious going on.
> >
> > I did "dispwin <profile>" and digikam detected there was a system profile
> > detected, but the atom was empty. In this case, digikam will now ignore this.
> >
> > Then I did "dispwin -I <profile>" and the atom was set, as well properly in
> > the info dialog.
> >
> > Use "xprop -root  | grep ICC" to check that the _ICC_PROFILE atom is indeed
> > set. With current SVN, digikam will only use non-empty data from X.
> >
> "xprop -root  | grep ICC" does not output anything after xcalib
> profile.icc. Then I tried "dispwin -I <profile>" and "dispwin
> <profile>", but the result is always the same: no atom set. The profile
> is loaded correctly using both tools.

xcalib only updates the video card gamma settings (i.e. sets the monitor
to a calibrated state) and does not touch _ICC_PROFILE atom in X.org.

You want to do also the second step: to "copy" the ICC profile to X.org
so that you do not have to set it manually in the Settings of each
application. This can be done by "xicc"
http://packages.debian.org/search?keywords=xicc

Once you do that second step, "xprop -root | grep ICC" should produce
some output.

dispwin from argyllcms does both steps at once, if it does not work for
you, try the xicc instead. Do not worry about "double" calibration -
only the last run command is valid.

Regards,

Milan Knizek
knizek (dot) confy (at) volny (dot) cz
http://www.milan-knizek.net - About linux and photography (Czech
language only)

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

[Milan Knížek]

Mark Greenwood píše v Út 22. 12. 2009 v 15:57 +0000:

> > > 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.

There are projects aiming to simplify the matter for an ordinary user:

GNOME Color Manager (tends to be more user friendly)
http://projects.gnome.org/gnome-color-manager/

Oyranos: (a bit more full-feature project - more of "backend" type to be
used by GUI tools inside KDE/GNOME/...)
http://www.oyranos.org/wiki/index.php?title=Oyranos

I do not know about KDE, though.

Regards,

Milan Knizek
knizek (dot) confy (at) volny (dot) cz
http://www.milan-knizek.net - About linux and photography (Czech
language only)

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

> xcalib only updates the video card gamma settings (i.e. sets the monitor
> to a calibrated state) and does not touch _ICC_PROFILE atom in X.org.
>
> You want to do also the second step: to "copy" the ICC profile to X.org
> so that you do not have to set it manually in the Settings of each
> application. This can be done by "xicc"
> http://packages.debian.org/search?keywords=xicc
>
> Once you do that second step, "xprop -root | grep ICC" should produce
> some output.
>

This works!

Calling "xcalib myprofile.icc" and after that xicc "myprofile.icc"and I
get an output of "xprop -root | grep ICC". Digikam has the selector
disabled again, but this time my profile is shown correctly with the
info button.

I have no clue why dispwin does not do the 2nd step on my installation.

Thanks,
Guenther



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

[Milan Knížek]

Guenther Erhard píše v So 26. 12. 2009 v 21:09 +0100:

> > xcalib only updates the video card gamma settings (i.e. sets the monitor
> > to a calibrated state) and does not touch _ICC_PROFILE atom in X.org.
> >
> > You want to do also the second step: to "copy" the ICC profile to X.org
> > so that you do not have to set it manually in the Settings of each
> > application. This can be done by "xicc"
> > http://packages.debian.org/search?keywords=xicc
> >
> > Once you do that second step, "xprop -root | grep ICC" should produce
> > some output.
> >
> This works!
>

Glad to hear that.

> I have no clue why dispwin does not do the 2nd step on my installation.

If you are interested, ask the developer in the mailing list:
http://www.argyllcms.com/mailinglist.html

Regards,

Milan Knizek
knizek (dot) confy (at) volny (dot) cz
http://www.milan-knizek.net - About linux and photography (Czech
language only)

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

[Elle Stone]

On Dec 22, 2009 Marcel(?) said,
"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."

I would like to offer "a usecase where this [greying out the combo box] should not be done". Here it is:

It is both possible and useful to have more than one completely different, but equally valid and useful monitor profiles. I list 4 such alternative monitor profiles:

(1) one monitor profile for general editing. This would be the system-installed monitor profile.
(2) a different monitor profile, tailored to your printer-paper-lighting combination, for soft-proofing prints.
(3) a third, lut-style monitor profile that is useful for inspecting details that might be lost upon conversion from raw color to a standard working space.
(4) a fourth monitor profile that is just for editing black and white images, totally sacrificing color accuracy for the sake of better tonal accuracy.

Gimp and UFRaw allow the user a choice even if a system monitor profile has been installed. Could digiKam please please please pretty please be modified to allow the user the same freedom of choice?

Warmest regards,
Elle Stone