News:

Main Menu
Menu

Show posts

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 Menu

Topics - C2V

#1
Esko / AE, Workflow Trap Tickets & Images
January 26, 2018, 01:31:47 PM
Odd title but I wasn't sure what to call it.

Since starting at my new workplace and using Esko Automation Engine 14.1 (currently installed) I noticed that clients would supply us .ai files with images (on transparent backgrounds) linked in [.tiff, .psd, .jpg(ugh)] the issue I have is when I run these files through our trap ticket  it always omits trapping the images to the background.

It gets worse when the .psd files have drop shadow layers in them.
Usually I end up just setting a clipping path around the image (and not the drop shadow) then going into the file, duplicating the image, and relinking the top most image to my clipping path applied image. (basically sandwiching the images ontop of one another, with he original image and its drop shadow in tact) 

Is this method risky?  totally crazy?  ... seems to work and beats  sandwiching 3+ images to get one that will trap in esko: just the shadow.psd / middle image with clipping path applied.psd / top most image with clipping path applied.psd ))

One particular graphics house does not use clipping paths (well I'm sure they do when creating this knockout) and instead creates a white ko behind the image that is contracted about 4pixels, then sets their main images to darken, thus creating a trap.. tho one thats more difficult to edit if the need arises]
I have used this method as well but finding the right pixel contraction to use on the images so you do not get too much or too little trap is tough as it tends to vary on the overall images size.
4 pixels on a tiny image 1x1 inch is too much but seems ok on an image thats 3x3 inch

I ran through some requested help cases which the old prepress operator had submitted to Esko support.
In one he mentioned that the images in his files were not trapping to the process background / pantone background in his files.

The help desk had assisted him and then closed his case.  Unfortunately they do not leave good notes on what the resolution of the case was.
I can tell by what is in the notes that they had told him:

Esko Support:
"The transparent bkgd does not provide any pixels to extend in order to create the trap.
The only way I could get it to Trap was to increase the Trap amount for the images and the trap direction for the spot to go into the image.
It is a file issue, if there is not data (transparent pixels around the image) then there is nothing to spread into the spot color. It would be better to actually have a tight clipping mask around it."

Which lead me to always having to create a tight clipping mask around the images in the files supplied to us (by almost every customer, and we have many)
Normally, not a huge issue but when certain customers supply 10 to 30 files with 2 to 4 different images in each it can take hours and hours of extra time spent creating a close clipping mask (1200%to 1600% zoom level) around the art for Esko to then realize there is a path/edge and trap the file/images properly.
Without this path Esko will not trap the image(s) to the background.

I have tried setting the ticket to how the support suggested and it does not work. 
I have set the trap to 1pt just to see and it fails to trap.

So is there any way to get images to trap to process or pantone backgrounds without having to spend extra time creating clipping paths in photoshop?

I have suggested to the artists (and it is within our spec sheet) that this step needs to be done on their end. (haha)  quick selection tool and/or lasso tool...beyond sloppy (or just not done at all as it takes too much time...."go figure"
Of course, when we try to charge them for this extra time it's an issue
(one which we end up on the losing side of)

If i send the files back nothing would ever get done file wise as it occurs with 90% of our customers.

Sorry turned into a bit of a rant there at the end : )

Thanks,
C2V
#2
Esko / Esko & DCS / Copy dot files
January 17, 2018, 10:11:16 AM
Hi,

Frequent browser but never joined or posted.
The community seems very helpful so I figured I would give it a shot and see if I can get any assistance.

Currently working with Esko and we have a few customers who have never updated their art and we need to get them through to plating.

A previous employee here had contacted Esko support regarding DCS and Copydot files and working with them using Esko workflow.

While I was not around for the conversation (as I was not working here at the time) they did end up setting up a wrapper file ticket for us to use.
(basically takes the .EPS and wraps it a .pdf)

I can get this file through Esko by:

placing this generated .pdf (from the Wrapper ticket) into Indesign.
Dropping in our company marks and colour dots and job # information.
Saving as a Hi Res PDF out of Indesign.
Ripping that high res pdf through Esko using our regular rip/trap ticket created (it was here when I started and seems to work for everything but these files) (we also have a ticket that is an exact duplicate except it does not trap a file)
Automation Engine viewer can see this final .pdf but everything looks ... moire patterned ( in Prinergy this was common and the files ended up plating OK despite the virtual proofers viewing of them)
but
When this pdf is placed into Pandora (as it is the layout program we are using) it just errors and we get a grey box with a red X in it.

When we go to Esko for assistance, they mention Pandora is the culprit and Kodak mentions Esko is the culprit (perhaps bit of both..)

Any idea on how we would use DCS/Copy Dot files with Esko?

I asked my co-worker and they used Rampage prior to Esko (Rampage is....odd and there seems to be no info or available training on it anymore, and they wouldn't train me on it anyhow.. I never received training on Esko either. (theres no time, i am the only operator who works with files) (been running blind for the last year, but so far so good)
We currently can't use Rampage as were having issues with the server its hosted on (permission issues) and our tech whom we hire in on as need basis insists that its not a server or permissions issues with Rampage but because we upgraded the OSX and CC suite.. (he's incorrect but won't budge on the issue so far)

Our short term work around is to send the files to our sister plant and they create the tiffs needed but its not a viable long term solution for us.
I have suggested these customers get a refresh on their art since we cannot work with it in our currently supported workflow and the sales are hesitant to ask them to do so. (why stir the pot apparently)

Thoughts?

Thanks,
C2V