Back to Search Document details
20th Meeting: by teleconference, October 2020 2020-10-09 11:47
JCT-VC AHG report: Project management (AHG1)
Abstract
This document reports on the work of the JCT-VC ad hoc group on Project Management, including an overall status report on the project and the progress made during the interim period since the preceding meeting.
JVET-T0021 JCT-VC AHG report: Project management (AHG1) [G. J. Sullivan, J.-R. Ohm]

This AHG report was discussed at 0530 Friday 9 October 2020 (chaired by GJS & JRO).

This document reports on the work of the JCT-VC ad hoc group on Project Management, including an overall status report on the project and the progress made during the interim period since the preceding meeting.

It is noted that, starting from the twentieth JVET meeting, work items which had previously been conducted in JCT-VC will be continued in JVET as a single joint team, as negotiated by the parent bodies. This particularly consists of work on

  • High Efficiency Video Coding (HEVC) and its extensions, the development of associated conformance test sets, reference software, verification testing, and non-normative guidance information,
  • Specification of Coding-independent Code Points (Video) (CICP), and associated technical report(s),
  • Maintenance and minor enhancement work on the Advanced Video Coding (AVC) standard, associated conformance test sets and reference software.

Seven input documents (JVET-T0048, JVET-T0050, JVET-T0051, JVET-T0052, JVET-T0054, JVET-T0075, JVET-T0113) relate to these items. Reports of the 5 AHGs which had been established at the 40th JCT-VC meeting were also submitted to JVET as JVET-T0021 through JVET-T0025. It is suggested to investigate possible merging of former JCT-VC AHGs with JVET AHGs to avoid duplication of efforts.

The JCT-VC email reflector had approx. 1294 subscribers as of 7 October 2020. It is suggested to keep it open, but send an email encouraging users to subscribe to the JVET reflector, and to continue future discussions on issues related to AVC, HEVC, and CICP on the JVET reflector as well.

The output documents from the preceding meeting had been made available at the "Phenix" site (http://phenix.int-evry.fr/jct/) or the ITU-based JCT-VC site (http://wftp3.itu.int/av-arch/jctvc-site/2020_06_AN_Virtual/), particularly including the following:

  • The meeting report (JCTVC-AN1000), posted 2020-10-07
  • High Efficiency Video Coding (HEVC) Test Model 16 (HM 16) Encoder Description Update 14 (JCTVC-AN1002), posted 2020-10-06
  • Errata report items for HEVC, AVC, Video CICP, and CP usage TR (JCTVC-AN1004), posted 2020-10-06
  • Annotated regions and shutter interval information SEI messages for AVC (Draft 1) (JCTVC-AN1006), posted 2020-09-11
  • Usage of video signal type code points (Draft 1 for version 3) (JCTVC-AN1008), posted 2020-10-07

It is suggested to reserve JVET numbers, or a number space, to “living” JCT-VC documents, such as HM, ongoing standards under development, CTC, etc.

Software maintenance for AVC and HEVC generally was progressing according to plans, and should further be continued in JVET.

Since the approval of software copyright header language at the March 2011 parent-body meetings, that topic seems to be resolved.

Released versions of the software are available on the gitlab server at the following URL:
https://vcgit.hhi.fraunhofer.de/jct-vc/HM/-/tags/version_number,
where version_number corresponds to one of the versions described below – e.g., HM-16.22.

Intermediate code submissions can be found on a variety of branches available at:
https://vcgit.hhi.fraunhofer.de/jct-vc/HM/-/branches/branch_name,
where branch_name corresponds to a branch (eg., HM-16.22-dev).

Various problem reports relating to asserted bugs in the software, draft specification text, and reference encoder description had been submitted to an informal "bug tracking" system (https://hevc.hhi.fraunhofer.de/trac/hevc). That system is not intended as a replacement of our ordinary contribution submission process. However, the bug tracking system was considered to have been helpful to the software coordinators and text editors. The bug tracker reports had been automatically forwarded to the group email reflector, where the issues were discussed – and this is reported to have been helpful.

The ftp site at ITU-T is used to exchange draft conformance testing bitstreams. The ftp site for downloading bitstreams is http://wftp3.itu.int/av-arch/jctvc-site/bitstream_exchange/.

A spreadsheet to summarize the status of bitstream exchange, conformance bitstream generation was available in the same directory. It includes the list of bitstreams, codec features and settings, and status of verification.

Decisions
A spreadsheet to summarize the status of bitstream exchange, conformance bitstream generation was available in the same directory. It includes the list of bitstreams, codec features and settings, and status of verification.
Citation