could not make it work in fusion
any fusion user here that made it work?
(blender 2.92 beta latest)
i exported object material and asset in a multilayer, then import in loader node then plug to crypto matte node(version 1.2.8)
it will only read object layer, if i try to touch the layer slider the entire cryptomatte node crash, not even the object layer will show again
@Machieb said it worked for him, maybe he can be of assistance.
did you made the connection go through an empty node before feeding it to the file output node?
like in the example Jeroen provided.
Hello,
I tested the file Jeroen provided and it was working in Fusion, Photoshop and After Effects.
Today I made a cryptomatte test with blenders todays build with two of my current 3D projects.
In one project the cryptomatte works with the output node and compositing in fusion. BTW I donĀ“t use the cryptomatte asset option. In the other project it works in one rendered view layer and in another view layer itĀ“s not working. I donĀ“t know why (objects, shader?), so my conclusion is, that it is not 100% working in fusion. I got a new workstation so I testet with Fusion 17 but cryptomatte plugin 1.26 installed via reactor.
What I see, in Photoshop and After Effects it works, mybe the cryptomatte implementation is different there?! I have no Nuke to test it there.
To answer the question about going through an empty group node. I donĀ“t use these group nodes.
I just tested with latest buld (2.92) and it still works in nuke. The first image is from nuke and both cryptoAsset, object and material work fine for me.
In the end I didnāt use reroute or empty groups either and it works just as well.
As the icing on the cake, @p2or was kind enough to share a script he wrote to automatically connect the render layers to file output nodes (there is also a patch awaiting review I think). It is really useful to avoid typing in the names manually (it takes the node label as a prefix, wich is nice)
Hi all,
I need some feedback on some cryptomatte changes that have some consequences. See https://developer.blender.org/D3959
With the new design, the user selects the RenderLayer or Image from which the
Cryptomatte layers are directly loaded (the type of pass is determined by an
enum). This allows the node to automatically detect all relevant passes.
This reduces some flexibility when using cryptomatte layers that are not stored in the same way as blender does. We could still allow the old workflow to ensure this.
Then, when using the eyedropper tool, the operator looks up the selected
coordinates from the picked Image, Node backdrop or Clip and reads the picked
object directly from the Renderlayer/Image, therefore allowing to pick in any
context (e.g. by clicking on the Combined pass in the Image Viewer).
This reduces the need of the pick socket. When done right it could be removed at all.
A technical change is that the cryptomatte isnāt supported in node groups anymore. This is a legacy issue on how nodes store the references to scenes and images. Any feedback is welcome!
on builder.blender.org in the experimental tab you can find compositor-cryptomatte-workflow that includes this new workflow.
I keep checking the experimental branches page, but still seems it is not up yet (mac and linux are there, but I only use Windows). As soon as it is available, I will try it out
There was an issue with the windows build machine. There is now a build available for windows. So check the builder website.
Hi. I have made a couple tests with a simple scene (4 primitives) and:
In NUKE everything seems about the same, tested it wuickly and everything looks normal, the picker works as expected. Soā¦great!
In PHOTOSHOP (using exrIO plugin) each object is split in separated layers. Iām unsure if thatās the usual behavior (Iāve only used Ps/exrIO with renders coming from Maya), but in a large scene it would mean an absurd number of layers, and probably a huge processing time. On the upside, there is no selection required, is literally having a ton of alpha layers split multiple times (obj1.material, obj1.asset, obj1.object, obj2.material, etcā¦).
Then again, I havenāt used it before coming from blender into PS. I tried the same scene with an earlier version of Blender and it does the same thing, so I guess itās working as expected. Maybe @machieb can shine some light.
@JeroenBakker: Sorry I canāt test it, in the build from today (23.02.2021) I canāt find the compositor-cryptomatte-workflow in the experimental tab.
@txo: The behavior in photoshop you subcribe is the way the Exr-IO plugin works/worked.
You are right if you have many objects or shaders in 3D, it ends up in a huge prosessing time and a mass of layers. So if you plan to make compositing in photoshop, you have to think beforehand if you render crypto materials, crypto objects or both of them. 
thanks for explaining, it seemed that way, but I wasnāt sure.
Sorry I canāt test it, in the build from today (23.02.2021) I canāt find the compositor-cryptomatte-workflow in the experimental tab.
The build is in the experimental branches tab whitin the builder page
@machieb it isnāt in the experimental tab. Just try to use the cryptomatte node in the compositor. The changes are all related to how to use cryptomatte within blenders compositor. There wouldnāt be any changes when exporting to an OpenEXR file.
Ah ok thank you very much! I thought it is in the nightly build.
@JeroenBakker: It works great, I have nothing to complain. It is definitely a time saver for users and easier to understand.
Hey, I still seem to be unable to render out cryptomattes correctly and export them to Nuke. Iāve downloaded the test file and exr and they both work fine in nuke. I can also render from the test file and that works fine in nuke also. However when I try and render my own scene I canāt access the cryptomattes in nuke correctly. The metadata looks correct in the render when I check inside of nuke so Iām not sure exactly what Iām doing wrong as far as I can see my blend file is set the same as the test file?
would you mind sharing the .blend file to test it?
Sorry, it isnāt allowing me to upload the blend file. Could you explain how to do that please?
OK, I opened it and it seems all is fine. The issue was thecrypto names in the fileOutput node didnāt have the 00 at the end. It is used in nuke to check how many levels there are per pixel, so it has to be there for the cryptomatte to work properly.
That kind of hassle is why I recommended to use the script by @p2or in a comment before in the thread. It helps a lot with that.
Ahh okay brilliant! That makes total sense thanks!
Hi all,
the new cryptomatte workflow has been committed to master. There is another patch in review (https://developer.blender.org/D10705) that shows the object/material name under the mouse cursor when picking.
