[BB PR #29] Fix constant UUID for SEI Userdata Unregistered - #860
Open
Ponsanthini wants to merge 2 commits into
Open
Conversation
When adding SEI Userdata Unregistered with x265pic.userSEI and payload type 5 then the first 16 bytes of the provided payload must be an UUID. However the encoder always prepends its own UUID (x265's identifying GUID) to the payload, shadowing the payload's individual UUID.
Ponsanthini
added
bb-open
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Migrated from Bitbucket PR #29
Author: Ingo Oppermann
State: OPEN
Created: 2024-11-11
Original PR: https://bitbucket.org/multicoreware/x265_git/pull-requests/29
Original Diff: https://api.bitbucket.org/2.0/repositories/multicoreware/x265_git/diff/ioppermann/x265_git:af829ae262dc%0Dcfee9638c82b?from_pullrequest_id=29&topic=true
When adding SEI Userdata Unregistered with x265pic.userSEI and payload type 5 then the first 16 bytes of the provided payload must be an UUID. However the encoder always prepends its own UUID (x265's identifying GUID) to the payload, shadowing the payload's individual UUID.