Re: Autoflow, iQueue, etc.
Re: Autoflow, iQueue, etc.
- Subject: Re: Autoflow, iQueue, etc.
- From: Glenn Kowalski <email@hidden>
- Date: Sun, 4 Feb 2001 10:41:42 -0500
>Among the automated color conversion servers, such as ICC AutoFlow,
iQueue, etc, is any of them configurable to do the following: ?
- watch a hotfolder for PDFs to arrive
- colormanage the PDF to a target device (ie source swop, target
tektronix)
- print the PDF to the target device (in postscript)
- delete the intermediate (colormanaged) PDF.
ICC AutoFlow already did all of this except the PDF part, so the new version
should qualify, though only on Windows at the moment...
C. David Tobie
Design Cooperative
email@hidden
I don't know if Autoflow Network for the PC will actually print the
file, but for the Mac it won't. The user has to drop the file on a
desktop printer, which is annoying and defeats the purpose of the hot
folders. If the user has to walk over to that computer to drop the
file on a desktop printer, then they may as well be doing the
conversion too. So Autoflow Desktop ($900 cheaper) will do in many
cases. (One other benefit to Autoflow Network that should be
mentioned is that it doesn't hog all MacOS resources, so it is
possible to color process and print at the same time) I've tried to
set up an Applescript to do the printing after processing is done,
but with only limited success--I get Applescript errors occasionally.
Does anyone have a foolproof Applescript for this? I love Autoflow,
but the simple ability for it to print would be a godsend.
Where can I find some info on iQueue? I think I looked at it once
before but dismissed it for some reason that I don't remember. But
now I can't find it.
Speaking of Autoflow, I had some problems the other day. I set it up
for an Epson 3000, processing QuarkXpress postscript files. The user
processes the file using Autoflow Desktop and selects either the
Epson Glossy or Epson Inkjet paper set, both use corresponding
profiles, a relative colorimetric rendering, and no proofer setup.
Either set seemed to work fine, processing the postscript and saving
a new file. However, the postscript file converted using the Glossy
paper profile kept choking the Epson RIP (don't laugh) while the file
converted using the Inkjet paper profile worked just fine. My
conclusion is that there is something wrong with the Glossy profile,
although I can't figure out what after examining it in ColorThink,
using it in Photoshop, etc.
The Epson RIP seems to be very sensitive when taking QuarkXpress
postscript files. It doesn't always like Photoshop EPS
files--especially if they are saved with binary encoding. Anyone else
notice this? I also wonder if the inability to accept the file
processed with the Glossy profile is a function of this sensitivity.
I was able to substitute another profile created on Glossy paper from
my own 3000 as a temporary solution and it worked fine, so I guess
I'm back to it being a bad profile.
--
Glenn Kowalski
Macintosh Systems Consultant
Studio 405
www.studio405.com