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
I have searched the existing issues and added correct labels.
Please describe the feature you have in mind and explain what the current shortcomings are?
With #13 we can now load and manage matteshapes and tracker points - however, it assumes that a single node will only ever get one loaded product at most. Even though it may be nicer to allow e.g. importing BOTH tracker points and matte shapes to a single roto node and manage them.
Suggested implementation?
Store the instances as a list of ayon_instances metadata on the nodes. In that metadata also keep track of which objects on the node belong to that particular instance, so that we don't need to remove all child objects on update - but only replace those entries that are tracked and go from there.
Describe alternatives you've considered:
No response
The text was updated successfully, but these errors were encountered:
BigRoy
changed the title
Support loading multiple times / multiple products to one node (as such, support multiple containers per node)
Support loading multiple products to one node
Feb 3, 2025
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
With #13 we can now load and manage matteshapes and tracker points - however, it assumes that a single node will only ever get one loaded product at most. Even though it may be nicer to allow e.g. importing BOTH tracker points and matte shapes to a single roto node and manage them.
Suggested implementation?
Store the instances as a list of
ayon_instances
metadata on the nodes. In that metadata also keep track of which objects on the node belong to that particular instance, so that we don't need to remove all child objects on update - but only replace those entries that are tracked and go from there.Describe alternatives you've considered:
No response
The text was updated successfully, but these errors were encountered: