Skip to main content
Known Participant
July 26, 2021
Question

Color banding only in prints made from Lightroom

  • July 26, 2021
  • 1 reply
  • 373 views

In trying to resolve some color management issues (some that are monitor and profiling related) I've also discovered some unexpected behavior. Using a 16-bit aRGB test file that contains linear and graphical color gradients, I get some abrupt color transitions that I don't get when I print the same file from Preview, Photoshop, or Canon's Professional print and layout program for my Pro-1000 printer. I suppose this could be an ICC profile/LrC problem; that same profile worked fine in PS. Other thoughts? A bug?

This topic has been closed for replies.

1 reply

TheDigitalDog
Inspiring
July 26, 2021

Doubt it has anything to do with profiles per se. 

What if instead of sending 16-bit (rendered) images, you try 8-bits per color (considering that's all that's going to the print driver anyway). Also, if you print from a raw, same issue? 

There was a bug in some Epson print drivers that could via a check box, send 16-bit data that didn't when it was not used, so I'm wondering if this could be similar with your Canon. 

Lastly, when issues appear in LRs print module, bast to start from scratch and build a NEW virgin Print Template after correctly resetting everything used to make a print; all LR settings and all print driver settings. The template could be corrupted or setup differently or incorrectly from the other applications. 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
lloyd_pdxAuthor
Known Participant
July 27, 2021

Andrew, thanks for sharing your expertise. (The files I'm using are yours, discovered in another thread and offered up then. Glad to have found them. One is aRGB 16bit, the other is ColorMatch 8bit.) Both files, printed, show the banding/abrupt transitions whether instructed to print in 16 bit or not. I'll next try converting a dupe of the 16 bit file to 8 before printing. 

The template info is intriguing; I won't be surprised if that solves it. Great to know about the possibility of corrupt or incorrect templates.