Yahoo Groups archive

QTR-Quadtone RIP

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

Thread

XP15000

XP15000

2019-06-13 by arnnadf@...

Haven't printed for over a year and thinking about replacing my aged Epson 2200. I hadn't realized Epson is selling a dye printer but with negative b/w results. Didn't see it on QuadTone's printer list and would appreciate knowing group;s opinions on the printer.

Thanks,

Arnold

Re: [QuadtoneRIP] XP15000

2019-06-13 by forums@walkerblackwell.com

Working on some base curves for the DYE and for possible forthcoming Piezo on this with a test driver. But it’s been put on hold for awhile due to a lot of other pressing needs . . . ink coverage is double due to doubled nozzles (Roy can explain the details). I’ve been waiting on him to limit the total dot coverage by 50% but in the interim have had no time just to do this in the curve(s) I’m making.

Tldr: On the horizon. May take some time. It’s a really really nice printer (and cheap!).

-Walker


> On Jun 12, 2019, at 8:20 PM, arnnadf@... [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:
> 
> 
> Haven't printed for over a year and thinking about replacing my aged Epson 2200. I hadn't realized Epson is selling a dye printer but with negative b/w results. Didn't see it on QuadTone's printer list and would appreciate knowing group;s opinions on the printer.
> 
> Thanks,
> 
> Arnold
> 
> 
> 



[Non-text portions of this message have been removed]

Re: XP15000

2019-06-13 by roy@...

I've got an Epson XP15000 printer that I've been able to test with. Its a bit
different than previous printers so its not exactly the latest reincarnation of
any previous model. While similar to 1430 in some respects - 6-ink Claria.
It uses different inks -- the usual CMYK but then instead of LC and LM it has
Gray (LK) and Red(R). Seems like this ought to make smoother B&Ws since
it has the LK but then toning will be done with darker color inks. The blacks
are quite cold toned rather than warm toned like the UltraChrome inks.

Anyway, I have a version of QTR driver that works with this printer, but since Epson
has changed their communication protocols, there's more of a trial & error
guess method to making it work. All is mostly just fine but strangely the dot
sizes from the inkjets are unusual. It has the advertised 1.5pl drop but the
next larger drop is much larger (about 6pl) rather than about 2.5 to 3.5pl that
other printers have. This makes it possible to output much larger amounts
of ink. All printers have different sizes but this seems to be an outlier.
But QTR driver has always had INK LIMIT controls so this is easy to fine tune in curve
for any printer. (the .quad files have ink values that just need to be smaller).
This has nothing to do with number of jets.
I guess there's one potential issue here -- the 1.5 to 6pl jump might be a little
more likely to be visible. I don't believe this is a problem but who knows in rare cases.

Roy


Re: [QuadtoneRIP] Re: XP15000

2019-06-13 by forums@walkerblackwell.com

> On Jun 13, 2019, at 5:24 PM, roy@... [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:
> 
> the 1.5 to 6pl jump might be a little
> more likely to be visible.

This 1.5-6 jump actually caused weird reversals in 3/4 tones for me and ended up throwing me such a curve-ball for linearization that I scrapped it until I could get some solid time into it (where did that go I have no idea).

I ended up re-building Gutenprint around it, limiting to only smallest dot size and this worked . . .

-Walker




[Non-text portions of this message have been removed]

Re: XP15000

2019-06-13 by roy@...

I tweaked the dot sizes for the 15000 a bit recently. This makes the
transition smoother. Hopefully this will fix the issue.

Roy

Re: [QuadtoneRIP] Re: XP15000

2019-06-13 by Arnold Frank

Thanks for your input. Hopefully I can resurrect my 2200 but will certainly consider the XP15000. Also want to check if it can use non Epson papers.
Regards,
Arnold
Show quoted textHide quoted text
On Thu, Jun 13, 2019 at 2:25 PM roy@... [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:

I've got an Epson XP15000 printer that I've been able to test with. Its a bit

different than previous printers so its not exactly the latest reincarnation of
any previous model. While similar to 1430 in some respects - 6-ink Claria.
It uses different inks -- the usual CMYK but then instead of LC and LM it has
Gray (LK) and Red(R). Seems like this ought to make smoother B&;Ws since
it has the LK but then toning will be done with darker color inks. The blacks
are quite cold toned rather than warm toned like the UltraChrome inks.

Anyway, I have a version of QTR driver that works with this printer, but since Epson
has changed their communication protocols, there's more of a trial & error
guess method to making it work. All is mostly just fine but strangely the dot
sizes from the inkjets are unusual. It has the advertised 1.5pl drop but the
next larger drop is much larger (about 6pl) rather than about 2.5 to 3.5pl that
other printers have. This makes it possible to output much larger amounts
of ink. All printers have different sizes but this seems to be an outlier.
But QTR driver has always had INK LIMIT controls so this is easy to fine tune in curve
for any printer. (the .quad files have ink values that just need to be smaller).
This has nothing to do with number of jets.
I guess there's one potential issue here -- the 1.5 to 6pl jump might be a little
more likely to be visible. I don't believe this is a problem but who knows in rare cases.

Roy


Re: [QuadtoneRIP] Re: XP15000

2019-06-13 by forums@walkerblackwell.com

Will retest once I have slightly less stacked plate. Thanks!

-Walker


> On Jun 13, 2019, at 5:53 PM, roy@... [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:
> 
> I tweaked the dot sizes for the 15000 a bit recently.  This makes the
> 
> transition smoother.  Hopefully this will fix the issue.
> 
> Roy
> 
> 



[Non-text portions of this message have been removed]

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.