On 10/29/04 8:20 AM, "Tacit" wrote:
Do you use an inkjet proof for your color proof as well?
Yes, an Epson 9600, but our Fuji FinalProofs are much much better. 🙂
If you’re using a Harlequin RIP, you should be able to take a varnish plate from a different page (or document) and overlay it on the 4/C inside the RIP, so it should still be possible to generate a composite digital proof that includes the varnish.
Well, my RIP is the Agfa Apogee PDFRip, but this is possible in my workflow, too. That’s a great idea. I wish I’d thought of it. 😉
One of my biggest gripes about Photoshop is that if you create a spot-color document for output from another app, you’re forced to save it as DCS; Photoshop can’t create a DeviceN EPS with the spot color channels included. There’s a third-party app, DCS Merger, that’ll take a Photoshop DCS and produce
a DeviceN EPS, but the fact that Photoshop can’t do this itself is kind of silly.
I wholeheartedly agree. It is very silly. Sometimes I wonder if it was an intentional "limitation" by Adobe, given the fact that InDesign isn’t hindered by this problem. "Want spot colors in Photoshop?", says Adobe, "Use InDesign for output–no problem!" Fine and dandy, but I’m in prepress–I don’t get to make that decision.
The OP would likely be best off using Illustrator to do the varnish or, if the varnish is too complex, creating it in Photoshop, then saving it as a grayscale
TIFF and colorizing it in Quark. (This is most often what I’ll do if for some reason I can’t use Illustrator; in Quark, the TIFF can be forced to overprint and placed on the same Quark page with the 4/C, if necessary.)
Be careful if you’re in Quark6 on Mac OSX. I know the marketing material claims that Quark can now (finally) handle colorized TIFFs, but I’m on the receiving end of all sorts of files. I can tell you that Quark 6 cannot handle colorized TIFFs yet, and the Quark 5 xtensions that I used to use to get around this ridiculous limitation no longer work in Q6. Yes, you might get lucky and your colorized TIFF will work (printing DeviceN), but if you look closely at the rest of the document (after PDFing and/or RIPping) you may notice type changing colors and other strange results. Printing separations might work, but I’d rather not do that, if it can be avoided.
If I’m missing some xtensions you know of that fix Quark’s nasty little bug (that they’ll probably never fix) please LET ME KNOW!! 🙂
I can also say that I cringe every time I receive a file from a customer that has the varnish plates in a separate document. >Almost every single time that happens, the varnish is off.
That’s why I never allow my clients to make their own varnish plates. 😉
Oh, I wish had that authority. I’d setup all my own dieline files, too! Sometimes it’s much easier to start from scratch than fix what I receive.
But then, do you eat the cost, or piss off the customer and charge him/her? Some customers can be…volatile, to put it nicely. How do you deal with that?
Including the varnish plate/s in the document that will rip is the only way I know to preview the results prior to any output. If you know another way, please enlighten me, and I’ll be forever in your debt.
The PolkaDots workflow does this easily (PolkaDots is a ROOM-based workflow management system that wraps around a Harlequin RIP core), but I think you can do it directly in a Harlequin RIP if that’s what your using to drive your proofer.
I’m not familiar with PolkaDots. I’ll probably research this workflow in the near future, but I’m quite happy with Apogee. Not so much Agfa, as their customer support is horrible with a capital "H", but the workflow is very nice. Once you get it set up the way you want it (Agfa doesn’t really help you do this–in fact, they seem to try to make it more difficult), it can be extremely fast and efficient.
Thanks for the reply! Happy Friday!
Tim