I have now painfully found out that the Cryptomatte nodes in the compositor make the UI extremely sluggish. But only if you set it to “Image” and use an image sequence with relatively large files (15MB and more). My impression is that - unlike the Image Input Node - the Cryptomatte Node is constantly accessing the disk. The whole thing becomes so slow that it is almost impossible to continue working properly.
Has anyone had this experience too and a solution for it?
Hi! I just created my account to reply. I’m havin the same issue trying to use Blender Compositor with Renderman Cryptomatte and as soon I load the Cryptomatte exr in the Cryptomatte Node the nodetree become slow. It seems something to do with how the data is stored on the exr as I did an render of the same scene with eevee and the cryptomatte loads fine (even if the file is bigger). One workaround that mitigate the issue is to hide node options, then all became fast/normal, it only slows down when the node is selected.