JVET-Y0099 VVC level 4.2 [G. Martin-Cocher (InterDigital)]

This contribution proposes to discuss whether a VVC level 4.2 is needed to address use-cases such as Cloud/Online Gaming as results on some non-CTC 1080p sequences indicates that a bit rate above the main and high tier limit is reached. It may be desirable to rely on a “Main Tier” to address this use-case rather than on a “high tier”.

It was pointed out that the proposal would have the problem that level 5.0 Main tier would not be capable to decode the proposed 4.2 Main tier. A possible solution would be to change the max bit rate in main tier from 50000 to 25000, and changing High tier from 75000 to 100000. This would be the same bit rate as 5.0, but smaller picture size.

Several concerns were expressed about whether such a new level is needed or would be used practically. Further evidence was sought.

Proposed modification of system interface (0)

Section kept as a template for future use.

Low-level tool technology proposals

AHG8: High bit rate and high bit depth coding for VVC (2)

JVET-Y2026 Conformance testing for VVC operation range extensions (draft 3) [D. Rusanovskyy, T. Hashimoto, H.-J. Jhu, I. Moccagatta, Y. Yu] (2022-03-18)

The basis is document JVET-Y0127 which had been reviewed and approved during the meeting.

This was issued as ISO/IEC 23090-15 DAM 1 as WG 5 N 110 (with an editing period as noted).

A DoCR (WG 5 N 109) of the NB comments received in m58554 from the ISO/IEC JTC 1/SC 29 CDAM ballot was reviewed Thursday 20 January in session 24. The NB comments in m58554 generally consisted of requests for editorial improvements or actions already addressed elsewhere in this report or in the report of the 24th meeting.

Future meeting plans, expressions of thanks, and closing of the meeting

Future meeting plans were established according to the following guidelines:

• Meeting under ITU-T SG 16 auspices when it meets (ordinarily starting meetings on the Wednesday of the first week and closing it on the Wednesday of the second week of the SG 16 meeting – a total of 8 meeting days), and
• Otherwise meeting under ISO/IEC JTC 1/‌SC 29 auspices when its MPEG WGs meet (ordinarily starting meetings on the Friday prior to the main week of such meetings and closing it on the same day as other MPEG WGs – a total of 8 meeting days).

In cases where an exceptionally high workload is expected for a meeting, an earlier starting date may be defined. In case of online meetings, no sessions should be held on weekend days. This may imply an earlier starting date as well.

Some specific future meeting plans (to be confirmed) were established as follows:

• Wed. 20 – Fri....