Re: Profiler PRO
Re: Profiler PRO
- Subject: Re: Profiler PRO
- From: email@hidden
- Date: Fri, 31 Aug 2001 12:54:33 EDT
In a message dated 8/31/01 11:29:46 AM, email@hidden writes:
>
I thought you were nuts at first CDT but I think I understand the thinking
>
now a bit better:
Yes, it seemed pretty bizarre to me when I first started unraveling it, too,
but the results were so good, I had to give it a chance, even though it was
outside the usual mindset.
>
>
* Determine ink limits, both per channel and total, PRIOR to printing the
>
target (Best does this using linearization and total ink settings, as do
>
other CMYK RIPs).
I believe ProfilerPRO actually goes further with this then simple channel
linairization does, but the idea is the same and, interestingly, eliminates
those pre-LUT curves in the profile at the same time.
>
>
* Separate RGB target to these CMYK parameters.
>
>
* Print, measure and profile.
Correct, though you don't make any comment on using the same setting when
profiling that were used when printing the target...
>
>
The hole I still have in my thinking is:
>
>
* Is building the ink limit/linearization data into the CMYK target
>
*inherently* better than printing a "raw" target and having the RIP apply
>
this supposedly same data to the target during printing.
>
Does one somehow
>
preserve more of the gray levels or produce smoother profiles than the
>
other? Why?
In theory you could make a case for the preseperated info offering improved
accuracy or smoothness (as well as a certain efficiency), but of course its
the real world results that matter...
>
>
* Doesn't the profiling app need to know what CMYK values were in the target
>
(reference data in ProfileMaker terms) and where does it get this?
It needs to know what settings were used when printing the target, so it can
determine the patch values that would be created.
In other
>
words, is there a magic application that can simply "read" the CMYK values
>
in the target and translate it into a properly formatted text file for
>
the
>
profiling app to reference to when measuring the print and generating the
>
profile? Or does one have to go thru patch-by-patch and manually create
>
the
>
text/reference data?
Its all hidden away in the application, but yes, it does determine what the
values of the printed patches "should" be, in order to build the correction
tables which are the heart of any output profile.
C. David Tobie
Design Cooperative
email@hidden