Page 2 of 4
Re: Proper workflow for cryptomatte
Posted: Wed Dec 11, 2019 12:19 pm
by christiaan
Same here,
The cryptomatte feature is a usefull tool but when comping and re-rendering a pain to work with.
I didn't changed a thing but the animation and when reloading the img seq I can set the comp up from scratch..
Fix the randomization please!
Re: Proper workflow for cryptomatte
Posted: Wed Dec 11, 2019 10:09 pm
by frankmci
KeeWe wrote:No, I just started the rendering again. If I can spare some time, I'll try some scenarios.
But even if I change the Objects or material count, isn't it possible to maintain the already given color plaette? Say my scene is finished but the client wants one more treet far in the back. I think its a no go if adding the object screws up my entire Postwork I already did, there has to be a solution. I can't believe big studios could work with this limitation.
Maybe other users could share there experiences with cryptomattes...?
aoktar wrote:
I didn't see this case on my sample scenes. Have you changed the count of objects in the scene while rendering?
Yup, I can confirm this. Simply re-sending the exact same scene to Octane generates completely new Cryptomatte colors. It's quite a pain having to re-assign the mattes every time a new render is updated in AE, so for the most part, we don't bother with Cryptomatte.
Here's a sample for what it's worth, Ahmet.
Re: Proper workflow for cryptomatte
Posted: Wed Dec 11, 2019 10:56 pm
by aoktar
What happens if you cyrptoMaterialNodeName pass? You should have unique material names for so it can match passes by material names.
Re: Proper workflow for cryptomatte
Posted: Thu Dec 12, 2019 2:52 am
by jayroth
The point is, the colors should not change. If you have any experience with a compositing workflow in production, it is all about the speed. Color picking simply goes faster than matching names for many artists, and that is why there has been such an uproar over this not working as expected. Is the issue within the plug in or standalone?
Re: Proper workflow for cryptomatte
Posted: Thu Dec 12, 2019 5:52 am
by aoktar
jayroth wrote:The point is, the colors should not change. If you have any experience with a compositing workflow in production, it is all about the speed. Color picking simply goes faster than matching names for many artists, and that is why there has been such an uproar over this not working as expected. Is the issue within the plug in or standalone?
What's your objection here? You can be sure names unique and use this pass, even with one click by a script. It's still much faster and better than object Id things. Uproar because nobody try to show the issue by some samples and good explanation
Re: Proper workflow for cryptomatte
Posted: Thu Dec 12, 2019 8:44 am
by christiaan
If one should render out a cryptomatte pass and uses it for compositing it is all ok. Works great, a bit slow but great.
Should there be for some reason be a change in for example the animation, a rerender is needed...one can NOT replace the new rendered result in post
because cryptomatte randomized the colors in another way than the first render. So you have to pick the mattes again in after effects/nuke/fusion.
That can be avoided I guess.
Re: Proper workflow for cryptomatte
Posted: Fri Dec 13, 2019 2:01 pm
by BCres
Did you guys try Ahmet's suggestion of using CryptoMaterialNodeName? My results confirm both what you all are seeing and what he is suggesting.
I tested this by rendering one frame of Frank's project and then the next as a separate render.
CryptoMaterialNode - different colors and selection numbers in AE
CryptoMaterialNodeName - identical colors and selection numbers in AE
Re: Proper workflow for cryptomatte
Posted: Fri Dec 13, 2019 2:32 pm
by aoktar
BCres wrote:Did you guys try Ahmet's suggestion of using CryptoMaterialNodeName? My results confirm both what you all are seeing and what he is suggesting.
I tested this by rendering one frame of Frank's project and then the next as a separate render.
CryptoMaterialNode - different colors and selection numbers in AE
CryptoMaterialNodeName - identical colors and selection numbers in AE
Yes! Unfortunately, me and team have a lot of things to do. This is unnecessarily long discussion I believe. Without giving enough information and don't try different ways that should be avoided.
CryptoMaterialNodeName should be way to GO, avoid to use
CryptoMaterialNode until we fix it if possible. It's not keeping IDs between sessions. Don't know if possible to fix.
Also do not activate many crypto passes. Having a lot that can cause slow down the AE. Let's finish this topic and concentrate to work
Re: Proper workflow for cryptomatte
Posted: Fri Dec 13, 2019 3:32 pm
by KeeWe
Also do not activate many crypto passes. Having a lot that can cause slow down the AE.
Can you expplain what you mean by that? Whats the suggested settings inside the render pass settings? I always thought having the ability to select ALL materials in post is the big advantage.
Re: Proper workflow for cryptomatte
Posted: Fri Dec 13, 2019 3:35 pm
by aoktar
KeeWe wrote:Also do not activate many crypto passes. Having a lot that can cause slow down the AE.
Can you expplain what you mean by that? Whats the suggested settings inside the render pass settings? I always thought having the ability to select ALL materials in post is the big advantage.
Just select one or two render passes if it's enough to work. Having all crypto passes are activated that causes slowing down the After Effects while working. It's for faster work-flow in compositing software. I may be wrong but it's my impression from AE.