Skip to content
Snippets Groups Projects
Select Git revision
  • JVET-AJ0234
  • master default protected
  • JVET-AJ0063
  • JVET-AI0061-PROPOSAL1
  • JVET-AI0061-PROPOSAL2
  • JVET-AI0059
  • AH2006-TextDescInformation
  • JVET_AD0067_Proposal2
  • SoftwareDocment
  • JVET-AC0344
  • JVET-AC0062
  • JVET-AC0061
  • AB0058
  • JVET_AA0054_PROPOSAL1
  • AA0055
  • AA0054_PROPOSAL2
  • JVET-V0111_DU
  • Bugfix_Ticket1291
  • JVET_S0184
  • JVET_S0183
  • VTM-4.0.1
  • VTM-4.0.1rc1
  • VTM-4.0
  • VTM-4.0rc1
  • VTM-3.2
  • VTM-3.1
  • VTM-3.1rc1
  • VTM-3.0
  • VTM-3.0rc1
  • VTM-2.2
  • VTM-2.1
  • VTM-2.0.1
  • VTM-2.0
  • VTM-2.0rc2
  • VTM-2.0rc1
35 results
Blame Permalink
Forked from jvet / VVCSoftware_VTM
Loading
README.md 4.81 KiB

VTM reference software for VVC

This software package is the reference software for Rec. ITU-T H.266 | ISO/IEC 23090-3 Versatile Video Coding (VVC). The reference software includes both encoder and decoder functionality.

Reference software is useful in aiding users of a video coding standard to establish and test conformance and interoperability, and to educate users and demonstrate the capabilities of the standard. For these purposes, this software is provided as an aid for the study and implementation of Versatile Video Coding.

The software has been jointly developed by the ITU-T Video Coding Experts Group (VCEG, Question 6 of ITU-T Study Group 16) and the ISO/IEC Moving Picture Experts Group (MPEG Joint Video Coding Team(s) with ITU-T SG 16, Working Group 5 of Subcommittee 29 of ISO/IEC Joint Technical Committee 1).

A software manual, which contains usage instructions, can be found in the "doc" subdirectory of this software package.

The source code is stored in a Git repository. The most recent version can be retrieved using the following commands:

git clone https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM.git
cd VVCSoftware_VTM

Build instructions

The CMake tool is used to create platform-specific build files.

Although CMake may be able to generate 32-bit binaries, it is generally suggested to build 64-bit binaries. 32-bit binaries are not able to access more than 2GB of RAM, which will not be sufficient for coding larger image formats. Building in 32-bit environments is not tested and will not be supported.