I am trying to route by size and I am having some issues. I have created a characteristic called 11 x 8.5 - no bleeds. This characteristic has the following conditions
PDF Crop box is equal to 11.000 x 8.500 or
PDF Crop box is equal to 11.001 x 8.501 or
PDF crop box is equal to 10.999 x 8.499
When I send a file through that the size for all of the PDF boxes is 11.000 x 8.500 (I have checked all of the PDF boxes) it is sending to the to the characteristic called 11 x 8.5 - bleeds. This characteristic has the following conditions
I have been trying to figure out why it does not follow the proper routing and have tried numerous options with no success.
Does anyone have any idea as to why this would not work?
Solved! Go to Solution.
My guess why the letter sized PDF is not going to the expected Route branch is that the PDF is portrait. For portrait the Crop Box should be width = 8.500 and the length = 11.000 -- which is the reverse of your job characteristic condition.
Another source of the problem could be that the PDF was rotated. The description of the Boxes will include a Rotate and retain the original dimensions (not switching the Box dimensions) . FFCore uses the dimensions to determine the Boxes.
Example 1-- a "clean" landscape Letter PDF snippet:
3 0 obj
<</Type/Page/Parent 2 0 R/Resources<</Font<</F1 5 0 R>>/ExtGState<</GS7 7 0 R/GS8 8 0 R>>/XObject<</Image9 9 0 R>>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/MediaBox[ 0 0 792 612] /Contents 4 0 R/Group<</Type/Group/S/Transparency/CS/DeviceRGB>>/Tabs/S/StructParents 0>>
Example 2 -- an original portrait Letter PDF rotated in Acrobat to landscape PDF snippet:
424 0 obj
<</Annots[441 0 R 442 0 R 443 0 R 444 0 R]/Contents[427 0 R 428 0 R 429 0 R 430 0 R 431 0 R 432 0 R 433 0 R 434 0 R]/CropBox[0 0 612 792]/Group<</CS/DeviceRGB/S/Transparency/Type/Group>>/MediaBox[0 0 612 792]/Parent 419 0 R/Resources<</ExtGState<</GS10 445 0 R/GS7 446 0 R>>/Font<</F1 448 0 R/F2 450 0 R/F3 452 0 R/F4 456 0 R/F5 458 0 R>>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/XObject<</Image5 439 0 R>>>>/Rotate 90/StructParents 0/Tabs/S/Type/Page>>
Both examples will appear in Acrobat to be landscape.
This doesnt work either since the files would read 8.5 x 11 and would not follow the 11 x 8.5 - with bleeds path either and would go into the "All Other" path.
Not sure if there is a way of attaching a file. I can send you a couple of files that do not work for you to look at if you tell me where to send them. I know that the logic does work because many files go through properly but some do not and I cannot figure out why. Unfortunately it happens at least a few times each day.
I did not have this issue with process manager.
You do not need to use the “Check” Between sizes for this small variation in Document sizes. If you use the check for 11x8.5 the other to variations (like 10.999x8.499) will go to the same branch. It seems like Core is only using 2 decimals. If I try with a 10.99x849 document it does not go to the same Branch. Maybe David could confirm this. A good way of checking what Core is reading out of the file is to use a watermark component with a text variable showing what you are looking for. In this case I used the Crop box width and height ($FFwfDoc.pdfCropWidth$$FFwfDoc.pdfCropHeight$). You will find all Variables under the help meny and Appendix: Job Properties.
This is the workflow. The Finish component is just to be able to see which Branch the job goes to.
This is the different jobs gone through the Route. As David said a document rotated in Acrobat will still have the original Page box size. The document called PDF Crop Box is equal to 8.500 x 11.000 is created as Landscape in InDesign.
This is in Acrobat where the Watermark at the bottom of the page show 11.00 8.50 and Acrobat shows the 10.999 x 8.499 size.
You said you you checked for all PDF Boxes but you only showed the check for the Crop box in the screen shot. It is not necessary to check for all boxes. The easiest check for Bleed is the same as what you might have used in Process Manager the check for “Maximum Bleed Distance”.
If you set the check for “Maximum Bleed Distance” to Greater than 0 you will get files with a Bleed box larger than the Trim box to go to this Branch.
The Routing I used. I have not analyzed why the Fits Between does not work as you want at this time. None of the files will go to this Branch. I hope you will see that you do not need to define the fit Between to get what you want.
You will see that you can reuse the Job Characteristics in the Routing component which makes it much more user friendly than with Process Manager. You will not have any limitations of how many Route you can have in a workflow. One thing to mention about the Route is that it has to have a uniqe name for your system. Even though it is in two different workflows the name has to be unique. You can still save Route as a preset by clicking on the Route in the Workflow and choose save as Global Preset. Then you can reuse this for other workflows and the will be numbered to get a unique name when you drag them into your workflow.
When you insert a Route component you can check which names are already taken under the Information buttton.
I have attached my test workflow and the test files for you to test with.
I hope this help you.
The FFCore page size algorithm works based on CPSS (Xerox Common Print Semantic Specification) value. The conversion factor of inches to CPSS is 2540 and millimeters to CPSS is 100. All the units will be converted to CPSS value and comparisons done.
If I define the size to be 11.000 inches a Box of 11.0001 inches be considered will be considered equal due to CPSS rounding (see below).
11.000 * 2540 => 27940
11.0001 * 2540 => 27940.
How can we tell if a page has been rotated? I do not know where you got the information noted below. Is this some kind of application you have that is giving you this information? I have done tests with PDF files and when I rotate them the box dimensions always rotate as well for example an 8.5 x 11 document when rotated show the crop boxes, trim boxes etc. as 11 x 8.5.
I used WordPad and then searched for "MediaBox" and examined the PDF object. I do not know of an "application" (including Acorbat) that will show that a PDF Box has been rotated.