Closed podborski closed 3 months ago
vote up for new 4CC(FourCC) solution
I don't think there is significant effort difference between reworking an existing saiz
implementation and the cut-n-paste that would be involved in making saz2
. So probably not an important consideration.
There is precedent for adding versions to published FullBox
definitions.
I think it depends on whether saiz
is seen as "generally applicable but a mainly a CENC thing". If so, saz2
might be better.
Orthogonal to my previous comment, if there is going to be a new box with per-sample auxiliary information sizes / lengths, maybe it could be called sais
or sail
. Neither of those appears to be registered.
At its previous meeting, the group decided to use versioning.
We noticed that the 8 bit
sample_info_size
limitation in the version=0 ofsaiz
can be problematic . Therefore, we proposed a fix to just extend the range by defining a new boxsaz2
that is equivalent tosaiz
. This is what the current CDAM text defines, it is basically the same assaiz
but with 16 and 32 bits used for the size signaling:At Apple we think that having a new 4CC
saz2
is a bit “safer” than defining a new version=1saiz
as there could be implementations out there that would still try to parsesaiz
version=1 assaiz
version = 0. However, in the file format group, when the issue was discussed, the feedback was a bit different. The group was leaning more towards extending the existingsaiz
as it is defined asFullBox
in the first place and versions field can be used for that. This approach is currently in the TuC.This issue here is just to get more feedback from the industry on the possible implications. Especially since it relates to CENC.