Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging Cryptomattes #105

Open
midvale99 opened this issue Feb 26, 2019 · 2 comments
Open

Merging Cryptomattes #105

midvale99 opened this issue Feb 26, 2019 · 2 comments

Comments

@midvale99
Copy link

Am I right in thinking that one limitation of Cryptomattes is that you can't merge them? We're rendering some cars using Vray in Maya. We have a car that has its wheels with primary visability set to off and then a set of different wheel renders that we swap out in Nuke. Problem is, the Cryptomattes are visible for the wheels in the car render even though the wheels are hidden in the render. This means that merging over new wheels doesn't work with the Cryptomattes. Is there anyway round this?

@andranikvfx
Copy link

andranikvfx commented Feb 27, 2019 via email

@acjones
Copy link
Collaborator

acjones commented Feb 27, 2019

It's not actually a technical limitation of the way Cryptomattes work, but there is no implementation of a "cryptomerge" currently in the Nuke plugin. The Encryptomatte gizmo does something sort of like a merge, but it only works on one matte at a time. So if you don't have many mattes in the foreground, you might be able to key them and then use Encryptomatte to merge them into the main Cryptomatte layers.

The technical issue that makes it difficult to implement Cryptomerge is that implementing a sort in the form of Expression nodes gets rather ugly. Maybe BlinkScript could be an answer. Otherwise, it would likely be fairly easy to do in a compiled plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants