Re: BW previewing and DigCamera profiling
Re: BW previewing and DigCamera profiling
- Subject: Re: BW previewing and DigCamera profiling
- From: Andrew Rodney <email@hidden>
- Date: Fri, 23 Mar 2001 07:05:59 -0700
on 3/23/01 6:43 AM, email@hidden at email@hidden wrote:
>
I was recently told (no NDA, in a public place)
>
that the upcoming derivatives of the D1 will use AdobeRGB as their target
>
space.
I'd take that with a grain of salt. Maybe. But Nikon told users the D1 used
NTSC RGB and I don't buy that for a second (just open a file from a D1 in
NTSC RGB and assign the profile and the image still looks like crap). Make a
custom profile and the image looks pretty good. Nikon in my mind is one
company that hasn't much of a clue about ICC color management (based on my
experiences with the D1 and their scanners).
It seems camera manufactures have two basic options:
1. Provide a wide gamut space that really represents what the cameras can
provide (and allow the user to profile it or produce a good canned profile).
This is common with many higher end scanners.
2. Force the data into some "known" colorspace like Adobe RGB (more often
it's sRGB when dealing with a consumer camera). This is common for some
consumer end scanners.
Neither approach is perfect depending on what you, the user is doing. If you
have no plan to use or create a custom profile, forcing a file into a known
space isn't so bad. Unless of course it's sRGB and you want something
bigger. But at least it's not ambiguous RGB (unless you happen to be Nikon
and like to tell people the file is in one space when it really isn't).
I've found cameras like the Fuji S1-Pro produce pretty nice output when you
simply assume (assign) ColorMatch RGB to the file you get. The E-10 is
working well for me in that space too (I wonder why you find sRGB better).
Have you tried using the raw 10 bit file for profiling?
Andrew Rodney