QTR-Quadtone RIP

Anyone know a Mac workflow for loading ACV curves from photoshop into QTR ink 
descriptor files.  By following many of Paul Roark's posts it sounds like there is a direct 
capability in the Windows version and that seems to be the method he uses to create his 
curves for things like the 3MK inksets.

I can see, and have done, this manually by transcribing points but I'm wondering if there is 
a shortcut I'm missing.

robert49brake wrote:

>Anyone know a Mac workflow for loading ACV curves from 
>photoshop into QTR ink descriptor files. 

> By following many of Paul Roark's posts it sounds like 
> there is a direct capability in the Windows version 
> and that seems to be the method he uses to create his 
> curves for things like the 3MK inksets.

> I can see, and have done, this manually by transcribing 
> points but I'm wondering if there is a shortcut I'm missing. 

Actually, I tried the *.acv to QTR curves method a few times and decided
against using it.  I could not keep track of the acv curves well enough.  I
vastly prefer either using Roy's semi-automatic partitioning method or
manually specifying the points in the point list.  The 3MK curves are all
essentially the same curve, aside from some minor changes in the end points
due to different ink loads needed for different papers.

Where I'm going now is using multiple, overlapping curves for the K6 - K8
inksets.  That is, rather than having one serial partitioning, I'll have 2
or more, perhaps totally different and independent profiles for the inks,
and then combine them with the QTR sliders.  In my initial experiments, this
seems to produce the best results.

Actually, with the 1800 system I now have with both the 3MK and Eboni-6
inksets loaded, the combining or mixing via the sliders of the super-smooth
dilute with the full strength and slightly grainy 3MK allows me to optimize
the "granularity" of the system.  While we may think that the smoothest is
always the best, I don't happen to agree, at least for many images.  Given
the reality of imperfect machines and files, I find I can often produce a
better looking print if it has a bit of grain to it.  Frankly, it hides
defects -- and at the limits and with a loupe there are always defects of
some sort -- and we've knows for years that a very sharp grain gives the
impression of sharpness that is really beyond the actual image information.
Our eyes often see that sharp grain and think the underlying image is
sharper than it really is.

Paul
www.PaulRoark.com

-- and we've knows for years that a very sharp grain gives the
> impression of sharpness that is really beyond the actual image
information.
> Our eyes often see that sharp grain and think the underlying image is
> sharper than it really is.
> 
> Paul
> www.PaulRoark.com

The beauty of grain in 35mm was emphasized by long-lost 2475 Recording
Film, which could be hyper-sharp (not similar to "high resolution")
when its grain was left intact, rather than dissolved. Many of us used
DK50 and rated it at relatively slow 800 rather than the easily
achieved 3200 for exactly that grain reason, AND to enjoy the
incredibly long tonal scale. 

Incidentally, there IS no such thing as "underlying image information"
when it's not in the film. Loss of potential detail (eg through
today's reliance on zoom lenses)is directly comparable to abandonment
of potential tones through use of short scale films (such as Velvia).

>

--- In QuadtoneRIP@yahoogroups.com, "Paul Roark" <paul.roark@...> wrote:

> Actually, I tried the *.acv to QTR curves method a few times and decided
> against using it.  I could not keep track of the acv curves well enough.  I
> vastly prefer either using Roy's semi-automatic partitioning method or
> manually specifying the points in the point list.  

I eventually did find that to be the case as well.  It was my first time creating curves and 
profiles for an unsupported inkset on a specific printer and I was dancing around looking for 
a starting point.  End result was jumping in and playing with the different (and older) 
commands.  It was really impressive how QTR can automatically get you into the ballpark 
even before linearization.