Search Results for "JVET-AL0061"
Found 10 document(s)
Use number, keyword, author, or MPEG number. Filter by meeting when needed.
JVET-AL0061 AHG 9: Encoder optimization information for AVC and HEVC [C. Kim, H. Tan, J. Nam, J. Lee, J. Lim, S. Kim (LGE)]
The encoder optimization information (EOI) SEI message is used to indicate optimizations that may have been applied during pre-processing or encoding. This SEI message has been developed and incorporated into VSEI V4 draft and also the interface for its use in VVC is available. It is asserted that EOI SEI message can also be used and beneficial for contents coded with codecs earlier than VVC such as AVC and HEVC.
This contribution proposes to include EOI SEI message in the new edition of AVC and HEVC specification.
Agreed in principle to include this. The proposal does not include the restriction concerning QP range of JVET-AL0057 which is asserted to be necessary for both AVC and HEVC.
A merge request for software was already submitted for JM and HM.
ID 215 is proposed to be used for all standards.
Proponents of JVET-AL0057 and JVET-AL0061 are requested to make a joint proposal for texts in AVC and HEVC, and also check if the QP range constraint needs to be implemented in software. A follow-up review based on JVET-AL0061 v2 was done on Friday 4 April (it was reported by proponents that it appeared not necessary to submit a formal joint contribution). This includes text for similar QP range constraints for AVC and HEVC. Checking of the constraint also needs software implementation, and new merge requests will be submitted by proponents of JVET-AL0057.
Decision: Adopt JVET-AL0061v2 for JVET-AL1006 and JVET-AL-1017.
JVET-AL0061 AHG 9: Encoder...
JVET-AP0003 JVET AHG report: Test model software development (AHG3) [F. Bossen, X. Li, K. Sühring (co-chairs), E. François, Y. He, K. Sharman, V. Seregin, A. Tourapis (vice chairs)]
The software model versions prior to the start of the meeting were:
- VTM 24.0 (April 2026)
- VTM-22.2-TuC4.0 (Feb. 2025)
- HM-18.0 (Apr. 2023)
- HM-16.21+SCM-8.8 (Mar. 2020)
- SHM 12.4 (Jan. 2018)
- HTM 16.3 (Jul. 2018)
- JM 19.1 (Apr. 2023)
- JSVM 9.19.15
- JMVC 8.5
- 3DV ATM 15.0 (no version history)
- HDRTools 0.26 (August 2025)
Software for MFC and MFCD is only available as published by ITU-T and ISO/IEC. It is planned to create repositories with the latest versions available in ITU-T H.264.2 (02/2016). All development history is lost.
- Software development
Development was continued on the GitLab server, which allows participants to register accounts and use a distributed development workflow based on git.
The server is located at:
https://vcgit.hhi.fraunhofer.de
The registration and development workflow are documented at:
https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/wikis/VVC-Software-Development-Workflow
Although the development process is described in the context of the VTM software, it can be applied to all other software projects hosted on the GitLab server as well.
Short before the 42nd JVET meeting denial of service was observed on the Fraunhofer HHI web servers, which required blocking large IP spaces. This may also affect legitimate access.
- VTM related activities
The VTM software can be found at
https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/
The software development continued using the GitLab...
JVET-AO0003 JVET AHG report: Test model software development (AHG3) [F. Bossen, X. Li, K. Sühring (co-chairs), E. François, Y. He, K. Sharman, V. Seregin, A. Tourapis (vice chairs)]
The software model versions prior to the start of the meeting were:
- VTM 23.13 (October 2025)
- VTM-22.2-TuC4.0 (Feb. 2025)
- HM-18.0 (Apr. 2023)
- HM-16.21+SCM-8.8 (Mar. 2020)
- SHM 12.4 (Jan. 2018)
- HTM 16.3 (Jul. 2018)
- JM 19.1 (Apr. 2023)
- JSVM 9.19.15
- JMVC 8.5
- 3DV ATM 15.0 (no version history)
- HDRTools 0.26 (August 2025)
Software for MFC and MFCD is only available as published by ITU-T and ISO/IEC. It is planned to create repositories with the latest versions available in ITU-T H.264.2 (02/2016). All development history is lost.
Software development
Development was continued on the GitLab server, which allows participants to register accounts and use a distributed development workflow based on git.
The server is located at:
https://vcgit.hhi.fraunhofer.de
The registration and development workflow are documented at:
https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/wikis/VVC-Software-Development-Workflow
Although the development process is described in the context of the VTM software, it can be applied to all other software projects hosted on the GitLab server as well.
Between the 31st and 32nd meetings, the GitLab server was affected by a huge number of spam issues, which were generated using newly registered accounts. Administrator user account confirmation was enabled to protect the server from spam postings. Proponents should plan for some time for server admins to confirm new accounts.
Between the 37th an...