This may be a misunderstanding on my part. My monitor is sRGB with >100nits and max of 12bits of color depth, marketed as HDR. Krita’s manual says the software assumes HDR monitors are >100nits and rec. 2020 color space.
On the page for Scene Linear Painting, it says on non-HDR monitors, enable OCIO through the LUT docker. Most configs of OCIO warp colors pretty drastically and even internal color engine somewhat washes them out.
If it matters, I’m running the .exr through Natron after painting to crunch down to srgb 8bit.
If you intend on doing any image manipulation of any kind outside SDR color ranges, you will not only need to enable OCIO, but you will need to have an .ocio profile. Otherwise, Krita locks the image exposure to 0 Stops, meaning your color pickers will be limited to colors no greater than 1.00. This is regardless of whether you operate with an SDR or an HDR monitor.
As far as simply VIEWING images is concerned, I don’t believe enabling OCIO is strictly necessary to display content. By default (OCIO disabled or set to Internal), I believe Krita will simply clamp any data to what your display can handle using a crude linear transform. This is fine if that’s your intent, but if you, say, render a scene in Blender and save it as an EXR, then opening it up in Krita will cause it to look different, perhaps a lot more intense and sizzled. This is due to Blender coming prepackaged with its own OCIO profile that includes, among other tonemapping styles, the AgX tonemapping algorithm by default.
Colorspace nonsense is basically a giant iceberg so if you have any questions, let me know.
Wonderful! Seems like the manual is a little funky at times, can’t complain much if it’s got me this far, though. Would be nice to see the pages for HDR and LUT management refreshed or something.
Perhaps. It helps if I know more about what you are doing. Is the EXR something you painted? Or did you get it from somewhere else?
I think it’s important to note that OCIO does NOT change the actual image data whatsoever, it simply changes what is sent to the monitor. If you are painting a scene-linear piece of art, and you paint a scene that includes, among other things, a sun that has the brightness of the actual sun itself, OCIO determines how that gets mapped to your monitor, whether it be HDR or SDR, and, depending on the look, the particular visual “flavor” it gets. But if you save it as an EXR, you’re saving the raw, un-tone-mapped data directly, and OCIO plays no part.
I personally paint using the Blender 5.0 OCIO config, which includes multiple tonemapping “looks”, including AgX, ACES 1.3, ACES 2.0, and Un-tone-mapped (or Standard). If I were to give you my project’s .kra file (or an .exr), the only way you’d be able to view it “the intended way” is if you configured OCIO to have the same .ocio config, the same Input Colorspace, and the same Look that I used when drawing. And if you want it to display properly, you’d have to set OCIO’s Display Colorspace to whatever your monitor is (either sRGB for SDR monitors or Krita installations not set up to output HDR, and Rec.2100-PQ for HDR monitors)