Yahoo Groups archive

Datacolor User to User Support Group.

Index last updated: 2026-04-28 23:18 UTC

Thread

CMYK profile using pfpro

CMYK profile using pfpro

2007-02-22 by Eesh Dewan

Hi,

I was working with print fix pro and tried my hand at creating color profile for offset. I could follow the below process to get a resonably good profile.

I used Photoshop for creating profile. After reading patches of 100% color of Cyan, Magenta, Yellow, Black, Red, Green, Blue, CMY and paper white, I noted down the Lab values using print fix pro.After this i read the lab values of 50% c, m, y and k. After that i used the spreadsheet from www.brucelindbloom.com for calculating dot gain using lab values.

We plug the lab values in custom ink dialog box of photoshop. and we put the dot gain values in their respective boxes in dot gain column.

Then we save this cmyk setup, which is saved as a profile.

Am i missing something more or am i wrong in this?

Regards

Eesh Dewan
India

Re: [colorvision_group] CMYK profile using pfpro

2007-02-22 by CDTobie@aol.com


In a message dated 2/22/07 12:51:02 PM, eeshdewan@... writes:



We plug the lab values in custom ink dialog box of photoshop. and we put the dot gain values in their respective boxes in dot gain column.

Then we save this cmyk setup, which is saved as a profile.

Am i missing something more or am i wrong in this?



This does indeed create the shell of a CMYK profile. Its has only one intent, lacks a lot of data typically built into a profile, and is based on dot gain assumptions that worked a lot better when dots were 150 dpi then they do at 1440 dpi. For instance, what if Cyan and Magenta don't blend linearly? Where do you measure that? (you don't). Even if you measure lots of patches per channel, thats still two dimensional data being stretched into a 3d profile. But yes, this will build a CMYK profile, of sorts.

C. David Tobie
Product Technology Manager
ColorVision Business Unit
Datacolor Inc.
CDTobie@...
www.colorvision.com



**************************************
AOL now offers free email to everyone. Find out more about what's free from AOL at http://www.aol.com.

Re: [colorvision_group] CMYK profile using pfpro

2007-02-22 by Eesh Dewan

Hi,
Actually, I was trying to use printfix pro like in this article written long time ago http://www.digitaldog.net/files/RGBtoCMYKconversons.pdf . I understand we have moved a lot forward since that time in the world of color management. Yes, i will acknowledge that you are absolutely correct, what i was trying to say is that i feel i have a workable solution with it's limitations but which gets us to a ballpark and maybe better than the canned profiles from MY particular usage.
Regards
Eesh
Show quoted textHide quoted text
----- Original Message -----
Sent: Thursday, February 22, 2007 11:28 PM
Subject: Re: [colorvision_group] CMYK profile using pfpro


In a message dated 2/22/07 12:51:02 PM, eeshdewan@gmail.com writes:



We plug the lab values in custom ink dialog box of photoshop. and we put the dot gain values in their respective boxes in dot gain column.

Then we save this cmyk setup, which is saved as a profile.

Am i missing something more or am i wrong in this?



This does indeed create the shell of a CMYK profile. Its has only one intent, lacks a lot of data typically built into a profile, and is based on dot gain assumptions that worked a lot better when dots were 150 dpi then they do at 1440 dpi. For instance, what if Cyan and Magenta don't blend linearly? Where do you measure that? (you don't). Even if you measure lots of patches per channel, thats still two dimensional data being stretched into a 3d profile. But yes, this will build a CMYK profile, of sorts.

C. David Tobie
Product Technology Manager
ColorVision Business Unit
Datacolor Inc.
CDTobie@colorvision.com
www.colorvision.com



**************************************
AOL now offers free email to everyone. Find out more about what's free from AOL at http://www.aol.com.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.