Enfocus Community

Every so often we get encounter a file that causes our Canon Colorstream to experience buffer underruns while printing.
This is due to the fact that the file contains a huge amount of unoptimized vector images (resulting in a crippling amount of points) which the rip cannot supply to the printer fast enough.
(we have less of an issue with this in our offset workflow as it can take a lot longer to develop a plate anyway)

Is there a way to check a file (actionlist/preflight) for an x amount of vector images and return a warning, or is there a better option?

Can you drop me an email with a sample file?

I think we can help.

Andrewb@enfocus.com

Hi Andrew,

I sent you a sample file via Wetransfer, pages 43 and 46 seem to cause the most problems.

HI Jeroen

Give this one a try, it worked on the file you supplied but you might want to play with the values in it.

This Action List checks for pages in a PDF that have more than 1,000 paths and are therefore likely to be complex to rip and output.
https://esko.box.com/s/ef3s6vqfmj3va89y1q6kr9ulyiw7iltw

You might also be interested in joining our Linkedin PitStop user group. There is a lot of content and information like this on there.

Thanks, that seems to work perfectly!

We'll play with the threshold value should that become neccesary.
(Paths are just one component after all...)

Glad to be of help.

Does PitStop currently have the ability to also correct the issue of too many points in a path, or just identify the problem?

You can select pages with too many points and convert the page content to a bitmap.

That would only work for images, though. How about in the case of a very overworked cut path / clipping path?

Interesting idea, if you have any sample files can you forward them so we can investigate? andrewb@enfocus.com