Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Qimage --> QTR workflow: 'Invalid TIFF Tags in image' at 13x19 print size

2005-09-01 by David Meddings

Thanks Stephen, and thanks for your great work on the GUI.

This particular image isn't that big - about 355 MB if memory serves 
as a 46 cm x 31 cm image at 720 ppi.

At 36 cm wide it is 24 cm high and comes in at 220 MB or something 
like that as a 720 ppi file.

I am running with 2 gigs of Corsair XMS RAM on a 2.6 GHz system. 
Photoediting is done on a RAID 0 array. I do have the system set up 
to give PS CS2 about 1.5 gigs of my RAM but I am quite sure this 
problem has occurred with and without PS running in the background.

I really do not feel as if I should be overstressing the 
capabilities of QTR asking it to handle a 720 ppi file that comes in 
at 355 megs. Surely many people here print at max resolution for 13 
x 19 format prints. 

I suppose I could hit the print button anyway...but I am rather 
reluctant as I have those big red warnings telling me some Invalid 
Tiff Tags are present etc. ....I hate to blow a sheet of HPR unless 
I know everything is ready to go.

Kind of am hoping that someone here can spot a simple thing I might 
be doing wrong, or even chime in if they have successfully fed 
images out of Qimage at 720 ppi into QTR.

Thanks for the comments,

Dave

--- In QuadtoneRIP@yahoogroups.com, "Stephen Billard" <stephen@s...> 
wrote:
> If you can hone in on the boundary condition, it will help in 
finding this
> problem. What is the length of the image? (You only mention 46 cm 
width.)
> 
> How much memory do you have on your system? I'm guessing you image 
is about a
> half gigabyte in size.
> 
> You probably don't need to sample at 720 ppi. Try 360.
> 
> Anyway, even though you can't see the thumbnail, you should be 
able to try to
> print.
> 
> -Stephen
>  www.sbillard.org/Stephen

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.