[Printing-architecture] Make use of extended color spaces on IPP printers
till.kamppeter at gmail.com
Sat May 29 19:19:56 UTC 2021
Thank you very much.
Not having any files in AdobeRGB I have shot a photo in JPEG, setting
the camera (Olympus PEN F) to AdobeRGB and shot another photo with the
standard sRGB setting.
The sRGB picture contains "ColorSpace: sRGB" in its EXIF data (section:
Photograph Information"), as you told, so it can easily be identified as
The AdobeRGB picture has "ColorSpace: Uncalibrated", so something
similar to the "Other" which you told, and in the "Image Information"
section now appears an entry "Primary Chromaticities: 64/100 33/100
21/100 71/100 15/100 6/100" which are exactly the 6 numbers for Red
Green, and Blue in the chromaticities table on
The 2 numbers for White in this table also appear in the EXIF data, as
"White Point: 313/1000 329/1000", also under "Image Information".
Note that I did not use the "official" EXIF standard via the link
as it seems to be some proprietary format presented in some reader which
has a Japanese-only UI, even for the English version of the document.
So one can identify the picture as AdobeRGB in the ugly way you
describe, but it seems that the EXIF standard does not actually support
AdobeRGB, even that cameras have this sRGB/AdobeRGB switch in their
menus for decades (probably from the beginning of digital photography, I
think my Canon IXUS 400 of the early aughties had it already).
But there is still the question whether this works with the AdobeRGB
pictures of all cameras or only of some of them. I really do not want to
have an AdobeRGB-identification quirk list for digital cameras (and phones).
Only there is also one thing: If you print a JPEG picture right away
from the command line, it does not get filtered at all, due to this line
in the auto-generated PPD files:
*cupsFilter2: "image/jpeg image/jpeg 0 -"
So the printer takes care of however you set your camera in the hope to
get the best image quality.
So it seems to be more important to identify AdobeRGB in raster-only
PDFs, for example if you print a photo from a photo manager or editor
and here it probably depends on what the user sets in the print settings
whether the PDF is AdobeRGB or sRGB. digikam allows turning on color
management in the print dialog and the select from a long list of
standard color spaces (includes sRGB and AdobeRGB) or with custom color
profile, but one does not know whether a JPEG image in AdobeRGB gets out
as a raster PDF in AdobeRGB without converting forth and back when one
selects AdobeRGB for printing.
It seems not to be easy to make use of the fact that a printer supports
AdobeRGB as input (sRGB probably serves 99.9 % of all printing needs).
Did you already try this out somehow? Do you really get better output
quality by that? And if you tried it, how did you do so?
So I am a little bit in doubt how important the support for the
printer's AdobeRGB is and how best to support it.
On 28/05/2021 14:59, Michael Sweet wrote:
>> On May 27, 2021, at 2:04 PM, Till Kamppeter <till.kamppeter at gmail.com> wrote:
>> If I look into the source code of the pclmtoraster filter of cups-filters (cupsfilters/pclmtoraster.cxx) I see that when readin the embedded bitmaps from a PDF file there only occur /DeviceGray, /DeviceRGB, and /DeviceCMYK color spaces. How do I determine whether I have sRGB or AdobeRGB? Vikrant?Ans what is the default/IPP/PWG-standard color space of /DeviceCMYK?
> Assume sRGB/sGray - pclm was intended as a format for entry-level HP laser printers. DeviceCMYK is CUPS_CSPACE_CMYK (no associated profile, always a device color space).
>> Also, if I have images (JPEG, TIFF, PNG, ...) how do I know which coloe space they are? imagetoraster seems not to determin whether images are sRGB or AdobeRGB.
> EXIF (used for both JPEG and TIFF) includes several tags related to color space, starting with ColorSpace (sRGB or "other") and then using PrimaryChromaticities (sic) for the "other" color space to match it with the AdobeRGB primaries.
> For PNG you need to look at the cHRM chunk to compare primaries:
> If the file doesn't have this chunk, assume sRGB.
> Michael Sweet
More information about the Printing-architecture