Search Results for "JVET-AE0172"

Found 3 document(s)

Search documents

Use number, keyword, author, or MPEG number. Filter by meeting when needed.

31st Meeting: Geneva, CH, July 2023 2023-07-12 17:41
Abstract
This contribution reports an information update on multilayer coding support for VVenC, which is firstly reported in JVET-AB0086, where the initial support of multilayer coding was implemented on VVenC-1.4.0. The base software was updated to VVenC-1.6.1 and the latest results of VVenC-multilayer over VTM-20.2 is reported as follows:
JVET-AE0172 Update on multilayer coding support for VVenC [S. Iwamura, S. Nemoto, A. Ichigaya (NHK)]

This contribution reports an information update on multilayer coding support for VVenC, which is firstly reported in JVET-AB0086, where the initial support of multilayer coding was implemented on VVenC-1.4.0. The base software was updated to VVenC-1.6.1 and the latest results of VVenC-multilayer over VTM-20.2 is reported as follows:

  • Faster BD-rate: {36.69%, 33.07%, 35.95%}, Encoder speedup:170.8x
  • Fast BD-rate: {29.02%, 24.08%, 29.52%}, Encoder speedup: 94.2x
  • Medium BD-rate: {10.59%, 10.54%, 10.37%}, Encoder speedup: 35.4x
  • Slow BD-rate: {5.07%, 4.16%, 3.25%}, Encoder speedup: 10.5x
  • Slower BD-rate: {0.52%, 0.29%, -0.98%}, Encoder speedup: 1.4x

The latest version of multilayer support on top of VVenC-1.6.1 is available at GitHub managed by NHK (https://github.com/nhkrd/vvenc.git).

Decisions
The latest version of multilayer support on top of VVenC-1.6.1 is available at GitHub managed by NHK (https://github.com/nhkrd/vvenc.git).
Citation
31st Meeting: Geneva, CH, July 2023 2023-09-15 12:55
Abstract
This document contains the draft text for changes under consideration for future extensions to the versatile supplemental enhancement information messages for coded video bitstreams (VSEI) standard (Rec. ITU-T H.274 | ISO/IEC 23002-7) to modify existing SEI messages or specify additional SEI messages.
JVET-AE2032 Technologies under consideration for future extensions of VSEI (draft 1) [M. M. Hannuksela, J. Chen, S. Deshpande, S. McCarthy] [WG 5 N 221)] (2023-09-15)

Elements from JVET-AE0061, JVET-AE0298, JVET-AE0064, JVET-AE0079, JVET-AE0095; see detailed notes under these document numbers.

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

Future meeting plans were established according to the following guidelines (assuming face-to-face meetings):

  • Meeting under ITU-T SG16 auspices when it meets (ordinarily starting meetings on the Tuesday or Wednesday of the first week and closing it on the Wednesday of the second week of the SG16 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 cases of online meetings, no sessions should be held on weekend days, such that meetings would typically start two days earlier.

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

  • During Fri. 13 – Fri. 20 October 2023, 32nd meeting under ISO/IEC JTC 1/‌SC 29 auspices in Hannover, DE,
  • During Wed. 17 – Fri. 19 and Mon. 22 – Fri. 26 January 2024, 33rd meeting under ISO/IEC JTC 1/‌SC 29 auspices, to be held as teleconference meeting,
  • During Fri. 19 – Fri. 26 April 2024, 34thmeeting under ITU-T SG16...
Decisions
As a primary goal, the JVET meeting reviewed the work that was performed in the interim period since the thirtieth JVET meeting in producing the following documents:
The meeting was closed at 1215 CEST on 2023-07-19.
Citation
31st Meeting: Geneva, CH, July 2023 2023-07-13 16:29
Authors: Youngkwon Lim
Abstract
An NNPF can be associated with a single purpose and ID within a particular CLVS regardless of its capability. Sometime it might be efficient and useful to reuse NNPF data with new purpose and ID. This contribution propose a new nnpfc_mode_idc for referencing an NNPF already defined with a purpose and ID for new purpose and ID without sending the data again.
JVET-AE0279 AHG9: New nnpfc_mode_idc for reuse of NNPF definition for new purpose [Y. Lim (Samsung)] [late]

This was presented in JVET on Friday July 14.

An NNPF can be associated with a single purpose and ID within a particular CLVS regardless of its capability. Sometime it might be efficient and useful to reuse NNPF data with new purpose and ID. This contribution proposes a new nnpfc_mode_idc for referencing an NNPF already defined with a purpose and ID for new purpose and ID without sending the data again.

(This is related to the discussion regarding disallowing changes of purpose, and “purpose” vs. “capability” as per BoG report JVET-AE0172 v2.)

Several experts saw some inconsistency w.r.t. the concept of updating vs. base.

Further study was requested.

AHG9: SEI messages on topics other than NNPF (13)

Contributions in this area were discussed at 1215–1300 and 1530–1800 on Friday 14 July 2023, and 0900–1225 on Saturday 15 July 2023 (chaired by JRO).

Decisions
Further study was requested.
Citation
New Search