Yahoo Groups archive

QTR-Quadtone RIP

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

Thread

Custom Ink Separation Stepwedge...

Custom Ink Separation Stepwedge...

2006-03-30 by davidkeasey

Hmmm...  I guess nobody knows much about the DTP-Inkseparation.tiff
file that I'm having trouble with.  So I'll try another approach...

Are there any guidelines or instructions for creating my own custom
inkseparation stepwedge (21-step) for printing in calibration mode? 
From a quick glance at the file, it appears that a series of custom
RGB combinations are used, and that these are somehow translated in
calibration mode to separate ink channels when sent to the printer.

Any help with this is appreciated!

Thanks and regards,
Dave Keasey

RE: [QuadtoneRIP] Custom Ink Separation Stepwedge...

2006-03-30 by Tom Moore

David

If you can open the file in PS and it looks ok, then the file most likely IS
ok. The problem is more likely somewhere else.

I presume you're using a PC and QTRgui. When you try printing the
calibration page are you selecting the correct printer and printing model.
Sorry if that's a dumb question.

Tom Moore

> -----Original Message-----
> From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On
> Behalf Of davidkeasey
> Sent: Thursday, March 30, 2006 12:44 AM
> To: QuadtoneRIP@yahoogroups.com
> Subject: [QuadtoneRIP] Custom Ink Separation Stepwedge...
> 
> Hmmm...  I guess nobody knows much about the DTP-Inkseparation.tiff
> file that I'm having trouble with.  So I'll try another approach...

...

Re: Custom Ink Separation Stepwedge...

2006-03-30 by davidkeasey

Never mind....  I managed to figure it out for myself.  I'm not sure
exactly what's wrong with the stepwedge that's posted in the files,
but the one I built from scratch works just fine.

Dave Keasey

--- In QuadtoneRIP@yahoogroups.com, "davidkeasey" <davidkeasey@...> wrote:
Show quoted textHide quoted text
>
> Hmmm...  I guess nobody knows much about the DTP-Inkseparation.tiff
> file that I'm having trouble with.  So I'll try another approach...
> 
> Are there any guidelines or instructions for creating my own custom
> inkseparation stepwedge (21-step) for printing in calibration mode? 
> From a quick glance at the file, it appears that a series of custom
> RGB combinations are used, and that these are somehow translated in
> calibration mode to separate ink channels when sent to the printer.
> 
> Any help with this is appreciated!
> 
> Thanks and regards,
> Dave Keasey
>

Re: Custom Ink Separation Stepwedge...

2006-03-31 by davidkeasey

I've tried and tried, but all I get is a black piece of paper when I
print this file in calibration mode.  I've built my own file and it
prints fine in calibration mode.

The only think odd about the posted file is that the RGB values for
the printed text are inconsistent with what is used for black in other
ink-separation files.  In this one, the text color is RGB 125,0,251
while Black in other separation files is always 127,0,255

Does having a Blue Channel of anything other than 255 cause problems
in the file?

Regards,
Dave Keasey
--- In QuadtoneRIP@yahoogroups.com, "Tom Moore" <r.t.moore@...> wrote:
>
> David
> 
> If you can open the file in PS and it looks ok, then the file most
likely IS
> ok. The problem is more likely somewhere else.
> 
> I presume you're using a PC and QTRgui. When you try printing the
> calibration page are you selecting the correct printer and printing
model.
> Sorry if that's a dumb question.
> 
> Tom Moore
> 
> > -----Original Message-----
> > From: QuadtoneRIP@yahoogroups.com
[mailto:QuadtoneRIP@yahoogroups.com] On
Show quoted textHide quoted text
> > Behalf Of davidkeasey
> > Sent: Thursday, March 30, 2006 12:44 AM
> > To: QuadtoneRIP@yahoogroups.com
> > Subject: [QuadtoneRIP] Custom Ink Separation Stepwedge...
> > 
> > Hmmm...  I guess nobody knows much about the DTP-Inkseparation.tiff
> > file that I'm having trouble with.  So I'll try another approach...
> 
> ...
>

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.