Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Curves help?

2006-10-29 by houstonspencer

Tom:

Many thanks for your guiding questions.  Apologies for my silence.
Travel commitments have kept me from printing.

Here are some -- I hope -- narrowing answers.

*You wrote*: "When you say EEM equivalent paper what do you mean -
which paper exactly. You don't state which QTR curves you are using.
Which are these."

I'm using Epson Archival Matte and Epson Matte Paper Heavyweight. 
Curves: mostly UC-EEnhMatte-warm. Warm is the tonality I'm looking
for, but I've also been playing with combinations with the other
UC-EEnhMatte curves to try to understand their properties.

*You wrote*: "You should always be using at least 1 curve in QTR. If
you're using UC inks and EEM paper on a 2100, there should be should
be curves already available."

Yep, thanks.  As you can see from the above, I am using them.

*You wrote*: "Have you read the QTR User Guide?"

Beginning to end, even the parts I didn't really understand about
curve creation.

*You wrote*: "It's also a good idea to state which machine type (PC or
Mac), OS version, QTR version, printer, inkset, paper brand and type,
QTR curves selected and any other details specific to your problem."

Sorry not to have done so: PC, XP, QTR 2.4.2.11, Epson 2100, UC inks,
paper as above, curves as above.  

To reiterate from my first post, my results are good -- smooth as silk
-- they're contrast just isn't very close to two different calibrated
monitors.

Appreciate any advice on tracking down likely culprits.

This is the last link in my transition out of the darkroom.  So,
thanks very much, in advance, for the newbie tolerance.

Cheers.  -Houston



--- In QuadtoneRIP@...m, "Tom Moore" <r.t.moore@...> wrote:
>
> Houston
> 
> You have posed question that could have a very involved answer.
> Responding to some of the questions below might get the discussion
going.
> 
> --- In QuadtoneRIP@yahoogroups.com, "houstonspencer"
> <houston.spencer@> wrote:
> >
> > 
> > Would be very grateful for any advice on how to get started with
> > developing curves to address the common issue outlined below. Having
> > asked once before without result, I'd be particularly glad of any
reply.
> > 
> > I've just run my first few prints via QTR on a 2100. I'm not getting
> > anything like a match -- tonality and contrast --
> > between screen and print. Two calibrated monitors on two different
> > machines show significantly higher contrast and lighter mid-tones than
> > the prints. I've played with gamma and ink limit adjustment in QTR,
> > but they don't go nearly far enough to solve the problem.
> 
> With the appropriate QTR curve you shouldn't have to use much (if any)
> gamma or ink limit adjustment to get close. 
> 
> > 
> > (I'm using standard UC inks and standard EEM-equivalent paper.)
> > 
> 
> When you say EEM equivalent paper what do you mean - which paper
> exactly. You don't state which QTR curves you are using. Which are
these.
> 
> > I'm assuming, at this point, I'm going to have to apply a curve,
> > either to the image in PS or directly in QTR. But, frankly, I don't
> > really know what I'm doing there, and I don't want to spend weeks
> > profiling.
> 
> You should always be using at least 1 curve in QTR. If you're using UC
> inks and EEM paper on a 2100, there should be should be curves already
> available.
> 
> > 
> > Does anyone have any newbie-friendly advice?
> > 
> > If this has been addressed before, I'd be much obliged for a pointer
> > to the right thread, or any other good source.
> 
> Have you read the QTR User Guide?
> 
> It's also a good idea to state which machine type (PC or Mac), OS
> version, QTR version, printer, inkset, paper brand and type, QTR
> curves selected and any other details specific to your problem.  
> 
> > 
> > Thanks in advance. --Houston
> >
> Tom Moore
>

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.