• 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: Device Link Profiles
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Device Link Profiles


  • Subject: Re: Device Link Profiles
  • From: Klaus Karcher <email@hidden>
  • Date: Wed, 10 Jan 2007 10:04:08 +0100

Lee Blevins schrieb:
My question is:

Are they consistent in what items are controlled by a device link
profile or is the a decision made by the programmers of the software?

Is there an ISO standard Device link profile is what I guess I'm asking?


The ICC specs (http://www.color.org/icc_specs2.html) distinguish (amongst others) between:


* Device Profiles for three different classes of devices (input-, display- and output devices) and

*DeviceLink Profiles

Device Profiles always build a link between a certain device and the PCS (profile connection space). You always need two of them to transform colors between two devices: the CMM takes the instructions how to transform from the first device colorspace to the PCS from the first profile (e.g. one of its A2B tables) and the instructions how to transform from the PCS to the second device from the second profile (one of its B2A tables).

DeviceLink Profiles form -- as the name implies -- a link between two dedicated devices, e.g. AdobeRGB and SWOP or ISOcoated and GRACol without referencing the PCS.

The advantage of device profiles is flexibility: you can connect any devices. By contrast each combination of two devices needs its own DLP.

The advantages of DeviceLink Profiles are:

* higher precision (the interpolation nodes are not limited to the PCS grid)

* the output part "knows about" the input part, e.g. a device link profile from ISO Coated to SWOP "knows" that CMYK 17/12/11/1 and CMYK 0/0/0/20 are different input values. Ordinary device profiles only can see the PCS coordinates, which are the same in both cases.

That means, a deviceLink profile *can* (not *must*) consider the separation of the input space, a device profile *can not*.

The ICC specs only describe the file format of a DLP, what to make of it depends on the intended use and the software that builds it.

A "smart CMM" could build DLPs of to two device profiles involved in a transformation on the fly and therefore could benefit of both ways. However the creation of a DLP is a complex, time consuming act.

Regards,
Klaus
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Device Link Profiles (From: email@hidden (Lee Blevins))

  • Prev by Date: Re: Device Link Profiles
  • Next by Date: Re: Colorsync-users Digest, Vol 4, Issue 19
  • Previous by thread: Re: Device Link Profiles
  • Next by thread: RE: Device Link Profiles
  • Index(es):
    • Date
    • Thread