Canon 40D and input colour profile

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Canon 40D and input colour profile

Sebastian Schubert-2
Hi again,

I wanted to use an input profile for my Canon 40D and I found in the
digikam manual that profile series 6101 is the right for the 40D.  Ok, I
found corresponding files in the windows installation of Canon's Digital
Photo Professional, so I set the folder to it's path.  Ok, that way I
was able to choose the Working profile (I would choose Adobe RGB which
is included in the files) and a Soft proof profile.  But I'm not able to
choose a input profile.  Nothing is listed there, I cannot choose
anything!

Any idea?

Thanks again

Sebastian
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Canon 40D and input colour profile

Gerhard Kulzer-3

On Friday 29 August 2008 23:54:23 Sebastian Schubert wrote:

> Hi again,

>

> I wanted to use an input profile for my Canon 40D and I found in the

> digikam manual that profile series 6101 is the right for the 40D. Ok, I

> found corresponding files in the windows installation of Canon's Digital

> Photo Professional, so I set the folder to it's path. Ok, that way I

> was able to choose the Working profile (I would choose Adobe RGB which

> is included in the files) and a Soft proof profile. But I'm not able to

> choose a input profile. Nothing is listed there, I cannot choose

> anything!

>

> Any idea?

Maybe it's a problem with the path to the windows partition or its locale.

Copy the profiles to ~/.color/icc for example, and set the digiKam path to it.

I use the 40D too with those profiles, works well.

Gerhard

> Thanks again

>

> Sebastian

> _______________________________________________

> 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
Reply | Threaded
Open this post in threaded view
|

Re: Canon 40D and input colour profile

Sebastian Schubert-2
* On Sunday, Aug 31 2008 15:34, you wrote:

[Canon 40D profile on windows partition not working]

> Maybe it's a problem with the path to the windows partition or its locale.
>
> Copy the profiles to ~/.color/icc for example, and set the digiKam path to it.
>
> I use the 40D too with those profiles, works well.

Hi,

thanks for the hint.  It somehow solved the problem, which was not the
place of the data, but the capitalization of the .ICC at the end.  Bug
or feature?

Do you use it in connection with 16 bit RAW development?  Do you have a
good method to work around the problem that the picture is too dark? (I
suppose that is meant by the comment in the digikam handbook)

As you are the author of the nice DAM article, do you know a good method
to convert the .cr2 to .dng?

Thanks

Sebastian
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Canon 40D and input colour profile

Bugzilla from mikmach@wp.pl
Dnia Sunday 31 of August 2008, Sebastian Schubert napisał:
> thanks for the hint.  It somehow solved the problem, which was not the
> place of the data, but the capitalization of the .ICC at the end.  Bug
> or feature?

Feature - names on *nices are case sensitive.

m.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Canon 40D and input colour profile

Sebastian Schubert-2
* On Sunday, Aug 31 2008 23:09, you wrote:

> Dnia Sunday 31 of August 2008, Sebastian Schubert napisał:
>> thanks for the hint.  It somehow solved the problem, which was not the
>> place of the data, but the capitalization of the .ICC at the end.  Bug
>> or feature?
>
> Feature - names on *nices are case sensitive.

Yeah, I know, but digikam opens .jpg and .JPG, etc.  I think most of the
programs are not sensitive to the capitalization of the suffix, that's
the reason why I asked.  I mean, is there a reason why .ICC is bad?  Ok,
somehow it does not feel good... :)

Cheers

Sebastian
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Canon 40D and input colour profile

Bugzilla from mikmach@wp.pl
Dnia Monday 01 of September 2008, Sebastian Schubert napisał:
> * On Sunday, Aug 31 2008 23:09, you wrote:
> > Dnia Sunday 31 of August 2008, Sebastian Schubert napisał:
> >> thanks for the hint.  It somehow solved the problem, which was not
> >> the place of the data, but the capitalization of the .ICC at the end.
> >>  Bug or feature?
> >
> > Feature - names on *nices are case sensitive.
>
> Yeah, I know, but digikam opens .jpg and .JPG, etc.  I think most of the

Because it's properly configured somewhere - either digiKam or
kcontrol/systemsettings.

Hmm, from this perspective looks like it is bug indeed. .ICC should be
included in default configuration to be recognized.

m.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Canon 40D and input colour profile

Gilles Caulier-4


2008/9/1 Mikolaj Machowski <[hidden email]>
Dnia Monday 01 of September 2008, Sebastian Schubert napisał:
> * On Sunday, Aug 31 2008 23:09, you wrote:
> > Dnia Sunday 31 of August 2008, Sebastian Schubert napisał:
> >> thanks for the hint.  It somehow solved the problem, which was not
> >> the place of the data, but the capitalization of the .ICC at the end.
> >>  Bug or feature?
> >
> > Feature - names on *nices are case sensitive.
>
> Yeah, I know, but digikam opens .jpg and .JPG, etc.  I think most of the

Because it's properly configured somewhere - either digiKam or
kcontrol/systemsettings.

Hmm, from this perspective looks like it is bug indeed. .ICC should be
included in default configuration to be recognized.


This is not a bug from digiKam.  It a problem from your icc color profiles witch do not respect standard. It's a know problem with Canon profiles.

If you have compiled digiKam with debug symbols, you will see few reports on the console about the parsing results of all profile files generated by LCMS library. You will see that a lots of files are not recognized.

You can thanks Canon to make private icc color profiles...

I know that digiKam must be more verboze in this case.  A new report dialog from ICC setup must be added.

Gilles Caulier


m.

_______________________________________________
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