johnegibson2

@nickbatz Thanks for your response. Good to know re: AF print dialog drivers, though I am using Windows and not OSX. I do have the ICC profiles for my papers. I am actually using Canon Pro Lustre paper for this print. My workflow doesn't normally involve printing from PNGs, it was just something I tried that happened to work. I think the problem here is that for 32-bit depth images from e.g. HDR merges, no (reasonable) print driver would accept such a format, but Affinity Photo does not issue a warning or convert to 16-bit before sending to the printer. I would consider this not particularly user-friendly. Maybe this is a feature that could be implemented, or at least a warning could be raised with an "Are you sure?"-style dialog.

I converted the afphoto to 16-bit RGB. This is much closer to what I'd expect, thanks all. Now the question is: where is the communication breaking down? Is this an issue with the printer interpreting 32 bit depth images, or Affinity? I don't know enough about print protocols to answer that

Aha, there is a difference there. The PNG is RGBA/16, the .afphoto is RGBA/32 (HDR). Do you think that could be causing the issue here?

Both documents are sRGB IEC61966-2.1 (although the .afphoto says Linear afterwards, not sure if that makes a difference). @thomaso I should have made this more clear, but my exact process was: 1. open the .afphoto 2. export to PNG 3. open the PNG in Affinity and print with identical settings Other relevant details, perhaps: Color Handling: Performed by App Printer Profile: Built-in Canon profile that matches the paper I'm printing on (Pro Luster) Rendering Intent: Perceptual These were all the same for both prints. Thanks!

The lighter-looking photo is printed using the .afphoto. The darker one is printed from the exported PNG, using exactly the same printer settings on my Canon Pro-300. I'm using 2.04, and this is consistent across other papers as well. Any tips? Could I be doing something wrong?