• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AW: Analyzing Workflow
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: Analyzing Workflow


  • Subject: Re: AW: Analyzing Workflow
  • From: email@hidden
  • Date: Fri, 18 May 2001 08:35:29 EDT

In a message dated 5/18/01 12:26:35 AM, email@hidden writes:

>I think you missunderstood me, I had say, that he should use the
>
>PrinterProfile of his RGB Printer and not the Monitor Profile as Workspace.
>
>I know, that the Adobe RGB is much better as Workingspace as the Monitor
>RGB
>
>if you want separate to CMYK via ICC, but why should I do this if I have
>an
>
>original RGB Space for printing.
>
>If somthing is wrong in my thinking please let me know, because RGB is
>not
>
>so common in the proofing area.

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.

C. David Tobie
Design Cooperative
email@hidden


  • Follow-Ups:
    • Re(2): AW: Analyzing Workflow
      • From: "William Close" <email@hidden>
  • Prev by Date: Re: Proofing on Destination Stock
  • Next by Date: Re(2): AW: Analyzing Workflow
  • Previous by thread: AW: Analyzing Workflow
  • Next by thread: Re(2): AW: Analyzing Workflow
  • Index(es):
    • Date
    • Thread