Quote:
Originally Posted by kyle
Input files for each job must now be given to the RIP to store in its database, whereas before they were merely referenced by name and location. When I have a single PDF file with pages that are printed in different sections on three different presses, I now have to either upload all of the pages to all three jobs, wasting time and hard drive space, or split the PDF file into separate files to upload to each job.
If we have a job with 4 inks on the first flat and just black on 15 other flats, I have to send 4 inks for all 16 flats and then delete the unused inks in Printdrive, or make a separate job for the first flat and combine in Printdrive. If we didn't use DQS, I could create two separate "flows," one for the first flat and one for the other fifteen.
Archiving takes about eight hours for a few hundred jobs, whereas with Series 3 it was just a matter of keeping the small QJT file.
|
Hi Kyle,
Apogee 6 might be worth a look to you. In 6, they have a new feature called Products where with a single job flow you can output a job to different presses (each with their own processing requirements) by allocating each page in your run list to a product you define (e.g. cover, body, text, etc.). Unfortunately, Products is not compatible with PrintDrive DQS (but can be used with PrintDrive via flat workflow). I've attached a PDF that shows this new feature and what it looks like.
The problem you describe with having to delete unused colors on PrintDrive kinda baffles me. In the PrintDrive TP, there is a checkbox labeled, "Do not output empty separations." With that checked, you should not have to delete unused colors at PrintDrive. Do you have this box checked?
When you say that archiving takes about eight hours for a few hundred jobs, do you put an Archive or Keep Result action on the Renderer or something? In Apogee 5 and now 6, I have archived several hundred jobs, and at the longest, it took about 20 minutes.
Cheers,
Jon Morgan
Hopkins Printing
