Scope PDF Workflow

[Oppah]

I have a workflow that tends to address the needs and issuse that our shop has using Esko's product line. However, the powers that be are being told that the Scope PDF workflow has worked out issues w/ AI CS2 effects and other issues. They've asked me to investigate this and hearing what you all have to say is a part of that.

I my testing I've found issues w/ the speed and size of AI CS2 files when saved w/ PDF Compatibility (a must) for Scope PDF.

Further, issues w/ the Scope PDF workflow generating hundreds of ct's and slicing up a file for no apparent reason.

Additionally, issues w/ layers being lost when the Scope PDF is opened in PackEdge. (even w/ keeps layers when possible is checked in the ticket)

Any advise - Suggestions - Similar Problems - Solutions - Work Arounds

Thanks for the Input

[shazam]

A bit more info, please.
Are you on Scope/Backstage 3, or just Packedge, or Deskpack +, etc.
I haven't seen, or don't understand, your question about size and speed of CS2 files.
Esko has NOT solved all the transparency issues. You cannot take any old CS file and import it and expect flawless results. There are a few ground rules, still.
I will say, GRS's days are numbered. When we pick up grs (Scope 2) files and use them in Scope 3, we check them very carefully. There is some room for trouble.

[Oppah]

Shazam,

I thought I'd entered my apps info in the signature window & it would show for other users. Sorry.

MAC OS X & Windows PC
AI CS2 - PS CS2
Deskpack plug-ins
BackStage 3
PackEdge 5
Mega Setters
CDI Advance
Epson 9000 & 9600
Cromalin b2

The issue with AI CS2 files as I see it when saved with PDF compatibility, the files sizes are larger and take longer to save (especially w/ placed images.) Any thoughts?

So, what limits and work arounds do you employ w/ AI effects?

Further what funcky things are happening to Scope 2 GRS's in Scope 3?

Thanks for the reply

[shazam]

OK, pretty much the same set-up we're running, thanks.

The CS2 issue with larger/longer I figured just came with the territory. I thught you were saying there was a problem with ESKO doing something to the file. You're saving with 'compatibility', it's kind of like the old days with doing an .eps from Illustrator; it was always WAY bigger and took WAY longer to save.

GRS and Scope PDF don't like to play nice, from what we've seen. Things don't show up in Packedge, or they show -up but don't image to film or rip to LEN, etc. Anything from a whole color channel to one character of text. Haven't been able to nail down the mechanism, and it's very sporadic. We just try to look at things VERY closely when we need to use grs in Scope 3.

If you come straight out of Ill with Deskpack, and bypass Packedge and grs, and say RIP straight to film, it seems pretty bulletproof.

As for Ill effects, you have to play by Esko's rules. For instance, instead of 20% transparent of Color A, make a 20%ColorA and give it 100% trans. A long way around the block, but it's not an everyday thing, either.