Multiple profile device support

[Richard Hughes]

On 26 May 2010 17:45, Pascal de Bruijn <pmjdebruijn at pcode.nl> wrote:
> I actually have a HP screen, it does have an sRGB mode indeed... But
> this means the screen fiddles with it's internal LUT a bit to fake
> this... It's not really a great idea...

Sure, I don't disagree.

> That's why I set my brightness to a value that correlates to ~200cm/m2.

Out of interest, how did you measure that?

> And that's how it should be in the future... GCM can only help by not
> providing any irrelevant profiles...
>
> So if I have a 400D, it could provide 400D profiles only so if I have
> a 5D as well, I won't see those profiles...

Sure at the moment it matches against make, model and camera serial number.

> But GCM cannot tell whether a picture needs the "daylight" profile or
> the "studio" profile...

Correct. In the absence of hints GCM provides both profiles, well, it
actually provides the filename and the description ready formatted, so
applications like GIMP can easy populate a combobox if there are more
than one entry and they don't just want the default. It's the reason
we have the complicated a(ss) return type so applications don't have
to parse the profile themselves to get the localized description
value.

> Again the scanning app doesn't know whether I'm scanning a
> transparancy or not...

It might, cleverer HP scanners can detect what accessories they have
inserted. In general I agree tho.

> But for say XSane (if anybody is still working on that, god forbid),
> it would still be the end-user that need to select which exact profile
> he needs to apply to his image... Obviously profiles for completely
> different scanner types could be omitted.

At the moment GCM just sets up the XSane default profile with the
default profile for the device. I know for sure it can't support more
than one profile, and I also know that XSane struggles with filenames
with spaces in them...

> Profiles are not per-se interchangeable between different
> applications... For example UFRaw does not output 100% true linear RGB
> RAW before applying the profile... DCRAW/Darktable do at least as far
> as I know...

Surely that's a UFRaw bug then?

Richard.