Yahoo Groups archive

QTR-Quadtone RIP

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

Message

RE: [QuadtoneRIP] Re: Creating custom gray ICC profile (QTR workflow)

2014-09-15 by Elliot Puritz

I admit to being a bit puzzled about the "entire profile business".  I recognize that some here are very computer savvy, and enjoy making their own profiles for black and white and color printing.  Note that of course there is no criticism directed at such skilled photographers.  Indeed, I wish I had both the skill and the equipment to make such profiles.

 

However, when one can install profiles ( from Jon Cone for BOTH his Piezography and color inks and from various printer manufacturers for virtually every digital paper that one might consider when using their own print tools) why is it necessary to construct one's own profiles?   I currently use Jon's profiles for the black and white printing I accomplish using Piezography and I wonder if other profiles would be at all superior.

 

No doubt I must appear to be naïve.  However, for those of us who do not desire to construct bespoke profiles:  Can't one simply use the profiles provided and then tweak the setting(s) in our editing programs based upon the appearance of the print?  One might consider the first print a "test sheet" and modify accordingly.

 

Elliot

 

 

 

From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] 
Sent: Monday, September 15, 2014 1:22 PM
To: QuadtoneRIP@yahoogroups.com
Subject: [QuadtoneRIP] Re: Creating custom gray ICC profile (QTR workflow)

 

  

there has to be a some gotcha in there somewhere making this more difficult than it should be. Maybe take a look here, everything is provided, charts and reference targets for colorport-

http://www.on-sight.com/using-colorport-for-qtr-grayscale-and-alt-process-measurement-and-profiling/

 



It's been working for me without problems

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.