See note on JVET-T2010

- Add brace after conditions or loop in order to enclose single line.

implement JVET-S0219,
in order to implement extraction process that is decided to adopt by JVET_S0219, the equation (32) in the SPEC(JVET-S2001_vG) is needed to integrate. for this, JVET-R0193 and JVET-S0141 item47 is also implemented here.
please refer below meeting note for each aspect.
[JVET-S0219] Enable removal of parameter sets (i.e., PPS and APS) in non-output layer that is not used as reference for decoding of pictures in output layers during extraction process

AHG Recommendation (cleanup): Adopt APS aspect only.

[JVET-R0193] Signal max_tid_il_ref_pics_plus1 value separately for each direct reference layer of a layer, i.e. max_tid_il_ref_pics_plus1[ i ][ j ] for each direct reference layer j less than i, instead of single  max_tid_il_ref_pics_plus1[ i ]

AHG Recommendation (cleanup): Adopt. Text was provided in the contribution, and the authors are to supply the software

[JVET-S0141 item 47] In the general sub-bitstream extraction process, specify the conditions under which an output sub-bitstream is required to be a conforming bitstream such that the value of tIdTarget is specified to be in the range of 0 to vps_ptl_max_tid[ vps_ols_ptl_idx[ targetOlsIdx ] ], inclusive (instead of 0 to 6 inclusive)? (JVET-S0158 aspect 1)

Editor action item: The editor is suggested to include this change.

Also fixes #738

Add the config file that is set sps_subpic_same_size_flag equal to 1.
(S0071)

VUI modifications including VUI length, moving two flags from GCI to
VUI, reordering VUI variables to follow syntax elements

Karsten Suehring authored 4 years ago and Frank Bossen committed 4 years ago

- also disable decoder conformance checks that fail for multi-layer streams apparently without valid reason
- rename Picture::layer to temporalId, because temporal ID is stored in this member variable

Chroma QP mapping tables are modified such that the relationship
between luma PSNR an chroma PSNR is on average closer to the
one observed with HM 16.20.
The net effect is that bits are shifted from chroma to luma and
BD-rate differences between VTM and HM are most consistent across
components.

BD-rate between VTM 8.0 and HM 16.20:
AI: -24.09% -31.32% -32.82%
RA: -34.84% -46.33% -46.91%
LB: -30.02% -42.62% -40.94%
LP: -33.12% -44.28% -42.80%

BD-rate between VTM 8.0 plus this change and HM 16.20:
AI: -24.99% -25.35% -26.86%
RA: -35.76% -39.04% -40.03%
LB: -30.56% -32.89% -30.77%
LP: -33.62% -34.86% -32.56%

Fix parsing dependencies in the VUI syntax by moving the
general_progressive_source_flag and general_interlaced_source_flag to
the VUI

- remove picture partitioning section from CTC file (so that they can be combined wit partitioning in any order)
- remove random access parameters from partitioning examples (combines well with AI or LD too)
- add examples for three slices with slice layout inference from subpictures and without
- try to make naming somewhat consistent

- new pattern: create a class to collect all parameters  related to this SEI
- existing code can be refactored to use the same pattern for grouping to avoid endless assignments

Note: fixes executable flags for some unrelated config files