Re(2): AW: Analyzing Workflow
Re(2): AW: Analyzing Workflow
- Subject: Re(2): AW: Analyzing Workflow
- From: "William Close" <email@hidden>
- Date: Fri, 18 May 2001 07:56:54 -0500
email@hidden writes:
>
The theory (unless you are using a LinoColor/NewColor Lab based system)
>
is to
>
use a neutral RGB workingspace (where gray is R=G=B) for all processing,
>
due
>
to its consistancy, effective monitor preview, and very small Matrix
>
based
>
RGB profile (so tagging it to images does not make them much larger, as a
>
high rez LUT based printer RGB profile would). Then convert as needed,
>
where
>
convenient, to a device specific RGB (or CMYK, or HEX...) output profile.
>
Unlike CMYK, where all spaces are device specific, in RGB work, using a
>
neutral, well mannered, well known, workingspace is much better than
>
working
>
in an output space.
Thanks David- that's what I thought I understood.
But here lately it seems I don't know my head form my...
Another issue has come up:
When we open up raw images from our scanner, assume sRGB (rather than
Adobe 98, our working space) and then convert them to our working space,
we get much better results. I've only done a couple of tests but the
prints seem to match our monitors much more closely.
Could someone shed some light on this? Does this mean the scanner more
closely scans to sRGB than Adobe 98 or am I way off here?
' ' ' ' ' ' ''"""""""""""'' ' ' ' ' '
William Close
GLS, Imaging
713-661-4743