Results 1 to 7 of 7

Thread: Spot-on won't work with PDF but does with EPS

  1. #1
    Join Date
    Jun 2010
    Posts
    1

    Default Spot-on won't work with PDF but does with EPS

    Had a customer with Canon C7000vp, A3100, CWS4. Tried to change a text color in an InDesign-created PDF file using Spot-On, but color didn't change. Verified with Pitstop Object Inspector that the color was being called out in the file as Pantone 533 C and that the replacement spot color on the Fiery had exactly same name, number and suffix. Output profile was correct, the Spot Color check box in Advanced Color setup was checked. Customer was doing everything they were supposed to do but they could not get this spot color to change.

    Customer changed to EPS output in InDesign. Imported the EPS file to the RIP and voila, color changed as desired.

    So the exact same job, from InDesign, has Spot-On fail with PDF file output but work just fine with an EPS. Any ideas?

  2. #2
    Join Date
    May 2009
    Location
    Minneapolis, MN
    Posts
    343

    Default

    Did you import the PDF file in Command WorkStation or did you print to the Fiery from Acrobat?

    Bob

  3. #3
    adam1991 is offline Fiery Forum Expert Contributor adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful
    Join Date
    Feb 2010
    Posts
    1,029

    Default

    Quote Originally Posted by sbparker
    Had a customer with Canon C7000vp, A3100, CWS4. Tried to change a text color in an InDesign-created PDF file using Spot-On, but color didn't change. Verified with Pitstop Object Inspector that the color was being called out in the file as Pantone 533 C
    Did you look at the PDF outside the Fiery system prior to bringing it in, or did you preview/edit the job once it was inside the Fiery system?

    It's possible that the InD-created PDF has what you need, but once you've put it inside the Fiery it doesn't. Always check the job that's inside the Fiery to know what's current about the job.

  4. #4
    Steve0 is offline Fiery Forum Expert Contributor Steve0 is on a distinguished path
    Join Date
    Aug 2009
    Posts
    249

    Default

    Adam, just so I understand: Are you saying that a PANTONE 533 C in the InDesign document may not still be called PANTONE 533 C in the PDF document saved in InDesign?

    Does this mean that there is a Distiller setting that could fix this situation?

    Steve

  5. #5
    thistlegorm is offline Fiery Forum Expert Contributor thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status thistlegorm has achieved rock star status
    Join Date
    Jul 2009
    Location
    London UK
    Posts
    814

    Default

    Was the original indesign file exported as a flattened pdf ? I wonder whether this is a layer problem if the original file was exported to pdf it would have the Spot Colour - if it was, then File -> Print & the pdf flattened as a result the Spot Colour would have been converted to CMYK which would produce the symptons you describe.

    A quick & easy way to see is on the Fiery select the properties of the job & in job Notes find the Postflight pulldown & select colour coded pages, OK then Process & Hold file, on the ripped file right click & select imageviewer - navigate through to the relevant page & look at your text if it is coloured in Orange then the text has been ripped as a Spot Colour if it comes out Blue then the Spot Colour was converted to CMYK. This might give you a way in to start fault finding.

  6. #6
    adam1991 is offline Fiery Forum Expert Contributor adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful adam1991 has proven very helpful
    Join Date
    Feb 2010
    Posts
    1,029

    Default

    Quote Originally Posted by Steve0
    Adam, just so I understand: Are you saying that a PANTONE 533 C in the InDesign document may not still be called PANTONE 533 C in the PDF document saved in InDesign?

    Does this mean that there is a Distiller setting that could fix this situation?

    Steve
    That is absolutely correct.

    There are many, many paths the document can take between being a native InD document and sitting on the Fiery as print-ready PDL. Most of those paths are incorrect.

    You must be very careful and precise about how you make the PDL (be that Postscript or PDF) and how that PDL ultimately gets placed into the Fiery for printing.

    As I said, the only way to know where the problem lies is to look at the print job in its native form as it sits on the Fiery. For me, that means previewing the job in Acrobat and using Pitstop to see some of the details.

    You can also use the Fiery preflight or postflight features, if available, to tell you some things you may want to know.

  7. #7
    Join Date
    Jul 2010
    Posts
    8

    Default problem is output profile

    I am going to bet that your problem is the output profiles don't match.

    If you look in the expert color settings/ output profiles, I will bet you that the setting for "use paper settings" is turned on. If you turn this off it will correct your problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts