|
|
|
|
|
|
|
|
Issue.JPG (67,717 bytes) |
|
|
The answer is simple. The contributors cared and spend considerable amount of time in making the software support the MVC framework which was honestly not an easy task (on the contrary). This feature is a trivial tweak, primarily relates to a rather extreme case, and obviously has no real implications in the software design. Note that currently, it is far more important extending the JM to support multiple views (>2) than such items. Btw, personally, I think the restriction was a poor choice given that the constraint was originally 16 for the non 3D profiles, and it seems that people still have misconceptions about what is a reference picture in a list and what is a stored reference in the DPB. |
|
|
Hi Alexis, I agree with you regarding the priority for JM developmen towards multiple views support. Regarding the same bug, can bit clarify for the below questions Two clarifications are required w.r.t to the draft version of AVC “ITU-T Rec. H.264 | ISO/IEC 14496-10” ? Value of the mvcScaleFactor, mentioned in the H.10.2 section of the standard mentioned as 2. This value will not get changed based on number of views. What I guess is the value of mvcScaleFactor should be set to the NumViews… right ? ? The max DPB size for 2 Views per frame stream will be equal to 16 [derived based on the equation given in the point f, mentioned in the section H.10.2.1]. So, the max_num_ref_frames will come as 8 per view [point x of the section H.10.2.1]. We are seeing one scenario where in. o 2 Views are present per frame. o After the N th frame decoding, DPB is full. o In the (N+1) th frame decoding, all the views of the frame are unreferenced. [nal_ref_idc = 0 for all the NAL units of the frame]. But the inter_view_flag is ON. o After the decoding of the first view of (N+1) th frame, the view should not be stored in the DPB right? Because what we think is, the DPB is full & the current view is unreferenced, so in this case it should not be stored. But if we do not store it, the second view decoding cannot be done. Is this scenario compliant to standard? ? In 2 view per frame case, can max_num_ref_frames exceed 8 & possess value 9 [8 inter frame & 1 inter-view]? Is this compliant to standard? Regards ~AB |
- Anonymous
