02-14-2017 04:33 PM
Lets say i had a 6000 page document (a file) but wanted to staple every 6 pages. Is there a way to do that in freeflow? i saw nothing that stood out to me.
Solved! Go to Solution.
02-14-2017 06:25 PM
Assuming Freeflow Print server and guessing the Solaris version you would be looking for Pad printing > Subset Finishing
If you have it in your FFPS , you would find it in the job settings via right-click Properties > Output > Subset Options.
Using your example you would want to turn on User defined Subsets from the dropdown, and 6 pages per subset Finishing checked. <Finishing won't be available if you have not enabled stapling first>
Here it is in FFPS 9SP3
I don't currently have access to the newer Windows based FFPS for the C60 or iGen, if you have one of those and can't find it let me know and I will find one to capture it from.
02-12-2018 04:37 PM
We use pad printing on a regular basis - iGen 5 with windows based freeflow. Up until a couple weeks ago, it worked like a charm. We always had an issue if we did a proof of the file - a release would get us 1 pad, no matter what we had set up.We resolved this issue by changing the # of pads and doing a process and hold before releasing.
Lately, we have been unable to get the file to print correctly by using our saved queue. No matter what, after a proof, it only prints 1 pad at a time. Now we are unable to use a queue and must set up each job after proofing. time consuming as there is layout, shifting, etc on top of the pads.
Any ideas on what could be happening?
02-13-2018 12:36 PM
It has to be assumed that the queue is broken, so it would stand to reason that simply making another one with the same settings and a different name would fix it.
Assuming nobody disabled PDL retainment on the FFPS...
Then you would need to troubleshoot in steps
1. Import pdf to the FFPS and apply settings, does it work?
2. Does it work imported to a new queue with the right settings?
3. Print to the queue from whatever application, does it still work?
4. Did MS decide your Windows 10 PC should be using a class driver?
etc etc to find the problem