Cryptomatte multi-layer exr's don't work in Nuke unless View Layer name is "Scene" #67820

New Issue

Steve Ernst · 2019-07-28T02:03:59+02:00

Steve Ernst commented

2019-07-28 02:03:59 +02:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-24 14:22, hash: 507ffee6e1
Worked: (optional)

Short description of error
I exported a multi-layer exr with cryptomattes for objects and materials multiple times, but couldn't get the Cryptomatte node in Nuke to recognize any cryptomatte information. After searching for a solution, I found this (https://blender.stackexchange.com/questions/129538/how-can-i-render-cryptomatte-pass-for-nuke) in which the #1 solution is to change the View Layer's name to "Scene". So I tried that, having exhausted all other alternatives, and by jove, it worked perfectly. So what this means is, you can currently only export cryptomattes (that will work in Nuke) from one single View Layer, and that View Layer had better be named "Scene" or you're screwed. Not sure if that's an issue on the Blender side, or if the developers of the Cryptomatte plugin need to work on that, but I figured I should bring it up.

Exact steps for others to reproduce the error
Render any scene with Cryptomatte and the default view layer name, save as a multi-layer exr with ZIP compression, import into Nuke, connect Cryptomatte node, and see that the dropdown doesn't see any cryptomatte information. Try again with view layer named "Scene" and watch the magic.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-24 14:22, hash: `507ffee6e1` Worked: (optional) **Short description of error** I exported a multi-layer exr with cryptomattes for objects and materials multiple times, but couldn't get the Cryptomatte node in Nuke to recognize any cryptomatte information. After searching for a solution, I found this (https://blender.stackexchange.com/questions/129538/how-can-i-render-cryptomatte-pass-for-nuke) in which the #1 solution is to change the View Layer's name to "Scene". So I tried that, having exhausted all other alternatives, and by jove, it worked perfectly. So what this means is, you can currently only export cryptomattes (that will work in Nuke) from one single View Layer, and that View Layer had better be named "Scene" or you're screwed. Not sure if that's an issue on the Blender side, or if the developers of the Cryptomatte plugin need to work on that, but I figured I should bring it up. **Exact steps for others to reproduce the error** Render any scene with Cryptomatte and the default view layer name, save as a multi-layer exr with ZIP compression, import into Nuke, connect Cryptomatte node, and see that the dropdown doesn't see any cryptomatte information. Try again with view layer named "Scene" and watch the magic.

Steve Ernst commented

2019-07-28 02:03:59 +02:00

Added subscriber: @steveernst117

Aditia A. Pratama commented

2019-07-28 13:46:02 +02:00

Added subscriber: @AditiaA.Pratama

Stephen commented

2019-08-06 10:24:49 +02:00

Added subscriber: @stephenwongdesign

Steffen Dünner commented

2019-10-08 14:26:31 +02:00

Added subscriber: @SteffenD

Rainer Trummer commented

2019-11-12 16:15:24 +01:00

Added subscriber: @RainerTrummer

Rainer Trummer commented

2019-11-12 16:15:24 +01:00

This is due to the PsyOp Cryptomatte Plugin for Nuke not handling the Metadata names correctly. The latest version of the plugin should work already (issue was caused by the space in "View Layer"). However, there are other cases that still don't work (like "." in the View Layer name, or a VL name starting with a digit). See this discussion here for reference.

This is due to the PsyOp Cryptomatte Plugin for Nuke not handling the Metadata names correctly. The latest version of the plugin *should* work already (issue was caused by the space in "View Layer"). However, there are other cases that still don't work (like "." in the View Layer name, or a VL name starting with a digit). See [this ](https://developer.blender.org/D5232)discussion here for reference.

Richard Antalik commented

2020-01-06 11:15:54 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-01-06 11:15:54 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Richard Antalik closed this issue

2020-01-06 11:15:54 +01:00

Richard Antalik self-assigned this 2020-01-06 11:15:54 +01:00

Richard Antalik commented

2020-01-06 11:15:54 +01:00

@steveernst117 Thanks for report!

Since this is problem of a plugin for external software, I am closing this report

@steveernst117 Thanks for report! Since this is problem of a plugin for external software, I am closing this report

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cryptomatte multi-layer exr's don't work in Nuke unless View Layer name is "Scene" #67820