Page MenuHome

cryptomatte file output produces incorrect matte image
Closed, ArchivedPublic

Description

System Information
Operating system: Windows 10 Pro 64 Bit
Graphics card: GTX 750 TI

Blender Version
Broken: blender-2.80-a813e259d630-win64, master, 2019-04-03

Short description of error
The matte image written to disk is wrong after the file output node is changed

Exact steps for others to reproduce the error

  1. load the file "archiviz5_bugtest1.blend"
  2. render once
  3. change the "File Output" node. Click on "Add Input", connect Depth (or Alpha) from "Render Layers" to Image_002.
  4. render once more. The "Matte" image_001 written to disk now is wrong ("C:\blender-output\Image_0010004.png"). The matte image displayed in blender is still correct however.

If the edited file is saved now and blender is restarted, then the rendering will be correct again

Also, even if the "File Output" node is restored to its previous state (the additional file output is removed),
then the rendering will always be wrong until blender is restarted.

Event Timeline

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.

@Jeroen Bakker (jbakker) feel free to reassign if this is not for you.

@afaenger (afaenger), are you able to reproduce the behavior in a new, smaller file?

No, not tried as I've basically no experience with blender. I've just started to play around a bit and do some tutorials. The file is was downloaded from the 2.8 demo site https://www.blender.org/2-8/

Seems like a color pipeline issue. The matte contains the 'lines' but they are not visible as it is stored in a value buffer (RAW buffer). When connecting a value directly to a color socket the data used as a linear color when displayed the display transform will be put on top. When exporting to PNG the colors are converted to sRGB.


When storing the matte in the Alpha channel of the color it will not be converted and you will see the right information.

I am not able to reproduce the issue you describe. (I was some time ago). Can you check if this is still failing.

Jeroen Bakker (jbakker) lowered the priority of this task from 50 to 30.May 24 2019, 9:42 AM

Tested again with blender-2.80-d525c76003b3-win64 (May 27th) and followed the steps as described above. The issue is still there and the png file written in 4) contains the unexpected lines; the viewer never shows the lines.

With the "set alpha" workaround, the lines don't appear.

Lemme try again.
Result step 1:

Result after step 4:

Both results are identical. The exposure of the file you are using is set to 5.5 what destroys the visual presentation of the data. When set to normal values you will also see the stripes in the viewport.

Is this the same result you get?

Yes, I get the same result in the viewer now if I change the settings to
Scene->Color Management: View Transform=Standard (instead of Filmic), Exposure=0.0 (instead of 5.5)

The stripes are not visible in the viewport if exposure is above ca. 0.7-0.8.

I think I understand now why the stripes are visible/invisible. But why is the behavior not consistent with the steps I described above? Shouldn't be the rendering results always be the same, no matter if I restart the application or add or remove some file outputs?

I am not able to detect any inconsistencies between step 1 and 4. You still are?

Yes, e.g. when exposure is set to 1. The viewport then contains no stripes, the png output contains them sometimes. I think the rendering results should always be the same in order to correctly work with the scene. Basically when using higher exposure values, then the issue appears.

Brecht Van Lommel (brecht) raised the priority of this task from 30 to 90.Jun 7 2019, 11:23 AM
Jeroen Bakker (jbakker) changed the task status from Unknown Status to Unknown Status.Jun 7 2019, 3:07 PM

We are aware of the limitations of blender single channel image pipeline. We intend to solve this in the future were we give users more control on the color spaces.

For now we will close this task as it is not a bug.