Compositor File Output node does not preserve cryptomatte metadata #72732

New Issue

Semyon · 2019-12-27T16:41:58+01:00

Semyon commented

2019-12-27 16:41:58 +01:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: Quadro M1000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d4
Worked: (optional)

Short description of error
[cant save cryptomatte data if file saves with "render animation", but can save cryptodata if render wiith f12 and after - save-as rendered file. ]

Exact steps for others to reproduce the error
[1. Open scene. Press render animation or cntrl+f12. 2. Open Nuke, import rendered file. Cryptopasses will broken
3. Press f12 and render. After finish, make Save-as, file format - OpenMultiExr, RGBA, Float, ZIPS and save the file. 4. Open the file in Nuke, Cryptopasses will need to rename matadata.
5. Rename View.Layer_Crypto... to View_Layer_Crypto...]

[Based on the default startup or an attached .blend file (as simple as possible)]
special_shot_281_v011_CRYPTOMATTE.blend

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: Quadro M1000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: `f1aa4d18d4` Worked: (optional) **Short description of error** [cant save cryptomatte data if file saves with "render animation", but can save cryptodata if render wiith f12 and after - save-as rendered file. ] **Exact steps for others to reproduce the error** [1. Open scene. Press render animation or cntrl+f12. 2. Open Nuke, import rendered file. Cryptopasses will broken 3. Press f12 and render. After finish, make Save-as, file format - OpenMultiExr, RGBA, Float, ZIPS and save the file. 4. Open the file in Nuke, Cryptopasses will need to rename matadata. 5. Rename View.Layer_Crypto... to View_Layer_Crypto...] [Based on the default startup or an attached .blend file (as simple as possible)] [special_shot_281_v011_CRYPTOMATTE.blend](https://archive.blender.org/developer/F8242434/special_shot_281_v011_CRYPTOMATTE.blend)

Semyon commented

2019-12-27 16:41:58 +01:00

Added subscriber: @Wizard_Semyon

Jacques Lucke commented

2020-01-14 14:46:14 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-01-14 14:46:14 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Jacques Lucke commented

2020-01-14 14:46:14 +01:00

Is there a way to reproduce this issue just with Blender without having access to Nuke? Maybe by reimporting the files somehow? I don't know.

Semyon commented

2020-01-14 15:12:55 +01:00

In blender cryptomatte is work. But in export in 28+ it is empty. Crypto export work in last version 279. We are very need resolve it - we made a film.

Jacques Lucke commented

2020-01-15 10:50:11 +01:00

Added subscriber: @Stefan_Werner

Philipp Oeser commented

2020-01-15 10:56:45 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-15 10:56:45 +01:00

Rename View.Layer_Crypto... to View_Layer_Crypto

This has also been reported in #71574 (OpenEXR layers from View Layers with names containing a period can't be read by Nuke) but turns out to more of a bug in Nuke then in blender, supporting this is on the TODO, see #68924 (OpenEXR pipeline improvements)
I wonder if the animation issue has the same roots?

> Rename View.Layer_Crypto... to View_Layer_Crypto This has also been reported in #71574 (OpenEXR layers from View Layers with names containing a period can't be read by Nuke) but turns out to more of a bug in Nuke then in blender, supporting this is on the TODO, see #68924 (OpenEXR pipeline improvements) I wonder if the animation issue has the same roots?

Semyon commented

2020-01-15 11:57:12 +01:00

As I know (i dont specialist in it) Nuke and AE have this trouble.
Here people talk about resolve this solution https://devtalk.blender.org/t/cryptomatte-metadata-missing-in-2-8/5546
And i think what a trouble in Blender too - If I bake crypto in open multiEXR vithout node Cryptomatte, the file files will empty. BUT if I do it in 279, files have size 3-4 MB instead empty 0.3KB

As I know (i dont specialist in it) Nuke and AE have this trouble. Here people talk about resolve this solution https://devtalk.blender.org/t/cryptomatte-metadata-missing-in-2-8/5546 And i think what a trouble in Blender too - If I bake crypto in open multiEXR vithout node Cryptomatte, the file files will empty. BUT if I do it in 279, files have size 3-4 MB instead empty 0.3KB

Semyon commented

2020-01-15 11:58:51 +01:00

And when we try using ID masks, antialiasing is no working in Nuke too. We need to resize our dimensions to uo in 5 step and bake.

Philipp Oeser commented

2020-01-15 12:13:44 +01:00

Only had a quick look, but https:*devtalk.blender.org/t/cryptomatte-metadata-missing-in-2-8/5546/47 suggests that updating the Nuke plugin from https:*github.com/Psyop/Cryptomatte fixed the dot/underscore issue?

which version of the plugin are you using?

Only had a quick look, but https:*devtalk.blender.org/t/cryptomatte-metadata-missing-in-2-8/5546/47 suggests that updating the Nuke plugin from https:*github.com/Psyop/Cryptomatte fixed the dot/underscore issue? - which version of the plugin are you using?

Philipp Oeser commented

2020-01-15 12:17:44 +01:00

Also the metadata issue seems to have been fixed on the Psyop side:

https://github.com/Psyop/Cryptomatte/issues/113
https://github.com/Psyop/Cryptomatte/pull/114
https://github.com/Psyop/Cryptomatte/commit/b382d4969b1f

Also the metadata issue seems to have been fixed on the Psyop side: https://github.com/Psyop/Cryptomatte/issues/113 https://github.com/Psyop/Cryptomatte/pull/114 https://github.com/Psyop/Cryptomatte/commit/b382d4969b1f

Semyon commented

2020-01-15 13:11:02 +01:00

Our problem is in missing cryptomatte metadata in exr
Renaming helps when this metadata is present but incorrect. And the new version of the plugin in Nuke probably does fix this, but we have a problem that when rendering without save as in the metadata there is no mention of crypte at all. Even erroneous ones

Our problem is in missing cryptomatte metadata in exr Renaming helps when this metadata is present but incorrect. And the new version of the plugin in Nuke probably does fix this, but we have a problem that when rendering without save as in the metadata there is no mention of crypte at all. Even erroneous ones

Philipp Oeser commented

2020-01-15 14:28:36 +01:00

Changed status from 'Needs User Info' to: 'Confirmed'

Philipp Oeser commented

2020-01-15 14:28:36 +01:00

Added subscriber: @brecht

Philipp Oeser commented

2020-01-15 14:28:36 +01:00

In #72732#849478, @Wizard_Semyon wrote:
Our problem is in missing cryptomatte metadata in exr
Renaming helps when this metadata is present but incorrect. And the new version of the plugin in Nuke probably does fix this, but we have a problem that when rendering without save as in the metadata there is no mention of crypte at all. Even erroneous ones

I think this is due to you using the File Output node.
To quote @brecht from https://devtalk.blender.org/t/cryptomatte-metadata-missing-in-2-8/5546/33

brecht Dec '19
The Blender compositor indeed does not preserve metadata with the file output node, that’s a limitation currently, there is no type of metadata node socket for passing along that information from one node to another.

Maybe you can somehow circumvent using that File Output for the crypto data in your pipeline?

Judging the above comment, will change to "Known Issue".

> In #72732#849478, @Wizard_Semyon wrote: > Our problem is in missing cryptomatte metadata in exr > Renaming helps when this metadata is present but incorrect. And the new version of the plugin in Nuke probably does fix this, but we have a problem that when rendering without save as in the metadata there is no mention of crypte at all. Even erroneous ones I think this is due to you using the `File Output` node. To quote @brecht from https://devtalk.blender.org/t/cryptomatte-metadata-missing-in-2-8/5546/33 > brecht Dec '19 > The Blender compositor indeed does not preserve metadata with the file output node, that’s a limitation currently, there is no type of metadata node socket for passing along that information from one node to another. Maybe you can somehow circumvent using that `File Output` for the crypto data in your pipeline? Judging the above comment, will change to "Known Issue".

Philipp Oeser changed title from ~~cryptomatte error export to nuke~~ to Compositor File Output node does not preserve cryptomatte metadata

2020-01-15 14:29:54 +01:00

Semyon commented

2020-01-15 14:50:04 +01:00

Sorry, I dont have good English and Im not specialist.
We need to make sequence with cryptodata. How we can made it?
When it trouble will resolve (what versions)?

Sorry, I dont have good English and Im not specialist. We need to make sequence with cryptodata. How we can made it? When it trouble will resolve (what versions)?

Philipp Oeser commented

2020-01-15 15:33:57 +01:00

When you dont output crypto via the File Output node, but instead just connect the RenderLayer image to the Composite image, then render your animation as OpenEXR Multilayer, then import those EXRs into Nuke, you should get Metadata, no?

When you dont output crypto via the `File Output` node, but instead just connect the `RenderLayer` image to the `Composite` image, then render your animation as `OpenEXR Multilayer`, then import those EXRs into Nuke, you should get Metadata, no?

Semyon commented

2020-01-15 15:40:48 +01:00

I right do it?
https://yadi.sk/i/ASTVSp-PTerSPA

I right do it? https://yadi.sk/i/ASTVSp-PTerSPA

Semyon commented

2020-01-15 16:12:40 +01:00

We have a second trouble with this scene - blender sometimes forgot passes. For example, I run emission pass, save file, but when open it - emission pass is off.

Philipp Oeser commented

2020-01-16 11:24:53 +01:00

We have a second trouble with this scene - blender sometimes forgot passes. For example, I run emission pass, save file, but when open it - emission pass is off.

Please report this separately (it is not practical chasing different issues in one report)

I right do it?

All I am saying is that you should check the output from Properties Editor > Output Properties tab > Output panel

set your FileFormat to OpenEXR Multilayer and specifiy an output path (resulting images saved there should be OK in regards to metadata)

This is all a bit cumbersome/unfortunate in a bigger pipeline, but this has actually been reported before, see #64953 (Cryptomatte - File Output node is messing up the multilayer exr (metadata), so blender cryptomattes cannot be read properly in external compositors), will have to merge these reports...

> We have a second trouble with this scene - blender sometimes forgot passes. For example, I run emission pass, save file, but when open it - emission pass is off. Please report this separately (it is not practical chasing different issues in one report) > I right do it? All I am saying is that you should check the output from `Properties Editor` > `Output Properties` tab > `Output` panel - set your FileFormat to OpenEXR Multilayer and specifiy an output path (resulting images saved there should be OK in regards to metadata) This is all a bit cumbersome/unfortunate in a bigger pipeline, but this has actually been reported before, see #64953 (Cryptomatte - File Output node is messing up the multilayer exr (metadata), so blender cryptomattes cannot be read properly in external compositors), will have to merge these reports...

Philipp Oeser commented

2020-01-16 11:25:33 +01:00

Closed as duplicate of #64953

Philipp Oeser closed this issue

2020-01-16 11:25:33 +01:00

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

Compositor File Output node does not preserve cryptomatte metadata #72732