WHAT IS VIPP NATIVE MODE PRINT DRIVER?
In DesignMerge-ese, a Print Driver is a separate module that enables printing (or emitting) in the desired variable data language. Inherent to DesignMerge architecture is the ability to modify and add Print Drivers as VI technology evolves and improves. In this case, the Print Driver will emit VIPP in a way that eliminates the need for programming. The DesignMerge VIPP Native Mode Print Driver is available for the Macintosh platform.

The DesignMerge VIPP Native Driver creates output that is compatible with any VIPP-enabled DFE. A VIPP Native Mode file is essentially three layers — Fixed, Variable Text, and Variable Image layers. The Fixed Layer contains all static data on the page, which may be text or images. The Variable Text Layer contains all variable text data; one page of variable text is created per each record in the database. If variable images are used in the document, the VIPP Native Mode driver will first analyze the database to determine which combination of variable images are used in the job. The Variable Image Layer will contain this information; all three layers are combined per record to produce a composite output.

WHY IS DESIGNMERGE VIPP NATIVE MODE IMPORTANT?
Three primary reasons: eliminates the need for VIPP hand coding, simplifies training and implementation of VIPP Workflow, and utilizes all of the various DesignMerge features such as CopyFit™, Rules, and Sequencing.

1. ELIMINATES THE NEED FOR VIPP HAND CODING
One of the challenges inherent to a VIPP workflow is that often, hand-coding of VIPP files is required. With the VIPP Native Driver, the resulting VPC file is a self-contained VIPP-ready product, ready to be RIP’d and start the press running. There are no jdt, dbm, or dbf files to edit — just the vpc file with instructions on how to process the page. It’s simple, and it RIPs much faster than the output device can print.

2. SIMPLIFIES TRAINING AND IMPLEMENTATION
As DesignMerge executes the merge, the operator simply transfers the finished file into the DFE and starts the RIP’ing. The process becomes one of point and click with little to no need for programming.

Utilizes CopyFit™, GroupPicture™, Rules, Sequencing, etc. All of DesignMerge’s capabilities are accessible with VIPP Native; in addition, Quark’s H&J tables and kerning are used as well. The merged file will then RIP at over 100 PPM.

3. SUPPORTS DATA DRIVEN GRAPHICS (DDGs)
A hallmark of VIPP is the creation of DDGs during the RIP process. VIPP Native fully supports this capability using the same DDG interface.



Files are merged in DesignMerge, but the data driven graphics are created
“on-the-fly” at the server.

HOW DOES DESIGNMERGE HANDLE VIPP NATIVE MODE?
Create the layout in QuarkXPress, and merge the files using DesignMerge with the Creo VPS Driver selected.

Create a layout in QuarkXPress, add the variable pieces with DesignMerge, and then merge the files using DesignMerge with the VIPP Native Mode driver selected.



The user has the option at this point of creating either VIPP Native or VIPP Database output (VIPP Database creates the .jdt, .dbm, .dbf, and ps files).



Enter a name into VIPP Native Job Name. If more than one VPC file is created (based on the Pages Per Job setting), each will share the same base name, followed by a sequential number.

Enter a value into the Pages Per Job field; this will define the “chunks” that are sent to the DFE while the merge is in process. For example, if you have a 4-up job with 1100 records to merge, you will get a total of 275 printed pages. By entering “150” in Pages Per Job, DesignMerge will create two VPC files, one containing 150 pages, the other containing 125. This allows the RIP to begin processing the first 150 pages while the last 125 are merged. To automatically include all records into a single file, insert the word “all” into the Pages Per Job field. Note that this method lets DesignMerge handle the “chunking”; there is no need to attempt to chunk the file manually using the “From” and “To” fields in the Merge dialog box.

VIPP PROJECT CONTAINERS
If you elect to create a VIPP Project Container, the output folder should contain one or more VPC files. Each VPC file is a small .zip file that contains all of the resources required to process the job. Once the merge is completed, this single VPC file can be moved (FTP’d) to the VIPP Projects folder, as defined below. All files needed for printing are contained with this VPC file; the file ending in “.nm” will start the process and run the job.

If you specified a Pages Per Job value other than “All”, you may have several VPC files, each one containing the resources for a specific batch of pages. Each VPC file is transferred to the VIPP Projects directory for processing.

VIPP NATIVE OUTPUT OPTIONS
Download Fonts: Check this box if you wish to download font information for the job. This option requires that the Font Collector XTension be installed (a copy of Font Collector is included in the same folder as the VIPP Driver module). If the Font Collector XTension has not been installed, this selection will be dimmed.

Print Duplex: When this option is enabled, duplex printing will be enabled for the VIPP job.

Crop Marks: When this option is enabled, crop marks will be printed at the outside edges of the defined Paper Size. The crop marks are printed using standard VIPP coding that is automatically included in the output file.

Bleed: When this option is enabled, each layer file will be created with 8 points of bleed around the outside edges of the page. Note that the crop marks will be adjusted to account for this.

Paper Size Section: Use the popup menu to select the final “trim” size of the document. Select Match Document Size to use the same dimensions as the current document. You may also select from one of the pre-defined page sizes, or select Custom and enter your own page dimensions. The VIPP output will be centered within the Paper Size selected here. If you are using crop marks, please be sure to increase the Paper Width and Paper Height by at least 36 points more than the actual document size. Failure to do so will mean that the crop marks will not be printed.

VIPP NATIVE PREFERENCES
Several Preferences are available to assist in customizing your productivity.



Enable Background Processing - Speeds processing by performing updates off-screen (no waiting for screen refresh).

Include Log File Info in VIPP File - Includes log information (see above) into VIPP job for reference purposes.

Line Endings - Allows the user to specify line endings specific to Mac, Windows, or Unix.

Projects Folder Name - Supporting the SetProjects VIPP command, this defines the directory where the VIPP native file will be processed.

Verify project folder name - Compares the output folder name to the specified name. Should the names not match, the following dialog will appear:



DesignMerge can then modify the output to match the folder name by selecting the “Match Folder Name” button, or continue as defined.

Adjust temp doc size - With this selected, DesignMerge will automatically adjust the temp doc size to optimize merge performance. It is recommended to select this option.

ADVANTAGES OF THE DESIGNMERGE VIPP DRIVER

• Simplifies end-user training to begin printing with VIPP.
• Utilizes established QuarkXPress-based workflow to create VIPP output.
• Creates VIPP output that matches (layout-only, not color) the screen.
• Utilizes all of DesignMerge capabilities, including CopyFit, GroupPicture,
  and Rules.
• Eliminates the need for hand-coding.

EFI QA Approval, PPML Driver, Windows Rules and More!

As always, thank you for your interest in DesignMerge.
Please be sure to visit our website at www.1meadows.com.

• • •