Page MenuHome
Create Task
Maniphest T72673

Metadatas differences between scene output and file output node
Closed, DuplicatePublic
Actions

Description

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3
Worked: (optional)

Short description of error
When we are writing .exr with the >Output proprieties> Output > "Path", using the openExr or the OpenExr multilayer, some major metadatas are written (espacially about the cryptomattes channels), and it's good.

When we are writing .exr with the Compositor > File output , we have a lot of thoses metadatas which are not written inside .exr (like cryptomattes informations), and it makes them not properly usable in other softwares like Nuke.

Exact steps for others to reproduce the error
in the same scene, output the scene with an openExr (multichannel or not), and output another openExr (multichannel or not) with a file output using the compositor. The first have plenty of metadatas, the second one, almost any of thoses metadatas

note : Obviously, a part of the problem is from nuke, but it could be very useful to have some consistency between the two kinds of outputs in terms of metadatas

Event Timeline

Yannick Castaing (0_BoUBoU_0) created this task.Dec 24 2019, 2:51 PM
Stephen Swaney (stiv) added a subscriber: Stephen Swaney (stiv).Dec 24 2019, 5:18 PM

Some who actually knows will need to weigh in, but...
I suspect that as a render output, all the Cryptomatte information is available.
In a composite, that information might not exist or might not get propagated thru the node graph.

Evan Wilson (EAW) closed this task as a duplicate of T64953: Cryptomatte - File Output node is messing up the multilayer exr (metadata), so blender cryptomattes cannot be read properly in external compositors.Dec 24 2019, 6:57 PM