Yahoo Groups archive

QTR-Quadtone RIP

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

Thread

QTR profile with relative rendering

QTR profile with relative rendering

2016-06-30 by info@...

I have question concerning the QTR grey profile relative table.


I have created a QTR profile for Museo silver rag on the P800, using the Epson driver. DMax is roughly L*2. Converting from a 2.2 workspace using perceptual rendering creates a perfectly linear toe from L*2 all the way to L*30. However manually targeting the black point to L*2 and converting to the QTR profile using relative rendering produces a strange lagging, source values from L*0 to L*4 are all mapped to L*2 and the visible threshold (L*3) is bumped to source value L*5. Reading the patches confirms the D Max actually produced is L*2 so I am reluctant to target a higher black value to push the source values L*1-4 out of maximum black. I am surprised that relative rendering seems to be allowing the CMM to modify ingamut colours by reducing L*3 & 4 to L*2.

Obviously I should be using Perceptual rendering, I‘m just curious to understand this behavior, usually manual black point targeting compresses the luminance scale uniformly, and relative translates the exact values.


Thank you


Eugene


Re: [QuadtoneRIP] QTR profile with relative rendering

2016-07-01 by forums@walkerblackwell.com

Don’t use the Relative table. These are perceptual profiles only (in my experience) . . .

Walker
Show quoted textHide quoted text
> On Jun 30, 2016, at 12:10 PM, info@moisdelaphoto.ca [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:
> 
> 
> 
> I have question concerning the QTR grey profile relative table.
> 
> 
> 
> I have created a QTR profile for Museo silver rag on the P800, using the Epson driver. DMax is roughly L*2. Converting from a 2.2 workspace using perceptual rendering creates a perfectly linear toe from L*2 all the way to L*30. However manually targeting the black point to L*2 and converting to the QTR profile using relative rendering produces a strange lagging, source values from L*0 to L*4 are all mapped to L*2 and the visible threshold (L*3) is bumped to source value L*5.  Reading the patches confirms the D Max actually produced is L*2 so I am reluctant to target a higher black value to push the source values L*1-4 out of maximum black.  I am surprised that relative rendering seems to be allowing the CMM to modify ingamut colours by reducing L*3 & 4 to L*2. 
> 
> Obviously I should be using Perceptual rendering, I‘m just curious to understand this behavior, usually manual black point targeting compresses the luminance scale uniformly, and relative translates the exact values.
> 
> 
> 
> Thank you
> 
> 
> 
> Eugene 
> 
> 
> 
> 
>

Re: [QuadtoneRIP] QTR profile with relative rendering

2016-07-02 by info@...

Thanks for the advice. I find the perceptual table works fine for glossy papers, it becomes more of a problem when the Dmax rises to L*18 or higher. Obviously the reproduction curve has to be compressed by 20%, I ‘m just used to targeting the threshold myself so that I can push the compression higher up the curve than most perceptual tables (including QTR).


Would I be able to achieve this if I were to make my own ink level curves and bypass the Epson driver? And would this replace the ICC profile? I’m asking this because, using the PC version I don’t see how I can configure the ICC profile in the QTR gui


Thanks

Eugene

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.