Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


How do I use Digital Blueline with Prinergy VPS files?


Product

  Prinergy 1.0; Prinergy 1.1; Prinergy Connect 2.0

Platform

 

Operating system

 


Error

 


Symptoms

 

Customer wants to continue to use Digital Blueline with the VPS files that Prinergy has generated. It has been tested and shown to work (need Digital BlueLine V1.2F SP2 or later).

One key issue is that they still must have a valid license for DBlue -- it is NOT part of Prinergy (they either use an existing, licensed copy from Impact or else purchase a new one). This is probably not a huge issue since the only people who will really want DBlue functionality are ones who are already using it today with Impact.


Cause

 

Solution

 

You must use Digital Blueline 1.2F SP2 or later (for example, 2.0 beta).

Configuring Digital Blueline:

1) VPS files from Prinergy have extension ".vps". But DBlue by default looks for ".prv". Edit the DBlue template of interest. On the General tab, change the extension DBlue looks for to "*.vps". If you do not do this, DBlue will not recognize Prinergy's VPS files since they have a ".vps" extension.

2) You may also want to configure DBlue to "Wait for missing pages". If this is configured, DBlue will wait until it gets missing pages before it starts to print. If you don't set this and you send a surface with pages 5, 7, 8 & 10 to it, you will get DBlue proofs with 5 backed up with 7, and 8 backed up with 10 (and you expected 5/6 backed up and 7/8 backed up). Edit the DBlue template of interest. On the Print Options tab, check the "Wait for Missing Pages".

3) Start DBLUE and it will watch its hot folder, just like in Platemaster or Overture.

Configuring Prinergy to Output to DBLue:

1) Setup an Imposed Proof Process Plan in Prinergy which generates VPS files directly into the DBlue hot folder. Whenever you send surfaces to DBLUE, they will automatically get queued and output by DBLUE.

NOTE: It is recommended that you send all of the signatures in an imposition when you proof to DBlue. The reason is that if you send individual surfaces or signatures, DBlue may not have all the required pages to produce its output. This means that you will get bad proofs (page 5 backing up page 7 since page 6 was not on this surface) or DBlue will block waiting an infinitely long time for the missing pages (if you have the "Wait for Missing Pages" option set).

Permanent fix:


See also

 


Keywords

 

Digital Blueline, proofing, VPS


Technical contact(s)
 

Simon Chen

Submitted by
 

Date submitted
 


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.