International organisation for standardisation organisation internationale de normalisation

3DV standards development (incl. software, conformance) (10)

1. MVC plus depth (2)

14.1.1.1.1.1.1.1.153JCT3V-F0095 Editor's proposed draft text of MVC plus depth conformance [T. Suzuki, D. Rusanovskyy]

Updated text has been reviewed, plan to issue FDAM text at this meeting.

14.1.1.1.1.1.1.1.154JCT3V-F0172 AHG12: MVC+D reference software and conformance bitstreams update [U. Hakeem, A. Norkin (Ericsson)]

The contribution proposes to update the MVC+D reference software with implementation of 3D reference displays information SEI (a part of MVC+D). The contribution also proposes to include a conformance bitstream that uses the reference display information SEI message. The generated bitstream and the reference software implementation are based on 3D-ATMv9.0.

There was support to include the SEI message in the software.

It seems unnecessary to include the SEI message as an integral part of conformance testing. It may optionally be included in a conformance bitstream, but should not be a target of conformance testing since the SEI message does not invoke any normative behavior.

Decision(SW): Adopt.

2. 3D-AVC (5)

14.1.1.1.1.1.1.1.155m31494 Summary of Voting on ISO/IEC 14496-10:2012/DAM 3 [SC 29 Secretariat]

Ballot comments reviewed

USNB #4 Usage of avc_3d_extension_flag was discussed

It was clarified that the base view and its depth map have NALU type 21 and this flag is 0. They are decodable by MVC+D decoders

Some editor’s comments to be resolved, particularly related to texture depth packing.

Further review Thursday morning.

Fin#3 (collect all depth parameters in DPS) no objection, accepted.

Fin#4 (investigate NBDV for other view configurations, or replace it by something else).

Include other configurations in conformance testing.

Fin#5 Text to be provided in input contribution

Fin#6 New title annex J “Multiview and depth video with enhanced non-base view coding.”

From further review on Thursday:

• 
  Software and text require alignment in BVSP. Offline activity (L. Zhang) to report back what the issue is and what exactly is to be changed. Further review based on JCT3V-F0268.
  
• 
  Review of depth_view_info SEI (which was renamed into texture_depth_view_packing SEI) – further review was done Friday morning as recorded below
  

14.1.1.1.1.1.1.1.156JCT3V-F0265 Editorial improvements for texture and depth view packing SEI message [Y. Chen, T. Senoh]

Was presented. Further study required to better describe the process of generating the output view, and where to convey the camera parameters for additional views.

Remove from 3D AVC draft, can be done in a later amendment.

14.1.1.1.1.1.1.1.157JCT3V-F0260 MVC+D / 3D-AVC HLS: on MVCD view scalability information SEI message [M. M. Hannuksela (Nokia)] [late]

The contribution proposes a change in the MVCD view scalability information SEI message that reportedly enables the usage of the SEI message for both MVC+D and 3D-AVC bitstreams as well as for bitstreams where some views are coded with MVC+D while others are coded with 3D-AVC.

It is asserted that the flags that are proposed to be invoked were originally reserved for extending when the SEI message was defined (as they had names “reserved”), and that its extension to the 3D-AVC case was missed so far.

14.1.1.1.1.1.1.1.158JCT3V-F0262 A fix to the mismatch of ATM and text for the disparity-based Skip and Direct modes in 3D-AVC [J.-L. Lin, Y.-W. Chen, Y.-W. Huang, S. Lei (MediaTek)] [late]

In current 3D-AVC, there exist a mismatch between the reference software and working draft (WD) which is related to the disparity-based Skip and Direct mode. In the software, the central point of the current block in the dependent view and the derived disparity vector are used to find the corresponding block in the base view. However, in the WD, the description to derive the position is incorrect. Therefore, in this contribution, it is proposed to fix the mismatch.

Decision: Adopt – integrate into 3D AVC text.

Intent to integrate all amendments in new edition, no separate publication, no separate ballot

• 
  3D-AVC Conformance (BoG T. Suzuki): Additional streams for IBP (requires software update), skip flag, video/depth order. Companies responsible for providing streams for tools to provide for both IBP and CTC case.
  

14.1.1.1.1.1.1.1.159JCT3V-F0268 BoG report on BVSP related issues in 3D-AVC [L. Zhang]

It was found lately that during the integration of D0162 a wrong operation was introduced in the software by which in fact BVSP was performed at macroblock level, which was actually intended for 8x8 block level. This may have occurred due to the harmonization between BVSP and inter picture prediction which was made by that time.

Decision (BF): Correct software to enable 8x8 BVSP

Text: Items 1-5: Changes related to the same issue and various editorial clarifications

Item 6 (The signaling of BVSP B_Direct_8x8 mode is missing): To be resolved by disabling BVSP for B direct 8x8.

Item 7 OK.

Item 8 (For BVSP coded 16x8/8x16/8x8 (excluding B_direct_8x8), the whole partition share the same motion vector): Solution asserted to be correct, but may require further study if the prediction for the conventional 8x16 and 16x8 modes is retained identical.

14.1.1.1.1.1.1.1.160JCT3V-F0118 AHG4: Report on 3D-AVC Software Integration of Depth View Info SEI Message [T. Senoh, K. Wakunami, Y. Ichihashi, H. Sasaki, K. Yamamoto (NICT), M. Tanimoto]

This contribution reports on 3D-AVC software integration of depth view info SEI message into ATM9.0.

Reported tables of BD rate performance are questionable in this contribution, as video 0 should not change the rate. Synthesis PSNR may not be very meaningful here, as the global warping involved does not provide pixel accurate reconstruction.

Currently, camera parameters are not included in the bit stream, but conveyed as SW parameters. This needs to be changed – further development required.

3.