Yahoo Groups archive

QTR-Quadtone RIP

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

Message

RE: [QuadtoneRIP] Re: Lightroom 1.1 and QTR

2007-06-29 by Eric Neilsen

Look in the read me section of the upgrade to 1.1. There are known issues
with certain aspects of printing. Sorry, I don't have all you email in front
of me right now, but there are some issues. I seem to remember Adobe telling
users to make sure to use the correct profile and not let printer manage
color. 

 

Eric   

 

Eric Neilsen Photography

4101 Commerce Street

Suite 9

Dallas, TX 75226

http://e.neilsen.home.att.net

http://ericneilsenphotography.com

Skype ejprinter

  _____  

From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On
Behalf Of Ernst Dinkla
Sent: Thursday, June 28, 2007 2:11 AM
To: QuadtoneRIP@yahoogroups.com
Subject: Re: [QuadtoneRIP] Re: Lightroom 1.1 and QTR

 

Carl Schofield wrote:
> Posted this reply a few hours ago by email, but didn't go thru so here is
answer via web:
> 
> Ernst,
> 
> I just tried that. Converted the image file in CS3 to the QTR create-icc
profile and then 
> printed from LR 1.1 with color management off ("managed by printer").
Print was perfect 
> so looks like something is not right with LR CM.
> 
> Carl

I got both Carl.

On BPC with Perceptual: Mike Chaney thinks that BPC 
shouldn't be used with Perceptual rendering as that 
rendering already compresses the image to the printer gamut 
including the greyscale range. Sounds logical to me. But you 
find it used everywhere as an option in software CM 
including Qimage. The Canon iPFx000 driver plug-in doesn't 
have it and people complain about that omission :-)

Is there a Chinese wall between the Photoshop and the 
Lightroom developers ?

Met vriendelijke groeten, Ernst

| Dinkla Grafische Techniek |
| www.pigment-print.com |
| ( unvollendet ) |

 



[Non-text portions of this message have been removed]

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.