All About Page-Level Color Detection

KB Home   |   All About Page-Level Color Detection

Main.PageLevelColorDetection History

Show minor edits - Show changes to output

Changed line 62 from:
''Categories:'' [[Category.TipsAndTricks|+]], [[Category.Printers|+]] [[Category.GlobalPrintDriver|+]]
to:
''Categories:'' [[Category.TipsAndTricks|+]], [[Category.Printers|+]]
Changed line 62 from:
''Categories:'' [[Category.TipsAndTricks|+]], [[Category.Printers|+]]
to:
''Categories:'' [[Category.TipsAndTricks|+]], [[Category.Printers|+]] [[Category.GlobalPrintDriver|+]]
Changed line 66 from:
[-Image: cc-by-ca by [[http://www.flickr.com/photos/sirihardeland/5432836109/|Siri Hardeland]]-]
to:
[-Image: cc-by-ca by [[http://www.flickr.com/photos/sirihardeland/5432836109/|Siri Hardeland]]-]
Changed lines 31-32 from:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''', '''HP/GL''' or '''XPS''' driver.  These terms refer to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  PostScript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is supported in most cases, and some GDI printers can support hardware-level validation (applied after print).
to:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''', '''HP/GL''' or '''XPS''' driver.  These terms refer to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  PostScript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers. 

GDI drivers 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 most GDI devices, and some GDI printers can support hardware-level validation.
Changed lines 43-44 from:
A: This topic is addressed in detail in [TieredBillingAndColorCoverage|+].
to:
A: This topic is addressed in detail in [[TieredBillingAndColorCoverage|+]].
Changed lines 43-44 from:
A: This topic is addressed in detail in [+|TieredBillingAndColorCoverage].
to:
A: This topic is addressed in detail in [TieredBillingAndColorCoverage|+].
Changed lines 41-44 from:
Q: Does PaperCut support color coverage or 3-tired billing (e.g. enhanced/limited color or color coverage)?

A: This topic is addressed in detail in TieredBillingAndColorCoverage .
to:
Q: Does PaperCut support color coverage or 3-tired billing (e.g. enhanced/limited or color coverage)?

A: This topic is addressed in detail in [+|TieredBillingAndColorCoverage].
Changed lines 34-35 from:
A: 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 remainer of the page.  In real-world documents, the increase in analysis time in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6
to:
A: 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 in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6
Added lines 41-44:
Q: Does PaperCut support color coverage or 3-tired billing (e.g. enhanced/limited color or color coverage)?

A: This topic is addressed in detail in TieredBillingAndColorCoverage .

Changed lines 58-59 from:
[-Keywords: colour detection, printer configuration, charging, color page quotas, mono, monochrome -]
to:
[-Keywords: colour detection, printer configuration, charging, color page quotas, mono, monochrome, difference between standard detection and page level detection -]
Changed lines 14-15 from:
The color or grayscale charge is applied at the document level.  It's based on the user's selection/use of the "grayscale" or "black and white only" option in the print preferences panel.  If the user has selected Grayscale, the job will be charged at the discounted rate for black and white, otherwise the document is assumed to be color.
to:
The color or grayscale charge is applied at the document level.  It's based on the user's selection/use of the "grayscale" or "black and white only" option in the print preferences panel.  If the user has selected Grayscale, the job will be charged at the discounted rate for black and white, otherwise the document is assumed to be color. ''Standard Color Detection'' is also known as '''Document Level Color Detection'''.
Changed lines 3-5 from:
Print job '''color detection''' refereed to a process where a different print job cost is charged based on the use color .  Most organizations charge/account more for color jobs because of:

to:
Print job '''color detection''' refers to a process where a different print job cost is charged based on the use color.  Most organizations charge/account more for color jobs because of:

Changed lines 31-32 from:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''' or '''HP/GL''' driver.  These terms referse to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is support in most cases, and some GDI printers can support hardware-level validation (applied after print).
to:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''' or '''HP/GL''' driver.  These terms refer to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is supported in most cases, and some GDI printers can support hardware-level validation (applied after print).
Changed lines 34-35 from:
A: 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 than 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 reasons for this is that as soon as color is found on a page, the color analysis is turned off for the remainer of the page.  In real-world documents, the increase in analysis time in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6
to:
A: 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 remainer of the page.  In real-world documents, the increase in analysis time in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6
Changed line 44 from:
# If some printers can't support page-level color detection, it may make scene to leave it off all printers to ensure there is a standard and consistent charging policy across all devices in the organization.
to:
# If some printers can't support page-level color detection, it may make sense to leave it off all printers to ensure that there is a standard and consistent charging policy across all devices in the organization.
Changed lines 34-35 from:
A: Page-level color detection does add overhead to job analysis.  It's a lot work to search through a document looking at every pixel rather than just page ends/starts.  However in the real world we find that the slowdown in analysis is minimal and not noted by end-users.  The reasons for this is that as soon as color is found on a page, the analysis is skipped for the remainer of the page.  In real-world documents, the increase in analysis time in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6
to:
A: 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 than 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 reasons for this is that as soon as color is found on a page, the color analysis is turned off for the remainer of the page.  In real-world documents, the increase in analysis time in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6
Deleted line 15:
Changed lines 47-48 from:
For more information about how to use and enable page-level color detection, please also read:
to:


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:
Added line 13:
%rfloat%Attach:driver-level-grayscale-option.png
Added line 16:
Changed line 40 from:
Q: Page-level color detection sounds good.  Why would I not use it?
to:
Q: Page-level color detection sounds good.  Why would I NOT use it?
Changed lines 55-56 from:
[-Keywords: colour detection, printer configuration, charging, color page quotas -]
to:
[-Keywords: colour detection, printer configuration, charging, color page quotas, mono, monochrome -]
Changed lines 27-28 from:
Page-level color detection is usually also run in conjunction with hardware page count validation.  The validation works by querying the printer's hardware 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.
to:
Page-level color detection is usually also run in conjunction with [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|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.
Changed lines 3-5 from:
Print job '''color detection''' refereed to a process where a different cost is charged based on the use color in the print job.  Most organizations charge/account more for color jobs because of:

to:
Print job '''color detection''' refereed to a process where a different print job cost is charged based on the use color .  Most organizations charge/account more for color jobs because of:

Added lines 56-57:

[-Image: cc-by-ca by [[http://www.flickr.com/photos/sirihardeland/5432836109/|Siri Hardeland]]-]
Changed lines 30-31 from:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''' or '''HP/GL'' driver.  These terms referse to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is support in most cases, and some GDI printers can support hardware-level validation (applied after print).
to:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''' or '''HP/GL''' driver.  These terms referse to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is support in most cases, and some GDI printers can support hardware-level validation (applied after print).
Changed line 2 from:
to:
%rfloat%Attach:focus-on-print-job-color-detection.jpg
Added line 5:
Changed lines 29-30 from:
A: PaperCut supports page-level color detection for any printer that provides a Postscript, PCL or HP/GL driver.  These terms referse to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is support in most cases, and some GDI printers can support hardware-level validation (applied after print).
to:
A: PaperCut supports page-level color detection for any printer that provides a '''Postscript''', '''PCL''' or '''HP/GL'' driver.  These terms referse to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is support in most cases, and some GDI printers can support hardware-level validation (applied after print).
Changed lines 3-8 from:
Color detection in PaperCut refereed to a process where a different cost is charged based on the use color in the print job.  Most organizations charge/account more for color jobs because of:

* Lease agreements - most leased devices have different "click costs" for color print jobs
* Color jobs use more expensive toner
* Color enabled devices are more expensive to purchase than a plain black & white printer
to:
Print job '''color detection''' refereed to a process where a different cost is charged based on the use color in the print job.  Most organizations charge/account more for color jobs because of:

* Lease agreements - most leased devices have different "click costs" for color print jobs.
* Color jobs use more expensive toner.
* Color enabled devices are more expensive to purchase than a plain black & white printer.
Changed lines 19-20 from:
* images (in all formats, bit depths and compression forms)
* text (including text using embedded True Type fonts)
to:
* images [-(in all formats, bit depths and compression forms)-]
* text [-(including text using embedded True Type fonts)-]
Deleted line 23:
Changed lines 34-37 from:
-->Standard Detection:  315 ms
-->Page-Level Color Detection:  364 ms
-->Difference:  < 1ms per page
to:
||width=50%
||[
-'''Standard Detection'''-]||[-315 ms-]||
||[
-'''Page-Level Color Detection'''-]||[-364 ms-]||
||[-'''Difference'''-]||[-
< 1ms per page-]||
Changed lines 45-48 from:
For more information about how to use and enable page-level color detection, see:


to:
For more information about how to use and enable page-level color detection, please also read:

* [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-color-detection.html|Manual section on printer color detection]]
* [[SupportedPrintersForPageLevelDetection|+]]
* [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|Hardware page count validation]]

Added lines 1-52:
(:title All About Page-Level Color Detection:)

Color detection in PaperCut refereed to a process where a different cost is charged based on the use color in the print job.  Most organizations charge/account more for color jobs because of:

* Lease agreements - most leased devices have different "click costs" for color print jobs
* Color jobs use more expensive toner
* Color enabled devices are more expensive to purchase than a plain black & white printer

PaperCut allows administrators to set a different cost on color vs grayscale (b&w) jobs and will apply these costs based on one of two different methods:

!!!Standard Color Detection:
The color or grayscale charge is applied at the document level.  It's based on the user's selection/use of the "grayscale" or "black and white only" option in the print preferences panel.  If the user has selected Grayscale, the job will be charged at the discounted rate for black and white, otherwise the document is assumed to be color.

!!!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 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:

* images (in all formats, bit depths and compression forms)
* text (including text using embedded True Type fonts)
* vectors
* and other graphics.


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 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.

Q: What printers support page-level color detection?
A: PaperCut supports page-level color detection for any printer that provides a Postscript, PCL or HP/GL driver.  These terms referse to the print language (PDL) used by the printer/driver.  The task of analyzing the stream of data sent to the printer looking for use of color is very complex and for this reason PaperCut only supports well documented printer languages.  Postscript and PCL are standard languages which are publicly documented.  The notable exception are GDI based printers.  Printers using GDI drivers use non-documented and proprietary languages, which are often evolving, and it's not viable to support page-level analysis for these drivers.  (Document-level color detection is support in most cases, and some GDI printers can support hardware-level validation (applied after print).

Q: Will page-level color detection slow printing?
A: Page-level color detection does add overhead to job analysis.  It's a lot work to search through a document looking at every pixel rather than just page ends/starts.  However in the real world we find that the slowdown in analysis is minimal and not noted by end-users.  The reasons for this is that as soon as color is found on a page, the analysis is skipped for the remainer of the page.  In real-world documents, the increase in analysis time in around 10% to 20%.  For example the analysis time of the PaperCut PDF manual (508 pages) in PCL6

-->Standard Detection:  315 ms
-->Page-Level Color Detection:  364 ms
-->Difference:  < 1ms per page

Q: Page-level color detection sounds good.  Why would I not use it?
A: If your printer support 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 some printers can't support page-level color detection, it may make scene to leave it off all printers to ensure there is a standard and consistent charging policy across all devices in the organization.
# Page-level color detection can make it harder for a user to understand/predict a job cost.

For more information about how to use and enable page-level color detection, see:



----
''Categories:'' [[Category.TipsAndTricks|+]], [[Category.Printers|+]]
----
[-Keywords: colour detection, printer configuration, charging, color page quotas -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on October 07, 2014, at 01:55 AM
Printable View   |   Article History   |   Edit Article