Re: [Cellar] AV1 mapping Matroska

[Andreas Rheinhardt <[e-mail]>]

Hello,

I have only just started reading the specification, but I already have
some comments:

1. Your proposal says that DisplayHeight and DisplayWidth must be set so
that they agree with what is said in the CodecPrivate/in the bitstream
so that one can't use the Matroska fields anymore to override what is
set in the bitstream. If I am not mistaken, then AV1 would be unique in
this regard among all the video codecs that are allowed in Matroska. I
don't see a reason for this at all and propose that there shouldn't be a
special treatment for DisplayHeight and DisplayWidth in AV1.

2. Two sequence header OBUs with the same [seq_profile],
[high_bitdepth], [seq_level_idx] and [color_range] can still differ in
the [BitDepth] derived from them due to [twelve_bit]. Therefore I wonder
if this is the right restriction. Wouldn't it be better if it is
demanded that the derived [BitDepth] coincide for every sequence header OBU?

3. Given that AV1 seems to only use one Sequence Header OBU at a time
couldn't one use the CodecState and CueCodecState elements to designate
where the currently active Sequence Header OBU can be found so that one
doesn't need to repeat the Sequence Header with every keyframe?
(Btw: There are currently conflicting recommendations regarding the
existence of Sequence Header OBU if there is actually only one Sequence
Header OBU. On the one hand, they should be omitted, on the other hand
every block marked as keyframe should start with a Sequence Header OBU.)

Andreas Rheinhardt/mkver

PS: This is my first mail to this list and I hope that it will be
presented as a reply to Steve Lhomme's proposed AV1 mapping in Matroska,
but given the fact that I only subscribed today I can't simply reply,
but had to explicitly set the "In-Reply-To" field. Hope it works.