Yahoo Groups archive

Datacolor User to User Support Group.

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

Message

Re: [colorvision_group] Not satisfied with PrintFix Pro profile - Any way to improve?

2007-02-18 by David Miller

>Using PrintFix Pro 2.0, I created a 729 patch plus extended gray patch
>based profile for Epson Radiant White Watercolor. The paper that many
>clients have me use for making prints of their artwork.

I've profiled this on an Epson 4800 and done a lot of prints with it, also
as 729 patches.

>When I tested
>the profile by printing the standard test target provided with the
>software, I felt very satisfied. In all respects the printed target
>was a very close match to the image on my screen (profiled with the
>SpyderII Pro). However, when I make prints of my clients artwork, I
>find that often subdued hues do not match the soft proof version on
>the monitor screen. For example tan colored shades will look too
>greenish. When I do a gamut check in Photoshop CS2, the colors appear
>to be in gamut. In theory it seems that the color can be reproduced by
>the Epson 2200 that I use for printing. By doing localized
>adjustments, I can get the inaccurate color to be a much closer match.
>But I use the PrintFix Pro profile and the appropriate printing setup
>in Photoshop color management to avoid having to do this.

What rendering intent are you soft proofing and printing through? (and
when you're soft proofing in Photoshop, you're doing this by going into
View:Proof Setup:Custom, selecting the profile and rendering intent, turning
on Preview, and leaving the other check boxes off (having the paper black
and paper white simulation on makes the soft proof visually too muddy, and your
brain adjusts well enough for those things, so I'd recommend not using them).

What light source are you viewing the prints under?

You've got the display calibrated to D65, 2.2, correct?

Best regards,

-- 
David Miller
Senior Software Developer, Digital Color Solutions
ColorVision

Attachments

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.