System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15
Blender Version
Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-05-10 06:30, hash: rB08a39d32a988
Worked: None
Short description of error
I have reported a bug for RGB blackbody node and the bug report was closed as a duplicate of T68926, then a "fix" was committed: rB029b0df81aa116a3e29f405dc8902834242d5338
But it didn't actually fix the problem. I mentioned it in T68926 but Brecht request me to yet open another bug report.
Here it is.
Exact steps for others to reproduce the error
- Open the config.ocio file with any text editor, change the scene_linear role to any other spaces like XYZ and save file (I know using XYZ space as working space for light transport is a bad idea, this is just for testing purpose to make the problem pop. Any space other than Linear BT.709 should be fine to reveal the problem, just not as obvious).
- Open Blender and open this .blend file:
- Render it and save OpenEXR file. Import it to any software that can show you the imported file's chromaticity diagram, in my case Davinci Resolve:
You see that strange straight line there?
That's the edge of the Rec.709 triangle.
I believe this is due to the incorrect handling of rB029b0df81aa116a3e29f405dc8902834242d5338
Keep the existing Rec.709 fit and convert to other colorspace if needed
This is basically keeping the hardcoded Rec.709 part hardcoded, and add another hardcoded "From Rec.709" transform after it.
I believe the correct way to do it is to use the CIE XYZ for correct chromaticity and convert it to the needed RGB colorspace.


