Re: profile spaces vs working spaces
Re: profile spaces vs working spaces
- Subject: Re: profile spaces vs working spaces
- From: email@hidden
- Date: Fri, 17 Oct 2003 10:04:55 EDT
In a message dated 10/17/03 1:04:40 AM, email@hidden
writes:
>
Can anyone tell me why it is really good to
>
move a file to a "working space" (AdobeRGB)
>
instead of just working in a capture profile or output profile
>
(Ektaspace or sRGB).
>
>
Is there something in the code that makes something a "working space"?
>
Do conversions go better?
>
>
Why not keep a file in my scanner profile untill I convert to SWOP or
>
sRGB.
>
There are advantages to either strategy. A workingspace has a few advantages
for editing, like neutral grays all the way from black to white where R equals
G equals B, and other rational form factors. A workingspace profile a only a
few percent the size of a LUT based space as well, and its a universal space
that everyone has access to, and knows the basic rules for. But this doesn't
mean that in image *has* to go thorugh one, only that its a good place to keep
images for multiple uses or multiple users. If you have a good source profile,
a good printer profile, and little happening in between, a direct conversion
from one to the other has some theoretical advantages. Whether those translate
into any real-world advantages, other then eliminating a step, is what you
need to determine.
C. David Tobie
Product Technology Manager
ColorVision Inc.
email@hidden
www.colorvision.com
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.