QTR-Quadtone RIP

You completely miss the point!

I'm going through the calibration procedure to understand what's going on and questions come up about the process that butts up against my attempt to understand the process.

First, there is no 'inkseparation.psd' file anywhere in my install of QTR.  I ask why.  Did it not download? Is the file stored away someway somewhere else since no folder is given for this folder?

The steps for printing the calibration sheet out is no where close to being user friendly, after making the assumption that the file is 'inkseparation.tif' in the BIN folder.

And, when the process for setting up the K, LK, & LLK is studied and make sense, there's nothing that addresses the M/LM or C/LC pairings or the Y.  After all QTR isn't just for b/w printing, right?  If it was only for b/w printing there would be no need for using a color example. Right?

The bottom line is that when you're talking to the choir, you can make certain assumptions, also to your detriment, that there is a level of knowledge already in place.  This works fine if you never want no new customers.  

There are many either new and/or less experienced technically who use this process and the speciality inks that are supported.  We want to learn and contribute to the quest for making digital printing more than just hitting 'PRINT'.

So, rather than taking me to task, provide we 'newbies' to QTR with the following:

Place the appropriate 'inkseparation.psd' up on the FILE section or tell me where to download it from or tell me what file in the current version is the right one to use and where to find it.

If there's not going to be a new version of the calibration procedure, then I'll be glad to put one together for review.

Update the User Manual or get rid of it and just say 'You're on your own'. At least I'd know where I stood.

Mike


--- In QuadtoneRIP@yahoogroups.com, Walker Blackwell <forums@...> wrote:
>
> Go try StudioPrint. You get to spend $2500 dollars for the rip replacement dongles cost 120 dollars, you can't do any toner splits besides 1-1 (or physical mixing of ink), and major updates come once every two or three years, cost 500 bucks, and break past workflows and hardware compatibility. Also, the documentation doesn't exist for artists (aka buiding custom environments for thick rag-type paper) and the dithers over-ink at 2880dpi. And Ergosoft rarely if ever replies to forum posts (I should know as I'm the moderator of that forum.) They don't even let you call them for tech questions anymore!  One thing they do is iterative linearization though. :-)
> 
> $50 dollars and all future updates for a semi-open source software (QTR) that really works much better than many competing closed source solutions is really nothing to complain about. Also, there are multiple user guides out there and many of them are still valid even if they are from an older version. And .tifs are needed because .psds are not compatible with other imaging software.
> 
> The problem here is a bit of an over-expectation around service I think.
> 
> all the best,
> Walker
> 
> 
> On Jul 19, 2010, at 10:16 PM, mbrouphy wrote:
> 
> > Okay, I've been an on and off user of QTR for a while.  Now that I'm back for another round I find that there are several old things still hanging around.
> > 
> > -- The Calibration paper still refers to version 2.5
> > -- The User Guide still carries Version 2.2, 26April2005 date on it.
> > -- There's no 'inkseparation.psd' file but 'inkseparation.tif' file.
> > 
> > 
> > Now no offense but this is a bit ridiculous!  I shouldn't have to come here to this forum to find out stuff that should be posted on the website, like updates to an existing version.
> > 
> > I put my money down some time ago with the implied deal that the price included all future updates, too.  The least you can do is bring everything up to date at the same time as the software.
> > 
> > Thanks, Mike
> > New Orleans, LA
> > 
> 
> Walker Blackwell
> 802.821.4451
> www.walkerblackwell.com
> aim: greendirtblues
> wblackwell@...
> 
> 
> 
> [Non-text portions of this message have been removed]
>