Re: Multiple profile device support

[Pascal de Bruijn <pmjdebruijn pcode nl>]

On Wed, May 26, 2010 at 10:29 AM, Richard Hughes <hughsient gmail com> wrote:
> Why might we want more than one profile for a device?
>
> * A monitor has two selectable modes, sRGB and wide gamut

Does this actually make sense? Not really....

You profile your monitor, and then the CMS convert sRGB into the screens RGB...

A display profile will always be about a display's native gamut
(within a certain set of display settings).

But again here, for the display settings, there is usually only way
correct way to set them.

> * A printer has different profiles depending on the media and inks

Profiles galore!

> * A camera has different profiles depending on whether it's shot in
> the studio or outside

Indeed... Though this is often very much exaggerated...

A single profile well-made against daylight or a strobe can usually
cover 80/90% of your usage scenario's, unless you're really anal
retentive...

> * Scanners, where nothing can be altered

Think of negative/positive scanning as well, which could mean a
profile per type of negative.

> So, if we decide we need prefs UI to choose between studio and outside
> camera profiles, what should it looks like?
> ___________________________________
> | Nikon D60 Studio (default)
> |#Nikon#D60#Outside################
> |__________________________________

This makes very little sense! At least if I'm getting this right (big IF) :)

When developing RAWs:
Which profile to apply is a decision you make on-the-fly when working
with a RAW converter...

When printing:
Which profile to apply is a decision you make on-the-fly when loading
the printer with paper before printing... This could very well be per
1 sheet...

When scanning:
To set a generic scanner profile this make sense... but for
negatives/transparancies this is something you would apply on-the-fly
using the scanning tool...

So I'm not sure to what extent it is useful for GCM to get involved
here... Except for setting the default profile :)

Regards,
Pascal de Bruijn