HDR Dynamic Metadata Splitting #1151
Draft
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.
Add HDR Dynamic Metadata splitting for both Dolby Vision RPUs and HDR10+ JSONs.
Related issue: #1005
Implementation
Adds two new parameters:
--dolby-vision-rpu <path>--hdr10plus-json <path>After running scene detection we load the RPU/JSON and split it.
This runs when creating the list
Sceneswhether that is by running scene detection or parsing an exisitingscenes.json.It does not introduce changes to scenes.json, but adds a new field in the internally used
Scenestruct.Todo
scenes.jsonis brokenIt could be that the deserialization is now incompatible withscenes.jsonfiles that don't include the new field.scenes.jsonare made after 7d40165Possible Todos