v2.3.0-B – Community Builds Thread

[BlueSwordM]

Community Builds Thread

This is a place for the community to share unofficial tools not affiliated with the project — mainly consisting of binaries compiled by community members.

Trust

⚠️ Community-built binaries are not affiliated with the SVT-AV1-PSY project & are to be used at your own risk. If you encounter bugs while using a community-built binary, ensure that you double-check with the person responsible for providing you with the binary before submitting an issue report.

Architecture

When downloading pre-compiled binaries, you might see AVX, AVX2, AVX-512, x86-64-v3, etc. If you don't know exactly what ISA extensions your CPU supports, here is a chart to help you quickly understand your hardware's support:

Not Vendor-Specific

x86-64    : Processors lacking SSE4.2 and newer features
x86-64-v2 : Processors with features up to and including SSE4.2
x86-64-v3 : Processors with features up to and including AVX and/or AVX2
x86-64-v4 : Processors with features up to and including AVX512

ISA extensions like AVX, AVX2, & AVX512 are for vector processing which SVT-AV1-PSY relies heavily on for its fast multithreaded performance. Below are some helpful charts to help you narrow down the best options if you have popular x64 hardware:

AMD

Generation                                             Vectors  Build
Zen   (1xxx)                                           AVX2     x86-64-v3 / znver1
Zen+  (1xxxAF-2xxx-3xxxG/H/U/C)                        AVX2     x86-64-v3 / znver1
Zen2  (3xxx-4xxxS/G/H/U-5700U-5500U-5300U-7520U-7320U) AVX2     x86-64-v3 / znver2
Zen3  (5xxx-7330U-7530U-7730U)                         AVX2     x86-64-v3 / znver3
Zen3+ (6xxx-7xxxH/U)                                   AVX2     x86-64-v3 / znver3
Zen4  (7xxx-8xxxG)                                     AVX512   x86-64-v4 / znver4

Intel (Desktop)

Generation                Vectors  Build
Haswell     (4th gen)     AVX2     x86-64-v3 / haswell
Broadwell   (5th gen)     AVX2     x86-64-v3 / broadwell
Skylake     (6th gen)     AVX2     x86-64-v3 / skylake
Kaby Lake   (7th gen)     AVX2     x86-64-v3 / skylake
Coffee Lake (8-9th gen)   AVX2     x86-64-v3 / skylake
Comet Lake  (10th gen)    AVX2     x86-64-v3 / skylake
Rocket Lake (11th gen)    AVX512   x86-64-v4 / rocketlake
Alder Lake  (12th gen)    AVX2     x86-64-v3 / alderlake
Raptor Lake (13-14th gen) AVX2     x86-64-v3 / raptorlake

Included below is even more information about what is available when specifying -march & -mtune on x64 CPUs:

Known valid x64 arguments for -march=:

i386 i486 i586 pentium lakemont pentium-mmx winchip-c6 winchip2 c3 samuel-2 c3-2 nehemiah c7 esther i686 pentiumpro pentium2 pentium3 pentium3m pentium-m pentium4 pentium4m prescott nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d arrowlake arrowlake-s lunarlake pantherlake bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont sierraforest grandridge clearwaterforest knl knm intel geode k6 k6-2 k6-3 athlon athlon-tbird athlon-4 athlon-xp athlon-mp x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 lujiazui yongfeng k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 znver4 znver5 btver1 btver2 generic native

Known valid x64 arguments for -mtune=:

generic i386 i486 pentium lakemont pentiumpro pentium4 nocona core2 nehalem sandybridge haswell bonnell silvermont goldmont goldmont-plus tremont sierraforest grandridge clearwaterforest knl knm skylake skylake-avx512 cannonlake icelake-client icelake-server cascadelake tigerlake cooperlake sapphirerapids alderlake rocketlake graniterapids graniterapids-d arrowlake arrowlake-s pantherlake intel lujiazui yongfeng geode k6 athlon k8 amdfam10 bdver1 bdver2 bdver3 bdver4 btver1 btver2 znver1 znver2 znver3 znver4 znver5

• Note: -march=foo implies -mtune=foo unless you also specify a different -mtune. This is one reason why using -march is better than just enabling options like -mavx without doing anything about tuning.

Antivirus

🛑 Be wary of antivirus software on Windows detecting EXEs distributed here as malicious software. While they may not always legitimately be malicious, it is important to maintain a healthy level of skepticism when running code that someone else has compiled.

[ItachiUchiha-IU]

All the problems listed here #118 (comment) have been addressed and should now be patched
Psy-rd is now extremely different from the previous version!
It would be amazing if u could try the builds and report any problems !

I have briefly tested the builds and everything seems to be working fine with the builds; all my observations so far:

• no crashes
• using --psy-rd now results in files with the same size every time u encode it, the size doesnt change anymore when encoding with the same settings
• pgo builds are injected cause they do rarely crash on p-1 if they are not injected to call mimalloc externally; this is a behaviour found in older builds too and seems related to the pgo training method and only on windows (where I would need to make multiple profraw to merge together until I find the combination that doesnt make the binary crash; pointless after we found out that injecting the binaries is enough to avoid the crashes)

The builds below are all from the v2.3.0-B pre-release (https://github.com/psy-ex/svt-av1-psy/releases/tag/v2.3.0-B), which is not currently NOW merged into the main branch! but is in the testing branch (so if u build it yourself remember to git clone from the testing branch!).
The zips include the generic builds:
x86-64, x86-64-v2, x86-64-v3, x86-64-v4
And the march specific builds (pgo builds dont cover all of them but only the ones my R9 7900 doesnt crash on obv):
znver1, znver2, znver3, znver4, znver5, haswell, broadwell, skylake, rocketlake, alderlake, raptorlake

cmake --fresh -B svt_build -G Ninja -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=OFF -DENABLE_AVX512=$AVX512ONOFF -DBUILD_APPS=ON -DSVT_AV1_LTO=OFF -DCMAKE_CXX_FLAGS_RELEASE="/DNDEBUG /clang:-O2 -flto /clang:-pipe -march=$march" -DCMAKE_C_FLAGS_RELEASE="/DNDEBUG /clang:-O2 -flto /clang:-pipe -march=$march"

The zips are a Matryoshka cause github doesnt support 7z
svt-av1-psy_2025-02-03_03.31.03_MULTI-MARCH_clang19.1.5_2.zip
svt-av1-psy_2025-02-03_03.42.33_MULTI-MARCH_av1an-pgo_clang19.1.5_injected.zip
svt-av1-psy_2025-02-03_07.52.07_testing-branch_MULTI-MARCH_dovi+hdr10plus_clang19.1.5.zip
svt-av1-psy_2025-02-03_08.26.21_testing-branch_MULTI-MARCH_dovi+hdr10plus_av1an-pgo_clang19.1.5_injected.zip

Look at the main thread up here to know what -march u should pick (ex: AMD 7000s are znver4)
(znver3 should still be bugged and slower than znver2, so I advise to use znver2; any report is appreciated)

More infos about the builds are at #69 (comment) and #88 (comment) for now.
More discussions regarding the problems of the previous version are in the v2.3.0 threads (#88) as well as in some issues (might be closed if patched)

[Ironclad17]

svt-av1-psy.2.3.0-B.dovi.hdr10plus.av1an-pgo.znver2.clang19.1.6.zip
svt-av1-psy.2.3.0-B.dovi.hdr10plus.znver2.clang19.1.6.zip
I just finished compiling these. Both appear to be working without any of the errors in 2.3.0-A.

[Andarwinux]

https://github.com/Andarwinux/mpv-winbuild/releases/tag/2025-02-03-38ad1ed

Svt[info]: SVT [version]:       SVT-AV1-PSY Encoder Lib v2.3.0-B
Svt[info]: SVT [build]  :       Clang 21.0.0git (https://github.com/llvm/llvm-project.git 689ef5fda0ab07dfc452cb16d3646d53e612cb75)      64 bit

x86-64-v3: -march=skylake -mtune=skylake -mno-gather
x86-64-v4: -march=rocketlake -mtune=znver5 -mprefer-vector-width=512
aarch64: -mcpu=cortex-a76
Performance is not expected to be as good as other builds, as PGO training has not yet been done for v2.3.0-B.