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.

Rename View.Layer_Crypto... to View_Layer_Crypto

This has also been reported in T71574: 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 T68924: OpenEXR pipeline improvements
I wonder if the animation issue has the same roots?

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

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.

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?

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

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

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)?

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?

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

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.

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 T64953: 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...