Skip to content

submit hash_refs for dolby_vision PR in gpac#50

Merged
aureliendavid merged 1 commit intogpac:dolby_visionfrom
DolbyLaboratories:dolby_vision
Feb 24, 2026
Merged

submit hash_refs for dolby_vision PR in gpac#50
aureliendavid merged 1 commit intogpac:dolby_visionfrom
DolbyLaboratories:dolby_vision

Conversation

@MingxinChen
Copy link
Contributor

Updated:

  • hash_refs/bssplit-dv-rpu-agg.hash
  • hash_refs/bssplit-dv-rpu-split.hash
  • hash_refs/dovi-cenc-dash-dash-mpd.hash
  • hash_refs/dovi-cenc-dash-dash-seg.hash

The dby1 brand is now added to the ftyp box for MP4 files containing Dolby Vision streams, which affects the generated file hashes and the range of and

Updated:

  • hash_refs/dovi-cenc-dash-profile.hash

The rpu_present_flag must always be set to 1, in compliance with Dolby Vision Streams Within the ISO Base Media File Format, Version 2.6.

Signed-off-by: Cecilia Chen <Cecilia.chen@dolby.com>
@rbouqueau
Copy link
Member

@MingxinChen Should we merge this one?

@aureliendavid
Copy link
Member

I'm testing a way to test updated hashes with external PRs without touching the tests for master.

Will update here.

@aureliendavid aureliendavid changed the base branch from master to dolby_vision February 24, 2026 11:12
@aureliendavid aureliendavid merged commit 4213ebd into gpac:dolby_vision Feb 24, 2026
@aureliendavid
Copy link
Member

Ok so here's the idea to properly test external PRs that need changes in the testsuite:

  1. open a PR on the testsuite with the needed changes and set the base branch to a branch of the same name as the code PR branch (here dolby_vision)
  2. wait for us to merge this testsuite PR into the local branch
  3. push to the gpac code branch PR

That way, when the buildbot builds the code PR, it sill see a testsuite branch of the same name and run the tests using this branch.

When all is done and ready we should then merge the local testsuite branch into testsuite:master (see #51), and then merge the code branch into gpac:master (gpac/gpac#3431).

(this method also prevent automatically running potentially malicious scripts in testsuite PRs)

So @MingxinChen if you need further hash changes for you PR please follow the 3 steps above.

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants