My rule of thumb for color mappings, if you have to do it more than once then it belongs in a remap color action. Why do the work twice?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Ear on August 03, 2017, 11:48:34 AMFor black text builds, you can go to Global Change. Change Specific Color. Grab fill. Change to whatever you want. Run per page or complete document. I use it all the time and it is very fast and effective. The tabloids send in shit with dozens of RGB builds in the text and odd intents. Global change is often faster and more dynamic than setting up an action.
Quote from: AaronH on August 03, 2017, 11:21:15 AMQuote from: mattbeals on August 03, 2017, 11:12:17 AMUse a device link profile with ink reduction and GCR. Why would you want to change overprints, wasn't the art designed with the overprints in place?
From what I'm seeing in their PDFs the Illustrator Overprints are causing the ink limit to be over 300%. I don't visually see a difference with the two overprint modes on their files.
I'm not sure I have a GCR device link profile. At least we don't in XMF, otherwise I would do so. Is there a default GCR in acrobat/pitstop 12?
Thanks!
Quote from: Ear on August 03, 2017, 11:18:21 AMI am seeing a lot of overprint all of a sudden too. You can change prefs and uncheck "overprint black".
No, it is not okay, prepping for offset presses and was not designed that way. I am seeing 100% black fills with parts of picture showing through and text that doesn't want to KO/trap because of these settings. And I know the designer intends the black to KO or crop a picture, and not show through. Good thing I have PitStop.
Quote from: Joe on July 12, 2017, 08:09:59 PMThe PDF's are showing up as 4 color black just by placing them into InDesign. And his PDF's do the same for me. But PDF's I have here aren't doing it. Doesn't make a lot of sense. I'm still blaming it on the grayscale PDF's coming out of Word 2013.
Page created in 0.150 seconds with 17 queries.