Skip to content

Conversation

@todd-n
Copy link

@todd-n todd-n commented Dec 23, 2019

Add explanation for MaxTileHeightSb limits when non-uniform/explicit tiles are used.
Based on discussion from:
https://bugs.chromium.org/p/aomedia/issues/detail?id=2559&q=

Add explanation for MaxTileHeightSb limits when non-uniform/explicit tiles are used.
Based on discussion from:
https://bugs.chromium.org/p/aomedia/issues/detail?id=2559&q=
@imoccaga
Copy link

What is the reason for this restriction, and does this restriction cause existing encoder / bitstreams to become non-legal ?

@peterderivaz
Copy link
Contributor

@imoccaga The change is in a note. Notes do not affect the normative decoding process but try to provide additional context or explanation for the reader.

This note does not add a restriction, but tries to explain the reason for a restriction that is already present in the specification.

Therefore it would not cause existing encoder / bitstreams to become illegal.

Personally, I think the note is helpful and would be happy for it to be included, but it is up to the editors to decide whether it is significant enough to be worth updating.

@imoccaga
Copy link

I missed the "Note:", thanks.

I suggest some additional people take a look to confirm that this note is technical correct.

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