Following his post last week about the speed and scalability of your raster image processor, in this film, Martin Bailey, distinguished technologist at Global Graphics Software, explains how to determine how much raster image processor (RIP) power you need to drive a digital press by calculating the press data rate. It’s the best way of calculating how much RIP power you need in the Digital Front End (DFE) to drive it at engine speed and to ensure profitable printing.
If you’re building a digital press, or a digital front end (DFE) to drive a digital press, you want it to be as efficient and cost-effective as possible. As the trend towards printing short runs and personalization grows, especially in combination with increasing resolutions, more colorants and faster presses, the speed and scalability of the raster image processor (RIP) inside that DFE are key factors in determining profitability.
For your digital press to print at speed you’ll need to understand the amount of data that it requires, i.e. its data rate. In this film, Martin Bailey, distinguished technologist at Global Graphics Software, explains how different stages in data handling will need different data rates and how to integrate the appropriate number of RIP cores to generate that much data without inflating the bill of materials and DFE hardware.
Martin also explains that your next press may have a much higher data rate requirement than your current one.
Product manager Paul Dormer gives an insight into why the Harlequin Core is the leading print OEMs’ first choice to power digital inkjet presses in this new film.
A raster image processor (RIP), Harlequin Core converts text, object and image data from file formats such as PDF, TIFF™ or JPEG, into a raster that a printing device can understand. It’s at the heart of the digital front end that drives the press.
Proven in the field for decades, Harlequin Core is known for its incredible speed and is the fastest RIP engine available. It is used in every print sector, from industrial inkjet such as textiles and flooring, to labels and packaging, commercial, transactional, and newspapers.
As presses become wider, faster, and higher resolution, handling vast amounts of data, the Harlequin Core remains the RIP of choice for many leading brands including HP, Mimaki, Mutoh, Roland, Durst, Agfa and Delphax.
Ever wondered what a raster image processor or RIP does? And what does RIPping a file mean? Read on to learn more about the phases of a RIP, the engine at the heart of your Digital Front End (DFE).
The RIP converts text and image data from many file formats including PDF, TIFF™ or JPEG into a format that a printing device such as an inkjet printhead, toner marking engine or laser platesetter can understand. The process of RIPping a job requires several steps to be performed in order, regardless of the page description language (such as PDF) that it’s submitted in. Even image file formats such as TIFF, JPEG or PNG usually need to be RIPped, to convert them into the correct color space, at the right resolution and with the right halftone screening for the press.
Interpreting: The file to be RIPped is read and decoded into an internal database of graphical elements that must be placed on the output. Each may be an image, a character of text (including font, size, color etc), a fill or stroke etc. This database is referred to as a display list.
Compositing: The display list is pre-processed to apply any live transparency that may be in the job. This phase is only required for any graphics in formats that support live transparency, such as PDF; it’s not required for PostScript language jobs or for TIFF and JPEG images because those cannot include live transparency.
Rendering: The display list is processed to convert every graphical element into the appropriate pattern of pixels to form the output raster. The term ‘rendering’ is sometimes used specifically for this part of the overall processing, and sometimes to describe the whole of the RIPing process.
Output: The raster produced by the rendering process is sent to the marking engine in the output device, whether it’s exposing a plate, a drum for marking with toner, an inkjet head or any other technology.
Sometimes this step is completely decoupled from the RIP, perhaps because plate images are stored as TIFF files and then sent to a CTP platesetter later, or because a near-line or off-line RIP is used for a digital press. In other environments the output stage is tightly coupled with rendering, and the output raster is kept in memory instead of writing it to disk to increase speed.
RIPping often includes a number of additional processes; in the Harlequin RIP® for example:
In-RIP imposition is performed during interpretation
Color management (Harlequin ColorPro®) and calibration are applied during interpretation or compositing, depending on configuration and job content
Screening can be applied during rendering. Alternatively it can be done after the Harlequin RIP has delivered unscreened raster data; this is valuable if screening is being applied using Global Graphics’ ScreenPro™ and PrintFlat™ technologies, for example.
A DFE for a high-speed press will typically be using multiple RIPs running in parallel to ensure that they can deliver data fast enough. File formats that can hold multiple pages in a single file, such as PDF, are split so that some pages go to each RIP, load-balancing to ensure that all RIPs are kept busy. For very large presses huge single pages or images may also be split into multiple tiles and those tiles sent to different RIPs to maximize throughput.
To find out more about the Harlequin RIP, download the latest brochure here.
When planning the implementation of your first or next digital press, the PC specification you choose to run your software workflow will play an important part in the data rates you will be able to achieve. Assuming you are not bottlenecked by disk drive performance due to requiring intermediate disk accesses, you can generally expect data rates to rise with the computational power of your PC.
It might therefore make sense to review the PassMark scores for a range of CPUs within your budget and make your choice based on that, but this alone won’t be enough to tell you whether you’ll be able to drive your printer at full rated speed. Similarly, you may already have an existing PC system in mind but need to know if it will be powerful enough for your new requirements.
Ideally, you could set up an evaluation system to run some typical print jobs to get a definitive answer, but this could be costly and labor-intensive, especially if this is your first digital press.
It’s for this reason we created Direct Benchmark™: an analysis tool that exercises Harlequin Direct™, our ultra-high data rate RIPping and screening solution, with your choice of press configuration and print jobs, stepping through a tuning cycle to obtain a series of data rates and line speeds that can be achieved.
There are two main ways Direct Benchmark can help you: firstly, if you have an existing PC system to run on, you can install Direct Benchmark and gather your own results; secondly, you could base your decision on a database of Direct Benchmark results we are gathering here at Global Graphics Software from running a variety of jobs on a range of PC specifications.
Running Direct Benchmark yourself
Whilst a real Harlequin Direct system would be connected to printhead electronics and driving your press directly, the Harlequin Direct invoked by Direct Benchmark doesn’t require this connection. This makes it very quick and easy to install and start gathering performance numbers. The screenshot below shows the settings you can use to reflect your printer configuration and define the print jobs to benchmark.
During benchmarking, you will be presented with a screen showing statistics for each run and a real-time graph of data rate at the bottom, and then you will be able to export the results at the end. If you would like to see Direct Benchmark in action, you can view a short demo here:
Using the Direct Benchmark database
If you aren’t in a position to run Direct Benchmark yourself, we are in the process of gathering results for a range of press configurations and print jobs, running on a variety of PC hardware specifications. This is being conducted in conjunction with Proactive Technologies, who are providing access to some of the machines we’re using. Whilst it is too early to draw any conclusions or share our results at this stage, if you have some typical print jobs and a press configuration in mind, please get in touch with me, email@example.com, because we may be able to generate the results for you.
Ian has over 15 years’ experience in industry as a software engineer focusing on high performance. With a passion for problem-solving, Ian’s role as product manager for the Direct range gives him the opportunity to work with printer OEMs and break down any new technology barriers that may be preventing them from reaching their digital printer’s full potential.
Would you fill your brand-new Ferrari with cheap and inferior fuel? It’s a question posed by Martin Bailey in his new guide: ‘Full Speed Ahead – how to make variable data PDF files that won’t slow your digital press’. It’s an analogy he uses to explain the importance of putting well-constructed PDF files through your DFE so that they don’t disrupt the printing process and the DFE runs as efficiently as possible.
Here are Martin’s recommendations to help you avoid making jobs that delay the printing process, so you can be assured that you’ll meet your print deadline reliably and achieve your printing goals effectively:
If you’re printing work that doesn’t make use of variable data on a digital press, you’re probably producing short runs. If you weren’t, you’d be more likely to choose an offset or flexo press instead. But “short runs” very rarely means a single copy.
Let’s assume that you’re printing, for example, 50 copies of a series of booklets, or of an imposed form of labels. In this case the DFE on your digital press only needs to RIP each PDF page once.
To continue the example, let’s assume that you’re printing on a press that can produce 100 pages per minute (or the equivalent area for labels etc.). If all your jobs are 50 copies long, you therefore need to RIP jobs at only two pages per minute (100ppm/50 copies). Once a job is fully RIPped and the copies are running on press you have plenty of time to get the next job prepared before the current one clears the press.
But VDP jobs place additional demands on the processing power available in a DFE because most pages are different to every other page and must therefore each be RIPped separately. If you’re printing at 100 pages per minute the DFE must RIP at 100 pages per minute; fifty times faster than it needed to process for fifty copies of a static job.
Each minor inefficiency in a VDP job will often only add between a few milliseconds and a second or two to the processing of each page, but those times need to be multiplied up by the number of pages in the job. An individual delay of half a second on every page of a 10,000-page job adds up to around an hour and a half for the whole job. For a really big job of a million pages it only takes an extra tenth of a second per page to add 24 hours to the total processing time.
If you’re printing at 120ppm the DFE must process each page in an average of half a second or less to keep up with the press. The fastest continuous feed inkjet presses at the time of writing are capable of printing an area equivalent to over 13,000 pages per minute, which means each page must be processed in just over 4ms. It doesn’t take much of a slow-down to start impacting throughput.
This extra load has led DFE builders to develop a variety of optimizations. Most of these work by reducing the amount of data that must be RIPped. But even with those optimizations a complex VDP job typically requires significantly more processing power than a ‘static’ job where every copy is the same.
The amount of processing required to prepare a PDF file for print in a DFE can vary hugely without affecting the visual appearance of the printed result, depending on how it is constructed.
Poorly constructed PDF files can therefore impact a print service provider in one or both of two ways:
Output is not achieved at engine speed, reducing return on investment (ROI) because fewer jobs can be produced per shift. In extreme cases when printing on a continuous feed (web-fed) press a failure to deliver rasters for printing fast enough can also lead to media wastage and may confuse in-line or near-line finishing.
In order to compensate for jobs that take longer to process in the DFE, press vendors often provide more hardware to expand the processing capability, increasing the bill of materials, and therefore the capital cost of the DFE.
Once the press is installed and running the production manager will usually calculate and tune their understanding of how many jobs of what type can be printed in a shift. Customer services representatives work to ensure that customer expectations are set appropriately, and the company falls into a regular pattern. Most jobs are quoted on an acceptable turn-round time and delivered on schedule.
Depending on how many presses the print site has, and how they are connected to one or more DFEs this may lead to a press sitting idle, waiting for pages to print. It may also delay other jobs in the queue or mean that they must be moved to a different press. Moving jobs at the last minute may not be easy if the presses available are not identical. Different presses may require different print streams or imposition and there may be limitations on stock availability, etc.
Many jobs have tight deadlines on delivery schedules; they may need to be ready for a specific time, with penalties for late delivery, or the potential for reduced return for the marketing department behind a direct mail campaign. Brand owners may be ordering labels or cartons on a just in time (JIT) plan, and there may be consequences for late delivery ranging from an annoyed customer to penalty clauses being invoked.
Those problems for the print service provider percolate upstream to brand owners and other groups commissioning digital print. Producing an inefficiently constructed PDF file will increase the risk that your job will not be delivered by the expected time.
You shouldn’t take these recommendations as suggesting that the DFE on any press is inadequate. Think of it as the equivalent of a suggestion that you should not fill your brand-new Ferrari with cheap and inferior fuel!
The above is an excerpt from Full Speed Ahead: how to make variable data PDF files that won’t slow your digital press. The guide is designed to help you avoid making jobs that disrupt and delay the printing process, increasing the probability of everyone involved in delivering the printed piece; hitting their deadlines reliably and achieving their goals effectively.
To be the first to receive our blog posts, news updates and product news why not subscribe to our monthly newsletter? Subscribe here
About the author:
Martin Bailey first joined what has now become Global Graphics Software in the early nineties, and has worked in customer support, development and product management for the Harlequin RIP as well as becoming the company’s Chief Technology Officer. During that time he’s also been actively involved in a number of print-related standards activities, including chairing CIP4, CGATS and the ISO PDF/X committee. He’s currently the primary UK expert to the ISO committees maintaining and developing PDF and PDF/VT.
To be the first to receive our blog posts, news updates and product news why not subscribe to our monthly newsletter? Subscribe here