You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you have in mind and explain what the current shortcomings are?
It would be great if extra shot information from the Ayon database could come into Houdini on a "shot_build" type node or onto the camera when that comes in. (metadata fields)
This information could include but not limited to...
render resoltuion
pixel aspect ratio
work in/out frame range
cut in/out frame range
back plate location on disk (to connect it to the camera back ground)
These parameters could then be connected to the ROP fields.
In LOPs there could be something like this too. Pulling in a sequence on shot data and building out loaders for these. Like Rise FX Solaris tools. https://youtu.be/jpbMbafS9FY?si=PU13Yk8tSviCEbbf
How would you imagine the implementation of the feature?
please see above
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
It would be great if extra shot information from the Ayon database could come into Houdini on a "shot_build" type node or onto the camera when that comes in. (metadata fields)
This information could include but not limited to...
These parameters could then be connected to the ROP fields.
In LOPs there could be something like this too. Pulling in a sequence on shot data and building out loaders for these. Like Rise FX Solaris tools.
https://youtu.be/jpbMbafS9FY?si=PU13Yk8tSviCEbbf
How would you imagine the implementation of the feature?
please see above
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: