Photoshop: Bad Prints (saturation)

  • 1
  • Problem
  • Updated 8 years ago
  • Acknowledged
Windows 7 64-bit, CS5 64-bit 12.0.4, Canon Pro9000 MkII.

I just started printing on CS5. I can provide file(s) to duplicate.

I have noticed that CS5 remembers my printer driver settings application wide. I also notice that CS5 saves print settings in each PSD file (photoshop manages and selected profile). This may be contributing to the problem.

I open a file. 16-bit, Prophoto PSD file.
I open the print dialog.
The dialog is defaulted to printer color management for the "bad" files.
Open the printer driver settings. Check the settings. The driver settings are correct. Paper, quality, no color management. Click ok.
Now the dialog changes to photoshop manages colors and the profile selected is some generic canon bubble jet profile.
I select the correct profile. A red river paper profile in this case.

Bad print. The colors with some amount of red in them has the red channel pumped up. Many colors are okay.

Start with a new file (one not worked around).
Open file, change print settings. Close and save file. Open file. Print. Bad Print.

Now the work around.

Start with a new file (one not worked around).
Open file, change print settings. Close and save file. Close photoshop. Open photoshop. Open file. Print. Good Print.

So it seems that my file(s) have some sort of saved print info that is confusing CS5 that persists until the file is saved with current settings and CS5 is closed. I never printed before on this installation so I have no idea what print info could be in the file. I did have a different Canon printer previously installed on this machine but never printed or opened the print dialog in photoshop. Photoshop probably noticed the "default" installed printer even though I never used it.

It is rather annoying to open a file, change print info, close file and photoshop and then reopen for all my files I want to print just to get around this.


  • 33 Posts
  • 5 Reply Likes

Posted 8 years ago

  • 1
Photo of Dave Polaschek

Dave Polaschek, Employee

  • 8 Posts
  • 2 Reply Likes
Official Response
Yes, it's a bug. Sorry. It will be fixed in the future.