Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] Linux and QuadToneRip - Any Howto Available????

2003-09-25 by Roy Harrington

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, Justin Florentine 
<justin@b...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Carl, what paper/black ink combo did you use for these curves?  I've got 
> the 2200/UT inkset with photo black, and it doesn't seem to be working 
> well on semi-gloss paper.  I'll try again with EEM, but I'm not sure 
> which black ink to get for that.
> 
> I've also had problems with the paper cutter on my 2200 with QTR.  It 
> works fine when I print from windows through the Epson driver.  It just 
> won't cut when I print from QTR.
> 
> 

Justin,

I don't know if this will solve your curve issues but ...
I think I've run across the cause of some mac/linux differences.  I've been
tweaking the various dot size weightings and it looks like I missed one
for the Linux source distribution.  This is the current situation:

Under the RasterSrc folder in the file print-escp2-data.c there's the section
for the 2200:

/***************************************************************\
*                                                               *
*            ULTRACHROME (2100/2200, 7600, 9600)                *
*                                                               *
\***************************************************************/

static const stp_simple_dither_range_t standard_4pl_pigment_dither_ranges[] =
{
  { 0.661, 0x1, 0, 2 },
  { 1.00,  0x2, 0, 3 }
};

DECLARE_INK(standard_4pl_pigment, 1.0);

------------

Well the 0.661 should be changed to 0.561 -- I did this for the Mac but inadvertently
missed moving the change into the Linux source. This should only effect printing
at 1440x720.


As far as the cutter is concerned I not sure that gimp-print supports that.

Roy

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.