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

Metadata manifest has way more objects than the ones visible in camera. #149

Open
MacbethReyes opened this issue Dec 16, 2021 · 1 comment

Comments

@MacbethReyes
Copy link

Hi ! I have performance issues inside Nuke with scenes with a lot of objects, I guess this is expected, but to my surprise even in shots when only 3 or 4 objects are visible in camera, the manifest includes ALL the objects of the scene 100000 to be exact, is hitting the limit I guess.

Is this normal ? Or is something going wrong in my setup, I was expecting that only the objects inside the frustum of the camera will be inside the metadata manifest.

Anyhow Nuke gets very very slow when this happens, even if the read node is not being used at all, as soon as you put a read node with a huge metadata manifest inside Nuke, it gets slower, my guess is that Nuke is not very good at handling huge metadatas.

Thanks a lot in advance! Any info will be appreciated.

@tanant
Copy link

tanant commented Feb 23, 2022

I'm not sure about the manifest generation, but in Nuke i've seen major slowdown from nuke having to parse large amounts of material in the EXR header (like, 100mb sized exr headers..) irrespective of it being for cryptomatte or for some other data.

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

No branches or pull requests

2 participants