This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Nuke: Collect representation files based on Write #3407
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief description
Collect output frames based on Write node file input field instead of guessing based on files in output directory.
Description
Using previous approach expected that output folder contains only output from current state of the write node but didn't handle previous renders with different frame range or different output extensions. New approach is using nuke api to collect all possible output files from write node based on it's current state by evaluating path with each possible frame.
This change fixed bug/removed feature - it is NOT possible that more frames is integrated then Write node has defined with frame start and frame end.
Example: Write node would render 1001-1010, but I could manually hit
Render Local
and render 999-1020. In that case were integrated frames 999-1020, that is not possible now.Testing notes:
Render family
Still frame
CreateWriteStill
plugin inproject_anatomy/imageio/nuke/nodes/requiredNodes/
to use different extension