finding if a page has bleed with pitstop

[sweisens]

We would like to find if a pdf has bleed before we bring it into our system. Can Pit Stop do this for us?

 

[pajdzn]

Why not check the page size of the pdf to see if includes bleed? If it is .25 bigger than the trim size then the excess can be used as bleed as long as there is enough room to keep copy from trimming.

 

[mattbeals]

Kind of, not really. It's a real tricky thing to detect. We can detect that objects are within a certain distance of the trim edge, and under certain conditions we can extend rectangles into the bleed area. But it is limited in its effectiveness. Better than doing nothing, but not 100% reliable. So yes, kind of, sort of sometimes.

 

[pacart]

just open the pdf in acrobat pro, you don't even need pitstop to do this, then place your mouse in the bottom left corner of the window and the size will pop up. You should be able to tell if it has a bleed this way- as long as you know what the final cut size should be.

 

[Sick HP]

We would like to find if a pdf has bleed before we bring it into our system. Can Pit Stop do this for us?

This is how I do it. The icon is show page boxes works fine for me.

-Dan

 

[sweisens]

sorry we are working with pitstop server. We want to check 1000's of files on the fly

 

[Sick HP]

sorry we are working with pitstop server. We want to check 1000's of files on the fly

I do not know how to do that. I don't know of an action you could create that would do this.

-Dan

 

[sweisens]

We have found that it can help find some but flags lots of things that are not a problem. Thanks anyway

 

[mattbeals]

Detecting "effectively bleeding objects" in a meaningful and automated way is kind of the holy grail of preflighting. No one does it correctly all of the time. Still need a human for that!

 

[caio]

In the preflight report (if you have check "Enable page box layout") there is this information.

 

[sweisens]

We have looked at that window as well. It came up with mixed results. We can't trust it. Thanks for looking.

Sy

 

[the_brain]

We have found that it can help find some but flags lots of things that are not a problem. Thanks anyway

Hi,

you can do it using an action list or activate the check in the preflight profile. It depends on which version of Pitstop Server you're running.

The preflight check can be found in the 'Page settings' category (second check). You set your area from a margin within the trim box to the bleed box or a margin outside the trim box. Any object located in this area will be reported.

The action list is a bit more complicated. the action you need to use a couple of times is the 'select objects inside/outside region'. Here you can set up to look inside or outside a page box.
e.g. find any object in between trim and bleed box
select objects inside/outside region (outside trim box)
select objects inside/outside region (inside bleed box)
AND
log selection

I hope this helps,
bert

 

[mattbeals]

This action works well in detecting objects in the bleed area. But what it doesn't do, and no one does this, is give a meaningful report. One object in the bleed area will trigger this even though a dozen or more objects may need to bleed but don't. Compound this with the bleeding object detection and extension (for rectangles) and you get a bit closer. But no automated solution is going to give a high enough accuracy rate to be truly meaningful. Still need a human for this.

 

[david]

What kind of routing do you have?

What kind of routing do you have?

Since you are using P Server - do you have any way of routing jobs based on the specific product ticket into specific queues in Pitstop for exact checking of the incoming job to specific rules and actions for the exact product?

 

[the_brain]

Since you are using P Server - do you have any way of routing jobs based on the specific product ticket into specific queues in Pitstop for exact checking of the incoming job to specific rules and actions for the exact product?

When the product ticket is XML, XMP or JDF, you might want to take a look at Enfocus Switch: Enfocus - Workflow automation for publishers and printers with Enfocus Switch 08. Standardize your work and reduce errors

Bert

 

[lfelton]

Detecting "effectively bleeding objects" in a meaningful and automated way is kind of the holy grail of preflighting. No one does it correctly all of the time. Still need a human for that!

Matt, we seem to have this working 100% so far on live customer orders , what's the prize? Lots of code though.

 

[the_brain]

Hi,

you can do it using an action list or activate the check in the preflight profile. It depends on which version of Pitstop Server you're running.

The preflight check can be found in the 'Page settings' category (second check). You set your area from a margin within the trim box to the bleed box or a margin outside the trim box. Any object located in this area will be reported.

The action list is a bit more complicated. the action you need to use a couple of times is the 'select objects inside/outside region'. Here you can set up to look inside or outside a page box.
e.g. find any object in between trim and bleed box
select objects inside/outside region (outside trim box)
select objects inside/outside region (inside bleed box)
AND
log selection

I hope this helps,
bert

If my explanation doesn't make sense...check out this tutorial: http://www.enfocus.com/webmarketing...l#/flv/PitStopProfessional/PP10_Checkfixbleed

cheers,
Bert