Prepressforums.com - DCS 2.0 and Illustrator art files not trapping

T · #1 (**permalink**) 03-10-2005, 10:39 AM

Here's the problem... The client has a scan (DCS 2.0, background is the PMS) placed in a Quark file. Sounds OK so far. They placed their Illustrator art in the Quark file on top of the scan (same PMS color) and also, typed some copy in the Quark file on top of the scan (same PMS, again) Seems normal to me? When the file is ripped, the Vector art and the copy typed in Quark don't trap to the CT? If the scan is plain old 4/C process, there's no problem trapping. Only when the scan is a DCS 2.0 does it refuse to trap?? Anybody?? :roll:

JoePixel · #2 (**permalink**) 03-10-2005, 10:59 AM

If I'm reading this correctly, it's a one color PMS, right?

If they are all the same PMS color, then you don't need to trap.

T · #3 (**permalink**) 03-13-2005, 10:20 AM

It's a DCS 2.0 photshop file. There is a womans face and shoulders (4/C) and the background is the PMS. The vector art and copy typed in Quark (same PMS as the background of the DCS 2.0) are actually on the top of her shoulders (4/C area), hence the need for trap. I think the scitex sees the DCS 2.0 file with the same PMS and won't trap it. If the vector art or copys PMS is changed it traps. Or if the DCS 2.0 PMS is different than the vector art it traps. But when the PMS is the same, the scitex won't trap to the vector art to the CT's 4/C area?? go figure?

rcmayor · #4 (**permalink**) 03-13-2005, 11:09 AM

You can do what you mentioned, run it as two different PMS colors. Let the brisque trap the files. Then copy the .job folder to your mac and edit the LW file to be only one spot color. Dont forget to edit the trap color also though. It may be a different swatch in Presstouch.

DCurry · #5 (**permalink**) 03-13-2005, 12:51 PM

Or, you can use the Decisions to add a trap between the 2 desired colors - just make sure you first define a new swatch that is the trap color.

T · #6 (**permalink**) 03-14-2005, 03:14 AM

I use Presstouch for this workaround, but I was wondering if anybody else has run into this issue and solved the problem, or am I the only one. It would be nice not to take the extra steps, but heck, I work in prepress. Work is a workaround.

DCurry · #7 (**permalink**) 03-14-2005, 05:17 AM

Have you tried the "Use CT Data" option in FAF? This takes forever and sometimes does weird stuff, but sometimes it works great.

T · #8 (**permalink**) 03-14-2005, 05:24 AM

I'll try, but I hate using that option. The traps always go in different directions.

rcmayor · #9 (**permalink**) 03-14-2005, 04:23 PM

That is what presstouch is for, to fix something without having to jack with all your normal workflow settings to get a special file to run.

JoePixel · #10 (**permalink**) 03-14-2005, 04:34 PM

T,

My apologies for the misunderstanding, I understand it much clearer now.

Have you tried changing the Transparent sep values in the Full Auto Frames?
Change the opacity in the PMS separation when ripping also may work.

I use the Ct data quite often as mentioned above, but I try to make that trap smaller than my usual trap. Those weird traps work great but don't look good if the trap is too big.

Sometimes I have to rip it a dozen times and FAF the file a dozen different ways to get the results, but mess with those FAF settings and something is bound to happen in the way you want.