[Mp4-tech] H.264 DPB storage

[Gary Sullivan]

Eric,
Regarding your Question 1, when referring to a bitstream, Annex A
specifies the constraints that must be obeyed by the bitstream; when
referring to a decoder, it specifies the class of bitstreams that the
decoder must be able to handle.
Regarding your Question 2: Your question is somewhat hard to understand.
The basic question seems to have something to do with whether the
confromance requirements are different depending on whether particular
pictures are reference pictures or not.  There is no such distinction
drawn in the standard.  The conformance requirements apply to all
pictures.  Clearly, if some pictures are not decoded properly, the
functional degradation experienced in an application may be less severe
if the pictures that are messed up by a decoder are not reference
pictures (or are higher-level dependent sub-sequences).  However, that
kind of thing is not part of the specification of conformance in the
standard.
Best Regards,
Gary Sullivan
________________________________
	From: mp4-tech-bounces lists.mpegif.org
[mailto:mp4-tech-bounces lists.mpegif.org] On Behalf Of
EricChuang via.com.tw
	Sent: Sunday, February 19, 2024 7:06 PM
	To: mp4-tech lists.mpegif.org
	Subject: [Mp4-tech] H.264 DPB storage
	Hi Experts,
	I have two questions regarding the DPB storage.
	1. The standard specifiy the method to decide the maximum DPB
slot count in Annex A, depending on the level value. Does this level
means decoder level or bitstream level ?
	2. In Annex C, the DPB operation described is used for both
reference picture and non-reference picture, is this an enforcement ? If
I let DPB storing reference picture only, and create another mechanism
for managing non-reference picture, and handle the reoder and
no_output_of_prior_pics_flag, would this cause any decoder conformance
problem ?
	Thanks very much for your answering in advance,
	Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/mp4-tech/attachments/20060220/b559e94a/attachment-0001.html