PDF Workflow Problems

[pcmodem]

I hear of people saying PDF workflows are 98 to 99 percent without change. I am curious as to what can/does change in the 1 to 2 percent.

I do see PDF as the way of the future. I just want to make sure the security is there.

Thanks in advance.

 

[John Clifford]

While PDF can be wonderful. There are a lot of things that can go wrong if a PDF is not created properly. If you're using a level 2 or early version of Level 3 Postscript RIP, then you can run into issues with transparency flattening. If you're just purchasing a workflow/RIP then you'll want to make sure that it's APPE (Adobe PDF Print Engine) RIP and those won't be issues.

Most of the other issues have to do with client supplied PDFs and they're mostly the same types of issues that you have with client supplied application files.

I'll be interested to see what other issues people come up with.

 

[gig0]

What changes in a PDF workflow is productivity. Coming from a Brisque standpoint (ROOM workflow) and migrating to a Prinergy PDF workflow, I can attest to that. Granted that 2% error ratio is rare, but the overall productivity makes up for that, easily.

One of the errors I can think of ATM is type not getting rendered on plates at 2400dpi. The low res 300 dpi virtual proof shows otherwise. However, it's very rare (and might have something to do with obscure fonts) but that issue has been forwarded to Adobe last year and may have already been resolved.

 

[pcmodem]

gig0,

I don't quite follow what you are saying with the rendering on plates at 2400dpi. Do you mean it doesn't match the screen view? Please elaborate.

Thanks,
Brian

 

[pcmodem]

If you're just purchasing a workflow/RIP then you'll want to make sure that it's APPE (Adobe PDF Print Engine) RIP and those won't be issues.

John,

What would happen if I didn't go with an Adobe PDF Print Engine (APPE) and instead went with Odystar from Esko?

Thanks,
Brian Cupp

 

[gig0]

gig0,

I don't quite follow what you are saying with the rendering on plates at 2400dpi. Do you mean it doesn't match the screen view? Please elaborate.

Thanks,
Brian

Yes. In Prinergy theres a separate app called VPS (Virtual Soft Proof) which displays the files/impositions as rendered images using whatever screening you normally use. Displaying virtual proofs for all jobs rendered at 2400 is not as productive (for obvious reasons) than 300 dpi. Last year, there was an issue that was forwarded to Adobe because everything looked ok at 300 dpi but when you made the plates, type dropped off. The funny thing is, if you made a VPS at 2400 dpi, it showed the type dropping off as well.

 

[Al Ferrari]

And did Adobe respond?

Al

 

[gig0]

My mistake. The issue was forwarded to Kodak, not Adobe, and had to do with a subset non-adobe font.

Theres a thread about it on the GUA forums, although haven't heard much about it since last year and we've only experienced it once.

 

[John Clifford]

John,

What would happen if I didn't go with an Adobe PDF Print Engine (APPE) and instead went with Odystar from Esko?

Thanks,
Brian Cupp

I believe that Odystar IS an APPE RIP. Check with Esko/Artworks. They are VERY good at implementing PDF workflows as they're the ones who created Pitstop, which is the most important tool you can have.

 

[zoran]

I believe that Odystar IS an APPE RIP. Check with Esko/Artworks. They are VERY good at implementing PDF workflows as they're the ones who created Pitstop, which is the most important tool you can have.

As far as I know, Odystar is not APPE rip. They use their own PDF libraries, not Adobe's.

 

[John Clifford]

As far as I know, Odystar is not APPE rip. They use their own PDF libraries, not Adobe's.

Thanks Zoran, I stand corrected. Actually Artworks support of PDF transparency actually predates APPE. However, it appears to be an advanced RIP that is fully PDF compliant and I'm sure would work out for PCModem.