Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: [QuadtoneRIP] Re: QTR not printing - "Filter Failed"

2015-05-28 by Roy Harrington

I guess I need to try and sort out what's what here.

There are multiple issues here and I think we're starting to mix them up.

1) There's a "super" version of some resolutions. These take extra passes of the inkjet head
and often do a little better for banding issues. On the Pro printers this is a in-the-printer feature.
When Epson came out with 7890/7900/9890/9900 there are new head designs and apparently
they no longer supported/needed this "super" version. None of this is documented of course so I
didn't know this at first. I removed this mode for new printers but apparently missed the 9900.
So Gary's 9900 still shows this option on 2.7.5 and the printer just does not work properly for it.
This is a hardware issue -- not something depending on OS or QTR driver version.
2880 dpi and 1440 dpi should both work but I do recommend 2880 dpi because it gives
better results and the printer is quite fast anyway.

2) The other issue is less well defined. A number of people have run into the "Unable to set
resolution" message. This is a very strange, very intermittent problem. I'm not sure what OSX
this started in, but it's caused by the default value for resolution not being set. You may see it on
the QTR driver page but it does not get thru to QTR driver itself. It's a printer Preset issue as
far as I can tell. Changing it, saving it in a Preset usually solves the issue. It happens with
different printers, different OSX's and different QTR's so you can't really generalize it.
I'm trying some other ideas to catch this and work around this in QTR driver -- we'll see.

Roy


On Thu, May 28, 2015 at 10:29 AM, gnickzone@sympatico.ca [QuadtoneRIP] <QuadtoneRIP@yahoogroups.com> wrote:


Hi Richard,

Thanks for the reply, much appreciated. About an hour ago I had an email reply from another member, and I must admit to using my reply to that email here as well, with a few additions. Only because I wrote everything I would have written in my reply to you RIchard.

Roy and I have been working on this for more than a week and in his last email he suggested that I use only 2880. I had been trying to print with 1440Super, and once I tried 2880 it worked, but still not with the other resolutions. Roy also mentioned he had heard that some of the latest OS/printer combos were not able to use any res except 2880. He also suggested that I do a “Printer Reset”, which of course deletes ALL printers, presets and custom paper sizes. Since I am not about to go that far at this time, I will work with the 2880 res only and be happy that I have QTR back online. There is obviously a glitch somewhere in the OS that’s causing this, but I cannot seem to find it. I have recently done a fresh install of Mavericks on an external drive and I’ll test QTR there just to verify that it does work in all resolutions. If so then the problem is with my main drive(Mac HD). I always take the Upgrade route when it comes to installing a new OS and perhaps that’s part of the problem. I have a lot of apps and it would take a long time to install everything again on a fresh OS installation. At some point I might have to do that, but I’m rather busy now. I will soon be installing Yosemete on an external for testing, so that will tell me a lot about QTR as well. About a month ago I encountered a very unusual problem with my main drive and the BootClones also(NVRAM issue I believe), so I brought a clone drive from the Mac Pro at home and cloned over to the Mac Pro here at work. Everything has been working well, except for QTR. As it turned out I had been in touch with Roy about a year ago with this same issue and we couldn't find a fix then. However, I haven't been using QTR for a while and didn't remember that issue or how to overcome it(2880 res only).

Thanks again Richard,

Gary




--

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.