Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Lightroom 1.1 and QTR

2007-07-01 by Carl Schofield

Walker,

I think Roy will have to address that question, but I thought that QTR was relying on 
Photoshop to handle the front end icc conversion.  I didn't realize that LR was passing the 
CM buck, but what you say certainly helps explain the problem.

Thanks,
Carl

--- In QuadtoneRIP@...m, Walker Blackwell <wblackwell@...> wrote:
>
> I believe I just got to the bottom of it. Photoshop (it seems) does  
> all of the grunt-work when it comes to pure color management. That's  
> because it's been around since before OSs had any color management.  
> So when you print a big'ol image it's actually doing a hard- 
> conversion of that file to the out-put profile and then sending that  
> data along to the print driver. (Thus all the time it takes to  
> print.) All the print driver has to do is send the data to the Printer.
> 
> Lightroom, on the other hand, tags the image with the profile and  
> lets the print driver handle the conversion. I think that is where  
> it's getting sticky. This explains why I was having such a hard time  
> with the old Spro9600 drivers when printing color. They just couldn't  
> handle the profile conversion themselves. The driver expected a  
> converted file.]
> 
> It also explains the slight lag between finishing a file rip in  
> Lightroom and seeing it come up in the print queue.
> 
> Can QTR handle ICC profile conversions? And is it v4 compliant? Most  
> likely more and more applications will come out soon that will  
> require OS and Driver color management instead of doing all the work  
> themselves. It makes everything faster and more scaleable.
> 
> The nice thing is the Adobe CMM is open source and available to use  
> for such a thing as driver-based ICC conversions.
> 
> take care, Walker
>

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.