Harlequin VariData (HVD) with Tiling and the Scalable RIP

This page applies to Harlequin v13.1r0 and later; and to Harlequin Core but not Harlequin MultiRIP

If /HVDElement tiling has been specified in any way, ScheduleIndividualTiles is assumed to be false. This means chunks of pages are always sent to individual farm RIPs that do their own HVD scanning in isolation, taking into account any tiling parameters specified. This is because we cannot pre-scan /HVDElement tiles in the controlling RIP, as that requires an HVD scan.

If there is no /HVDElement specified but /HVDPage is specified, the HVD page tiles are scheduled based on the ScheduleIndividualTile value but with slightly different semantics than what is described above. Mainly:

• If ScheduleIndividualTiles is true and all tiles for each page are identical across the entire job, a chunk of pages is sent to a farm RIP but with an individual tile for all pages in that HVD page range. This means the first page range is processed in parallel, improving first page output time.
• If ScheduleIndividualTiles is false, chunks of pages are sent to farm RIPs that process every tile on every page in that page range. This is the same behavior as described above.