Re: [Cellar] AV1 mapping Matroska

["Timothy B. Terriberry" <[e-mail]>]

Steve Lhomme wrote:
> You're right. This is a mistake on my part. Instead of MUST it's a
> SHOULD. Because Matroska allows to override the codec internal values
> to display this differently, including changing the aspect ratio or
> forcing physical dimensions. I will change that.

Keep in mind that "SHOULD" tends to have a somewhat stronger force in an 
IETF specification than in normal English. If you're going to use SHOULD 
and not MUST, it is a good idea to explain when someone might reasonably 
violate that SHOULD (if you can't because you can't think of a reason, 
then you want MUST; if you can't because there are too many reasons, 
then you want MAY).

> You mean in my document or the AV1 specs ? My understanding is that
> the AV1 bitstream allow Sequence Header OBUs to be found within the
> stream. And doesn't mention which elements are allowed to change or
> not. Maybe there will be profiles for such restrictions. It won't be

See Section 7.5 "Ordering of OBUs":

"Sequence header OBUs may appear in any order within a coded video 
sequence. Within a particular coded video sequence, the contents of 
sequence_header_obu must be bit-identical each time the sequence header 
appears except for the contents of operating_parameters_info. A new 
coded video sequence is required if the sequence header parameters change."

So the question you want to answer is how what is stored in a Matroska 
file maps to a "coded video sequence". My opinion (as an individual) is 
that a single EBML Document should correspond to a single coded video 
sequence. That means that nothing in the sequence header can change 
(except for the operating_parameters_info).