This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Nuke: Slate frame is integrated #3427
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jakubjezek001
approved these changes
Jun 30, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Slate frame is missing in representation files. It is primarilly caused by #3407 but the same issue could happen even before.
Description
Add slate filename to representation files in Extract Slate.
Addiotional information
I've used input with different frame range then write node frame range which caused that slate was not rendered at all (file was rendered but without slate content). Maybe we should force duplicated netflix gizmo to use frame we define as slate frame (e.g. prepend FrameRange/Retime node)?
Testing notes: