The Scalable Video Technology for AV1 Encoder (SVT-AV1 Encoder) is an AV1-compliant encoder library core. The SVT-AV1 development is a work-in-progress targeting performance levels applicable to both VOD and Live encoding / transcoding video applications.
SVT-AV1 Encoder is licensed under the OSI-approved BSD+Patent license. See LICENSE for details.
More details about the SVT-AV1 Encoder usage can be found under:
SVT-AV1 Encoder may run on any Windows or Linux 64 bit operating systems. The list below represents the operating systems that the encoder application and library were tested and validated on:
Windows* Operating Systems (64-bit):
Linux* Operating Systems (64-bit):
Ubuntu* 16.04 Server LTS
Ubuntu* 18.04 Server LTS
Unix* Operating Systems (64-bit):
The SVT-AV1 Encoder library supports the x86 architecture
In order to achieve the performance targeted by the SVT-AV1 Encoder, the specific CPU model listed above would need to be used when running the encoder. Otherwise, the encoder runs on any 5th Generation Intel® Core™ processor, (Intel® Xeon® CPUs, E5-v4 or newer).
Resolution | 8-vCPU Commit Size (GB) | 40-vCPU Commit Size (GB) |
---|---|---|
4k | 14 | 24 |
1080p | 6 | 10 |
720p | 4 | 7 |
480p | 3 | 5 |
Build Requirements
Build Instructions
Binaries Location
Installation
For the binaries to operate properly on your system, the following conditions have to be met:
Build Requirements
Build Instructions
Sample Binaries location
Installation For the binaries to operate properly on your system, the following conditions have to be met:
We welcome community contributions to the SVT-AV1 Encoder. Thank you for your time! By contributing to the project, you agree to the license and copyright terms in the OSI-approved BSD+Patent license and to the release of your contribution under these terms. See LICENSE for details.
Follow the coding guidelines
Validate that your changes do not break a build
Perform smoke tests and ensure they pass
Submit a pull request for review to the maintainer
Use the "Issues" tab on Github. To avoid duplicate issues, please make sure you go through the existing issues before logging a new one.
The notices and disclaimers can be found here