We would like to create an Auto Workflow for Saddlestitch books under the size of 5x7.
Goal: To drop in smaller booklets, under the finished folded size of 5x7, and have them impose onto a sheetsize of 29.5x20.8125. That in itself is simple, the smallest size that our finishing equipment can fold and trim is 5x7, meaning, if we have a final book size of 4x6, the smallest sheet size of each imposed book, when trimmed out of the imposed sheet, can only be 10x7. We would like to drop different size books into 1 workflow, and have Core impose them centered in each quadrant of the sheet, with the quadrant being no smaller then 10x7.
Problem: Core wants to impose too many on a sheet, which doesn't give a large enough sheet to fold & trim on our finishing equipment. For example: If we drop a 3"x5" booklet into Core, it wants to impose it 15up on our 29.5x20.8125" sheet. This does not allow us enough paper per booklet to run on our finishing equipment.
What we have tried: In order to begin the AUTO process for different size books, using Route, I set a branch condition to send books that "fit into" 5"x7". Then under my Imposition Node, I set the press sheet to automatic, layout to signature relative to trim box with Cell Clustering off. and a .25" Margin under Gutters. then, under the Secondary Stage, I set my Press Sheet size to 29.5x20.8125, with Orientation at Automatic.Under Layout, I set it to Repeated, Relative to PDF Bleed box, with Cell Clustering Off and the Margins set to .5", to accommodate the gripper on our press. I set the Impose Relative To "Bleed Box" under the Layout Tab in the Secondary Stage so that Core will impose it with the .25" Margin that I set in the Primary Stage. I really can't set the Margin too large in the Primary Stage, because we don't know what size book is being sent through the workflow.
So basically, I would like Core to impose automatically any size book, with a minimum size of each book block at 10"x7". These are Saddlestitch, so the pre-fold size is 10x7, folded to 5x7.
One could have multiple branches out of a Route based on the page size. The smallest page size should be the first branch, etc. Off of the multiple branches, different imposition nodes can be defined meeting the requirements for the page size.
In the example you provide, I think you dont really want 'Automatic' page size. It really sounds like you want 10x7. This way all the small booklets would be imposed onto this 10x7 sized page. Then you could as a second step impose the 10x7 pages using the media box instead of bleed box onto your larger sized press sheets.
Also, the imposition is RULES based. What this means is that you can select 'Automatic' and then also select MULTIPLE sheet sizes for the jobs to be imposed onto.
For example, you might set an Automatic page size, then select 8.5x11, 11x17, 12x18, as possible sizes. After the imposition is completed, it will try the imposed document on each of the sizes you selected for the best fit (least paper waste actually). So you really dont even need the Route node in your workflow if you program this correctly. The 10x7 would be a custom size you can program for available sizes.
I have attached a workflow from Core version 6.1.5 that has a sample for you. The workflow keeps any bleed from your booklets (standard imposition settings can lose them) and then after the 'auto' sized booklets, then I put a Route node in that is for sizes that fit into 7x10 it will then do another imposition (1up) that adds crop marks and places onto 10x7. Next a preflight removes all boxes in the PDF file. This is so that when the gang up onto the 20x29 press sheet is done the imposition can be done based on the trim box for ALL SIZES. However, because we removed the trim box from the small documents it will instead use the media box (the only box it will have). As such, the smaller documents will get a second set of cut marks on the 20x29 sheet that are placed at 10x7. This way you can tell where to cut the sheet, then where to cut the small 4x6 booklets for final trim.
Thank you so much for the info. I use .kpf files brought into Preflight quite a bit, but just lately, Core has stopped recognizing my .kpf files. Do you know why that might be?