Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: [QuadtoneRIP] Tiff Error Message

2008-01-18 by Roy Harrington

The issue is the compression -- use LZW only.
Roy

On Jan 18, 2008 10:52 AM, William Presho <wpresho@...> wrote:

> If I take the TIFF file created in CS3 and open it in Lightroom and then
> export the file as a TIFF from Lightroom (with no work done, only open
> and export) then QTR doesn't have a problem with it. So I am guessing
> that one of the settings you are talking about is the problem will have
> to experiment some more. Thanks for the info,
>
> Mike Finley wrote:
> > Possible causes are things in TIFFs that QTR doesn't like. I can't
> > remember what these are, but given that this should be a final print
> > file, try with:
> >
> > image flattened, no layers or alpha channels
> > uncompressed (or at least avoid ZIP compression)
> > I can't remember what colour channel interleaving  QTR wants - but you
> > could save as greyscale anyway
> > don't allow any extra embedded things that CS3 allows (I don't have CS3
> > so don't know)
> >
> > - basically strip back to a more basic TIFF and then if you want add
> > things back in until it breaks again!
> >
> > hope that helps
> >
> > William Presho wrote:
> >
> >> Hi
> >> I am using PS CS3 and QuadToneRIP version 2.5.2.1. The problem I am
> >> having is when I bring the image into Quad it gives me the following
> >> error "TIFF format not supported". Can anyone tell me what the problem
> >> is. I am using Adobe RGB 1998 in CS3.
> >>
> > ----
> > mike finley
> > fine art photography and website construction
> > http://www.mikefinley.co.uk
> > http://www.roguegenecollective.com/Mike_Finley.html
> > http://www.efikim.co.uk
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
>
>
>
> Yahoo! Groups Links
>
>
>
>


[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.