search

Psyop / Cryptomatte

Cryptomatte Nuke plugin, Fusion plugin, sample images, and specification
BSD 3-Clause "New" or "Revised" License
640 stars 151 forks source link

Property support blender output with period in Cryptomatte names #104

Closed jonahfriedman closed 5 years ago

jonahfriedman commented 5 years ago

As seen in this ticket:

https://developer.blender.org/T57745

jonahfriedman commented 5 years ago

Fixed in 1.2.4 (but not tested with actual Nuke output, only mocked up with modify metadata)

lukasstockner commented 5 years ago

Here's a Blender/Cycles render of the 2.77 splash screen (source) containing Cryptomattes for testing: blender_cryptomatte_example.zip

caelunshun commented 5 years ago

Still only appears to work with Blender when the view layer is renamed to "scene." This should probably be fixed.

karlisstigis commented 5 years ago

Are there any news? It still doesn't work.

jonahfriedman commented 5 years ago

It was fixed as of 1.2.4, which was months ago.

In the release notes: Fixed gizmo for Blender channel names containing "." which get converted to underscores in Nuke, also fixed for Encryptomatte. (#104)

Could you confirm you're using that version, and send an EXR file that doesn't work in it?

karlisstigis commented 5 years ago

@jonahfriedman Hey, we solved the issue by following a suggestion here: https://github.com/Psyop/Cryptomatte/issues/19

When rendering straight to multipass exr without Compositing, everything works, but the problem appears when using Compositing File Output node in Blender, because the exr file doesn't get the needed metadata.

Although the issue basically is fixed by using the "ModifyMetaData" node in Nuke, I think it would be much nicer if the file just worked. The solution would be to include the same MetaData in exr file if at least one cryptomatte channel is connected to file output node in Blender, but that is a Blenders problem.