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-07-01 by Walker Blackwell

After reading your post, Ernst, I agree with you somewhat. I believe  
the input/output world is way too varied to really be able to use LR  
as only a path and not a full CMM. But the only reason why I'm  
interested in it is for four reasons. I can run it on OS X (my OS of  
choice); I don't have to sit there for days waiting for prints to  
spool; I can tile images; I can keep print jobs and portfolios  
organized permenantly (and with Keywords). That last one is the key  
when you have 3.2 tbs of photographs hanging around.

The reason why it's fast is because it relies on tagging. But that's  
its flaw as well. I agree. So maybe the Adobe people need to get  
there act together and make there own conversion quicker. Maybe they  
can talk with Epson and the Gimp driver community and get file  
segment policy down so we don't have to sit there waiting for the  
image to completely spool before we print. We are still in the dark- 
ages with PS and printing. As a StudioPrint user I can never go back  
to working w/ Photoshop for spooling. Lightroom and QTR offer a great  
alternative. I would say they are better than StudioPrint as far as  
speed and organization are concerned. Once we can use BPC with QTR  
from Lightroom and the 10,000 pixel limit is lifted it's all rocking  
and rolling as far as I'm concerned.

  I also agree with you about the complexity of the hand-off from x  
application and x printer driver. Lightroom IS color managed in that  
it gives it gives its intent to the print driver + a background task  
that I've noticed kick into high-gear in the system process tree  
after hitting print. It's just not compatible with many drivers out  
there and they aren't with it. It's a pretty bone-headed move by the  
the lightroom folks I'd say.

take care, W

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.