All About Page-Level Color Detection
Last modified on 15 August 2020 04:35 AM
Print job color detection refers to a process where a different print job cost is charged based on the use of color. Most organizations charge/account more for color jobs because of:
PaperCut NG/MF allows administrators to set a different cost on color vs grayscale (Black & White) jobs and will apply these costs based on one of two different methods:
Standard Color Detection:
Page Level Color Detection:
Page-level color detection is a more advanced mode and it works by applying the different grayscale and color costs on a page by page basis. If the page contains any use of color, the color rate is applied for this page, otherwise the black and white rate is applied.
PaperCut NG/MF accomplishes page level color detection by carefully analyzing each individual pixel on the printed page. It looks for use of color in all areas of a page such as:
This analysis is done while the document is spooling to the print server before the print job is passed to the printer. This allows accurate costs to be calculated prior to print allowing appropriate actions to be taken as defined by the administrator.
Page-level color detection is usually also run in conjunction with Hardware Page Count Validation. The validation works by querying the printer’s hardware (via SNMP) after the job, to ensure the analysis done on the software layer on the server prior to printing is the same as observed by the hardware.
What print drivers are required for Page-Level Color Detection?
Currently, PaperCut NG/MF can perform page-level color detection with many popular Page Description Languages used by print drivers. Including:
This combination covers about 95% of business style network printers. Many manufacturers offer PostScript and PCL drivers as well as proprietary ones - check your printer manufacturer’s website for availability. Where possible we suggest sticking to PostScript as this is the most mature and open standard and is the only environment that offers support for all major platforms.
PaperCut NG/MF is not able to perform page-level color detection for proprietary page description languages like PCL3GUI. Print drivers like this may use non-documented and proprietary languages, which are often evolving and in many cases it’s not viable to support page-level analysis for these drivers. PaperCut supports page-level color detection on the EMF spool file format so page-level detection is possible on some GDI drivers that spool the jobs in EMF format - results may vary, so testing is always required. At a minimum, document-level color detection is supported in many GDI devices.
Will page-level color detection slow printing?
Page-level color detection does add overhead to job analysis. It’s extra work to search through a document looking at every pixel for color than it is just looking for page ends/starts. However, in the real world we find that the slowdown in analysis is minimal and not noted by end-users. The reason for this is that as soon as color is found on a page, the color analysis is turned off for the remainder of the page. In real-world documents, the increase in analysis time is around 10–20%. For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6 is as follows:
Does PaperCut support color coverage or three-tiered billing (e.g. enhanced/limited or color coverage)?
This topic is addressed in detail in Tiered Billing and Color Coverage.
Page-level color detection sounds good. Why would I not use it?
If your printer supports page-level color detection, we recommend enabling it as it provides the most fair and accurate policy for charging print usage. There are, however, a few reasons why sites often choose not to enable it:
If page-level color detection forms an important part of your print management strategy or print charging policy, please also take the time to read: