By the way, that Blender bug won’t affect the GPU denoiser build I provided above, because the GPU denoiser will work when the compositor is set to CPU mode too. Make sure you use the latest one I posted: 🚀 Turbo Tools - Faster Cycles Renders & Compositing! - #861 by Michael_Campbell
@Beautifool_Hueman Worth mentioning too, Blender has never included meta data from the compositor’s file output node (only from files generated by the blender output properties).
I don’t use Nuke personally, but it’s been confirmed to me that the meta data is not essential for cyptomatte usage in Nuke.
I can’t remember exactly what the difference is, so I just asked copilot to re-explain:
can cryptomatte be used without meta data in nuke?
Copilot
Cryptomatte relies on metadata to store information about the objects and their IDs. Without this metadata, Cryptomatte won’t be able to identify and isolate the different objects in the image by name.
However, you can still use the Cryptomatte plug-in in Nuke to select mattes, but you won’t be able to recover the original matte names. In this case, Cryptomatte will add a floating-point value of the selected ID to the Matte List.
I’d recommend using the EXRs created by Turbo Tools and set Blender’s own output to something very light such as ffmpg, you’ll save a ton of disk space, plus Turbo’s output has the additional advantage of being able to denoise the individual passes.
Make sure when outputting data layers such as cryptomatte that you set the output to 32 bit in the Turbo Tools addon preferences, otherwise you’ll be missing information.
1 Like
Wow thank for your effforts !
I have only started learning nuke like half a year ago, so i am still figuring things out. The thing is it worked in Blender 4.1 with the output node and the cryptomatte layers where merged correctly into respective layers, like object, material asset. In 4.2 that was broken using the GPU compositor. Now they fixed it.
Anyways, i just tried with your build in CPU mode and it kind of works. It’s a bit muddled up, but the layers get recognized. So no worries, thank you !
I thought it would be slower in CPU mode, but that seems not to be the case. Blasting through like a charm. I love using that build.
1 Like
No problem 
I hope the Blender developers will add it to the official Blender soon, even if it’s as experimental. Could perhaps do with a few people nudging Omar and Sergey about it to let them know it’s important to enough people to make it worth prioritising 
#115242 - Compositor: Enable GPU denoising for OpenImageDenoise - blender - Blender Projects
Yeah, will do. This should be on top of the list 
(like a million other things)
Honestly this makes so much difference in speed it’s amazing.
1 Like
Hey guys, I’ve made a quick demo of the imminent new GPU compositor denoising, it has a massive impact in some cases:
2 Likes
Oh, and shameless plug, I also released a new addon today if you’d like to check it out:
2 Likes
Last chance saloon for the Blender Market Black Friday - Cyber Monday Sale!