Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: Banding (lines) using QTR with 1430

2012-11-12 by bobtrebor194

Hi Michael,
it seems not every 1400 has this issue. I had problems with these very thin lines and i didn´t get it under control. I bought my 1400 at Amazon. I went to an authorized Epson Dealer & Service Partner and told him my problem. Of course i didn´t tell him about QTR. I also didn´t tell about bw. I just said i have these lines printing my photos.
He took my 1400 and send it to Epson and he told me it will take about three weeks for repair(?) or get a new one. And the surprise: Four(!!!) days later i got a call:"Your new printer is ready to go...".
The service partner told me, that they called Epson and that they send the printer. Epson said ok, and send parallel a new one to the service partner.
Thats really quick and Epson send the new one without seeing my printer.

I dont have these hard problems with the lines anymore. And if i have some lines, i just set up the inklimit. In some hard cases i re-edit the photo to a little bit darker.

But with the first printer i was going mad. I was dreaming about these lines. ;) Horrible...


So, if you have warranty and dont get the lines under control, try to get a new printer. Maybe helps... 

Greetings from Cologne/Germany
Robert

--- In QuadtoneRIP@yahoogroups.com, "bakerstrten1" <bakerstrt@...> wrote:
>
> Hi
> 
> Can anyone diagnose my problem?  Printing on my Epson 1430 using QTR with MIS EB 6 inks results in lines at either end (landscape) of the print.  It appears to me as if the printer has missed printing on some of it's passes.  The problem occurs regardless of whether I use the MIS curve or either of the two 'straight' QTR curves which come with the program.  
> I printed the same file with my R800 on QTR without this problem.  Can anyone suggest what is causing the problem?
> Thanks
> Michael
>

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.