Skip to main content
fredl11600511
Inspiring
February 21, 2019
Answered

Bitmap showing as CMYK color space in preflight

  • February 21, 2019
  • 4 replies
  • 3159 views

Following the advice now being given about when best to convert the RGB color space to CMYK for printing, I changed my preflight defs to flag images which are CMYK prior to ripping to PDF. But preflight is categorizing bitmap images, which show as "black and white" in the links panel (and are truly bitmap when opened in Photoshop) as having a CMYK color space. How can this be?

    This topic has been closed for replies.
    Correct answer rob day

    The issue I'm focused on is not the export; it's preflighting: using preflight conditions to easily find images placed as CMYK and correct them to RGB, since experts are now saying that InDesign's conversion from RGB to CMYK for print production is the best way to go (rather than converting in, say, Photoshop). Since preflight can't distinguish between the CMYK black that bitmap uses and actual CMYK images (using 4 colors), preflighting for this condition is pointless. If InDesign had an option to use an RGB black as the default black, the issue would be solved. So it's not an issue to be solved, apparently, at this point; it's just a limitation for using Preflght.


    If InDesign had an option to use an RGB black as the default black, the issue would be solved. So it's not an issue to be solved, apparently, at this point; it's just a limitation for using Preflght.

    It does: Document Setup>Intent set to Web or Mobile will convert default [Black] and other CMYK swatches to RGB.

    But I think you are taking the RGB advice too literally. In the case of 1-bit Black and White images that you want to print as black on press, assigning an RGB black to the bitmap means the image will print as 4-color. The conversion of RGB black will be to the CMYK profile’s maximum black point. So for default SWOP the conversion will be something like this, which could easily cause a registration nightmare on press for 1-bit line art. Similarly you would never want to use an RGB black for small text:

    Also once an image is converted to CMYK converting it back to RGB has little or no benefit because the damage has been done. At that point you might as well allow a CMYK-to-CMYK conversion in the RIP.

    Placing RGB is more of a convenience than a necessity—it allows you to wait until the final press destination is known before making a device dependent conversion. If the placed CMYK file was converted using the correct press profile, there would be zero need to go back to RGB.

    4 replies

    Legend
    February 25, 2019

    "But InDesign doesn’t have a distinct K space. For print intent documents, [Black] is actually 0|0|0|100 CMYK, and not 100%K"

    But it doesn't need to be distinct space, InDesign is more than capable of checking the other channels are zero.

    fredl11600511
    Inspiring
    February 25, 2019

    I want to thank all of you for taking the time, making the effort to reply in detail as you have. It's been helpful and an education. I do think the preflight could be made more useful so that users can ferret out mixed color spaces (e.g., some CMYK, some RGB) in a document without being concerned that bitmap black is being picked up as CMYK when it is only K; it would seem that the conversion results would then at least be uniform, since it would be applied at whatever stage (e.g., InDesign, Pit Stop) to all images, not just the ones not already converted to CMYK.

    rob day
    Community Expert
    Community Expert
    February 25, 2019

    I do think the preflight could be made more useful so that users can ferret out mixed color spaces (e.g., some CMYK, some RGB) in a document without being concerned that bitmap black is being picked up as CMYK when it is only K;

    But InDesign doesn’t have a distinct K space. For print intent documents, [Black] is actually 0|0|0|100 CMYK, and not 100%K.

    Protecting [Black] from a conversion can be handled on export by setting the Color Conversion to Convert to Destination (Preserve Numbers).

    That option protects all native CMYK colors and swatches, but converts any RGB colors, or CMYK objects with conflicting embedded profiles to the chosen Destination space.

    If for some reason you wanted to force a CMYK-to-CMYK conversion of native swatches and colors, while still protecting the default  [Black] swatch, that can be done via Edit>Convert to Profile...

    Derek Cross
    Community Expert
    Community Expert
    February 21, 2019

    In InDesign choose PDF/X-4 to convert your RGB images to CMYK.

    Also tick, in the Export Adobe PDF dialogue box, Crop Marks and Use Document Bleed Settings.

    (Unless your printer has given you a different spec.)

    Community Expert
    February 21, 2019

    Hi fredl11600511 ,

    what is the document intent?

    Is it print intent? Then it's correct that your preflight is showing an error.

    If the intent of your document would be Web Intent or Mobile Intent your preflight would not throw an error on [Black].

    What can you do?
    Create a swatch with RGB 0,0,0 and color your bitmap graphic with that.

    Regards,
    Uwe

    fredl11600511
    Inspiring
    February 21, 2019

    The intent is offset printing.

    The images are bitmap in Photoshop, black on or off.

    So you're saying that preflight does not recognize bitmap images--an image has to be either RGB, CMYK, spot, Lab or gray? And this is because the default Black in InDesign is CMYK and not RGB? If today's InDesign does a better job than Photoshop of converting RGB to CMYK in ripping PDFs, then why doesn't it have the option of a RGB black? It would seem that the current setup defeats the purpose of preflight, because you can't effectively preflight for CMYK images.

    Community Expert
    February 21, 2019

    Hi fredl11600511 ,

    InDesign does not convert any placed bitmap images.

    It applies a color to the bitmap image.

    That color, by default, is [Black].

    If [Black] is defined with color space CMYK, and this is the case with every document that is created with Print Intent, your preflight that is defined to flag CMYK elements, will throw an error. That's no bug.

    Regards,
    Uwe