Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New PicParamSetId to perform proper bounds check #64

Merged
merged 1 commit into from
Feb 27, 2024

Conversation

dholroyd
Copy link
Owner

Using a single ParamSetId had the problem that Ids for pic_parameter_set and seq_parameter_set have different maximum allowed values. This change removes that original type and replaces it with seperate PicParamSetId and SeqParamSetId types.

SeqParamSetId enforces a limit of 31 as before, but PicParamSetId enforces a limit of 255.

Fixes #56

@dholroyd dholroyd force-pushed the pic-param-set-id-bounds-check branch 2 times, most recently from ebe2468 to 10fd58b Compare February 27, 2024 18:39
Using a single ParamSetId had the problem that Ids for pic_parameter_set
and seq_parameter_set have different maximum allowed values.  This change
removes that original type and replaces it with seperate PicParamSetId and
SeqParamSetId types.

SeqParamSetId enforces a limit of 31 as before, but PicParamSetId enforces a
limit of 255.

Fixes #56
@dholroyd dholroyd force-pushed the pic-param-set-id-bounds-check branch from 10fd58b to 6fa1be5 Compare February 27, 2024 19:03
@dholroyd dholroyd merged commit 1c353b1 into master Feb 27, 2024
1 check passed
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.

Wrong Bounds Check for pic_parameter_set_id
1 participant