Converting OpenEXR files with negative values crashes Photoshop

  • 1
  • Problem
  • Updated 5 years ago
Attempting to converting a (32-bit floating point) OpenEXR image with negative RGB values (*) to 16 bit reliably crashes Photoshop CS5 & CS6 (both Windows and Mac). Since negative values do not have a straightforward interpretation for color values, we would suggest clamping them to zero.

(*) debug output from scientific tools; a sample file can be downloaded from https://dl.dropboxusercontent.com/u/5...
Photo of stephan mantler

stephan mantler

  • 4 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
Odd, we use EXR files with negative values in Photoshop all the time, without problems - as does the VFX industry. And no, they should not be clamped to zero, since negative color values DO have a straightforward interpretation as color values: out of gamut colors.

Your file opens without any problems on MacOS.
What exactly are you doing that triggers a crash?
Photo of stephan mantler

stephan mantler

  • 4 Posts
  • 0 Reply Likes
Hi Chris, thanks for the reply.

Out of gamut. Of course! Stupid.

I guess that complicates the conversion to 16-bit, which is the problem child:

1. open file
2. Image -> Mode -> 16 Bits/Channel ...
3. wait a second or two [for the preview, I'd guess]
4. --zappo--

Here's a crappy little screen capture:
https://www.youtube.com/watch?v=7rRupQ...

Crash dump / details at:
http://pastebin.com/2HgzRKnm

I just tried converting to 8bpc, and it crashes as well.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
OK, so the problem is in the HDR Toning code.
I think there was a bug like that in 13.0.0, that was fixed in a dot release. But you already have 13.1.2.

I'll have to check our crash database and see if I can find your issue there (to get all the resolved symbols).