Yahoo Groups archive

Datacolor User to User Support Group.

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

Message

Spyder3Print profiles worse than standard Canon driver?

2009-08-27 by Bob Petruska

I currently have the 6 color Canon I950 and in the process of 
purchasing the Canon Pro 9500 MKII.

I purchased the Spyder3Print to be able to generate "great" Printer 
profiles using different papers and inks.

I have profiled many different papers on the I950 and was fairly 
happy with the results, but the printed skin tones were just slightly 
off compared to the calibrated NEC monitor image and took a little 
tweaking by adding color to the image in CS4 or Nikon Capture NX2 and 
high loss of paper/ink to try and get the skin tones I wanted, but 
was never completely successful.

The other day I just turn off the Spyder profiles, turned on the 
Canon standard printer driver, checked auto, and WOW the printed skin 
tones matched my monitor image perfectly!  All printed colors were a 
significantly closer match to the monitor than the Spyder3Print profiles.

What is wrong here?  I would think that the Sypder would generate 
profiles as good or better than the Canon standard printer driver in 
auto mode!  Does Canon perform some magic tweaking of their profiles 
to produce great color matching that can't be accomplished by Spyder profiling?

I'm a little concerned with this before I buy the Canon 9500 and find 
out that my Spyder generated profiles will not match the monitor as 
well as the Canon standard profile especially when I was planning on 
using a wide range of papers.

It's just amazing that the Spyder3Print test target photos printer to 
monitor matching with standard Canon driver is almost perfect and the 
Spyder ICC profiles are not.



Any suggestions on how I can get great print/monitor color matching?


What could I posibly be doing wrong?


Thanks,


Bob P.

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.