"He who marches out of step hears another drum." ~ Ken Kesey
Print separations to a PDF file and check it.
I assume that Adobe Illy ihas something similar, but in Corel, in your print dialog, when you select Print as Separations, it should show all colors used. If you check only one of the CYMK colors, and then go to a Print Preview, it should display the guilty object(s)
Using Adobe products, I've found "empty" text boxes that had CYMK text in them, for one example. Occasionally I'll find duplicates under a part of the artwork that were CMYK colors.In Illustrator, what I do is make sure all objects and layers are unlocked, pick a spot color, choose "select same fill color", then "hide" everything that was selected, and repeat for every spot color. When I've hidden all the spot colors, I do a "select all" keystroke to find anything that was hidden or invisible, check to see if it was a necessary part of the art, then delete them, then "unhide" the spot colors previously selected.
use the separations preview in illustrator to check you have everything. By clicking the eyeball it removes the color. This way if you have two different blacks and turn of the spot black, all the spot black will become invisible and what's left has to be different color. I just go and peck on the leftovers and change them to correct colors until there is nothing left on the screen.It will make more sense when you try it!pierre
Quote from: blue moon on June 12, 2012, 12:49:27 PMuse the separations preview in illustrator to check you have everything. By clicking the eyeball it removes the color. This way if you have two different blacks and turn of the spot black, all the spot black will become invisible and what's left has to be different color. I just go and peck on the leftovers and change them to correct colors until there is nothing left on the screen.It will make more sense when you try it!pierreThat's what I do... but the problem comes when things are just too small to be seen.In this last situation what ended up being the culprit was a jpg layer that was turned OFF and yet still caused the issue. Last ditch effort we deleted that layer and TADA!