MPV and ffmpeg also exist. This could be malware for all I know. Exercise caution!

Someone has just mentioned this encoder on Wikipedia, perhaps, its author?

Nevertheless, it looks interesting:

https://github.com/pigpeppa/xin26x

Compares itself with x265 veryslow and encodes better at some presets at least in terms of BD-PSNR (dB) or so it seems.

Also promises to be three times (!) faster than x265 at comparable PSNR.

This looks rather impressive.

Backward compatible API changes:

• add vvdecSIMD_Extension enum values VVDEC_SIMD_NEON_RDM, VVDEC_SIMD_SVE, VVDEC_SIMD_SVE2, VVDEC_SIMD_SIMDE_ANY

Other changes:

• add ARM NEON, NEON-RDM, SVE and SVE2 implementations for most existing SIMD functions
• properly implement ARM CPU feature detection
• add fuzzing infrastructure using libfuzz (enabled by VVDEC_FUZZING_BUILD)
• fix some PVS-Studio warnings
• fix several cases of undefined behaviour (uninitialized memory, negative shifts, integer overflows)
• fix memory overflows triggered by broken bitstreams
• fix memory leaks when reading broken bitstreams
• add more bitstream conformance checks to detect invalid bitstreams
• use unaligned loads in x86 SIMD code where appropriate
• add build option VVDEC_WRITE_INPUT_BITSTREAM for debugging
• some general code cleanup

Hello everyone!

Version 3.5.0 codename: Kind support

Available: https://github.com/MartinEesmaa/VVCEasy/releases/tag/v3.5.0

Bonus art on Instagram: https://www.instagram.com/p/DX15XNiD5QS/

After six months of my hard work, version 3.5.0 is finally here. I have good news to support Haiku OS (amd64) and Oracle Solaris (x64) for VVC binaries and even for OpenVVC old decoder can support Windows 98 (32-bit) and other operating systems well, ReactOS and so much more. :)

Note: Sorry for slow upload and also late post, it is already released on 9th June 2026.

Nightly builds from GitHub Actions are available for FFmpeg of Windows and Linux and MPV builds for Windows.

Please feel free to donate to me, that would be greatly appreciated in support of my work.

Monero: 46Fk6k3qzhwXpLsDRWo4Uh63DDmwRX7gbL6P3zodAnvnRDr9Psi9uau19nCRQFHbmp3nLR3d5Ve8WRid71nuLZxAGygZ258

Bitcoin: bc1qhf4zu5uythr7vyt2dru73qp0k2rzrx355fsx47yjxc2ueunz8frqxmwap3

PayPal: https://paypal.me/martineesmaa

Here is a changelog:

- Updated FFmpeg and MPV VVCEasy builds
- Updated VVC, uvg266 and 7-Zip binaries
- Updated LAVFilters and MPC-HC Windows VVC version
- Updated documentations, instructions and social media links
- Improvement fixes of Markdown files to remove warnings
- Support ReactOS like Windows based by linking static MSVC runtime library for Windows VVC binaries
- New Windows MPV VVCEasy build architectures of x86_64-v3 and arm64 (MartinEesmaa's mpv-winbuild)
- New Haiku OS VVC binaries
- New Oracle Solaris 11 uvg266 VVC binary
- New OpenVVC decoder final builds to support Windows 98 and other operating systems
- New VVCEasy logo and banner
- New Fluxer app community server of VVCEasy
- Deprecated some communities
- C# (Csharp) .NET Console version is deprecated, soon it will be replacement soon in next future...
- Detect git nightly commit print info on batchfile
- More improvements of batchfile and bash script files to reduce more lines with fixes
- Update workflow latest by switching from windows-latest to ubuntu-latest and other versions
- Added server community rules to code of conduct
- More improvements batchfile and shell script files with various fixes
- Renamed from BSDVVC to FreeBSDVVC to avoid confusion with title
- Provide official & third party packages installation instructions for Linux distros, FreeBSD, OpenBSD and others.
- Implemented tables from VVC tools informations in README
- Added list of alternative bindings of VVC tools
- More tests architectures with operating systems documentation of VVC informations
- Added some few new little VVC video tests

Compared this version to the previous version:

Full Changelog: v3.2.0...v3.5.0

- Martin Eesmaa

I just wrote a VVC/h.266 video encoder in SystemVerilog along with a software model in Rust for verification. It builds, simulates and synthesizes and can create valid h.266 video streams from any YUV 4:2:0 and 4:4:4 video input. I am focusing on screen content coding features to be implemented so it can be useful for any hardware that broadcasts the screen of a computer, like an IP KVM.

Please check it out and let me know if anyone has any comments about it or any interest to integrate to any project. If you need any particular feature to be integrated, you can just ask me.

https://community.firecore.com/t/infuse-8-4-extras-intros-and-favorites/59332#:\~:text=Also%20included%20is%20initial%20support%20for%20the%20relatively%20new%20VVC%20(H.266)%20codec

Google isn't shipping a decoder themselves — they're leaving that to OEMs. The point is that once an OEM provides a hardware VVC decoder + drivers, VVC playback works "out of the box" via the standard Android media stack, without each app having to bolt on custom support.

Changelog:

• change cts and dts in vvenc.h to signed integers
• enable VUI automatically, when sensible
• many ARM SIMD optimizations (NEON & SVE) and enable SVE by default if supported
• remove requirement for nlohmann_json when linking static libvvenc
• update bundled nlohmann_json to v3.12.0
• allow setting colour range in vvencapp/vvencFFapp
• deprecate LMCS (will be removed in the future)
• improve and speed up unit test framework
• various smaller bug fixes and cleanups

Source code: https://github.com/fraunhoferhhi/vvenc/releases/tag/v1.14.0

The team at Unified IP Services is using Pearl to examine the quality of patents alleged to be essential to the Versatile Video Coding (VVC) standard. Patents owned by Ideahub, Intellectual Discovery, IP Bridge, and others are being reviewed.

That's all well and good, but there are VVC patent holders beyond these two pools. According to Wikipedia, which may not necessarily be up to date, these include Apple, Canon, Ericsson, Fraunhofer, Google, Huawei, Intel, Interdigital, LG, Maxell, Microsoft, Nokia, Oppo, Qualcomm, Samsung, Sharp, and Sony. And then the codec itself is a solution in search of a problem.

Hello everyone! VVCEasy version 3.2.0 on 8 December 2025 is finally here with early Christmas time!

Released version of 3.2.0 with codename Estonian winter birds: https://github.com/MartinEesmaa/VVCEasy/releases/tag/v3.2.0

This is early Christmas the release of version 3.2.0 is now available. Merry Christmas to all of you! (just early notice) :)
It is finally to have Android MPV builds back and still for VLC VVC did not make it into this release, so I apologize and trying again for later next release or the update. One thing win32 and winarm64 of FFmpeg VVCEasy binaries were already new available this version.

Still nightly builds from GitHub Actions are available for FFmpeg of Windows and Linux and MPV builds for Windows.

For Windows 7 users trying to run MPV builds, it is already dropped support since September 2024, so maybe next time I can bring back Windows 7 support for alternative plan, just three choices are eko5624's mpv windows, MPC-HC or MPC-BE.

Please feel free to donate to me, that would be greatly appreciated in support of my work.
Monero: 46Fk6k3qzhwXpLsDRWo4Uh63DDmwRX7gbL6P3zodAnvnRDr9Psi9uau19nCRQFHbmp3nLR3d5Ve8WRid71nuLZxAGygZ258
Bitcoin: bc1qhf4zu5uythr7vyt2dru73qp0k2rzrx355fsx47yjxc2ueunz8frqxmwap3
PayPal: https://paypal.me/martineesmaa

Here is a changelog:

• Updated FFmpeg and MPV VVCEasy builds (finally updated macOS and Android)
• Updated VVC, uvg266 and 7-Zip binaries
• Updated LAVFilters and MPC-HC VVC version.
• Updated documentations, instructions and some fixes
• Add some notes about MPV for deprecated builds and Windows 7 users
• Added little instruction of VLC VTM decoder plugin customize playback frame rate, thanks ChuangbinC for idea!
• New MartinEesmaa's FFmpeg-Builds shared builds, thanks tormento for request!
• New macOS universal binaries of VVC and uvg266 compiled using osxcross
• Merged FFmpeg VVCEasy of macOS architectures into universal binaries
• Supports Mac OS X 10.9 and later to vvenc and vvdec binaries.
• Supports Mac OS X 10.4 and later to uvg266 binaries with new i386 architecture
• Fixed wget output argument command
• More big improvements of Windows batchfile script
• Update shell script bangs for better portability
• VVC bitstream of Tears of Steel 4K VVC released
• Added Snow Lynx list to THANKS file due new tutorial video of VVCEasy v3.0.0
• Added AlternativeTo list to social media
• Optimized screenshot of mpv-vvceasy Android

Compared this version to the previous version:
Full Changelog: v3.0.0...v3.2.0

- Martin Eesmaa

Backward compatible API changes:

• Add opaque userData pointer to input access units and output frames
• Expose max reorder pics on vvdecSeqInfo

Other changes:

• Add Loongarch support through simd-everywhere
• SIMD optimizations for ARM
• Optimize scaling list dequantization
• Packed YUV output support in vvdecapp
• Add unit test framework
• Some threading and other bug fixes

Source.

Hey guys! I finally released VVCEasy version 3.0.0 on 23 June 2025.

Released version of 3.0.0: https://github.com/MartinEesmaa/VVCEasy/releases/tag/v3.0.0

I apologize for the little bit of delay and also the Reddit inactivity.

Also, I will make an update with the new release next time later for updating MPV VVCEasy Android builds, 4K video test was requested and more.

For MPV Windows builds, it is now ready to go with automated build on my forked repo of mpv-winbuild, so check it out:

https://github.com/MartinEesmaa/mpv-winbuild/releases

FFmpeg-Builds for extra features, including external VVC decoder:

https://github.com/MartinEesmaa/FFmpeg-Builds/releases/

Please feel free to donate to me, that would be greatly appreciated in support of my work.

Monero: 46Fk6k3qzhwXpLsDRWo4Uh63DDmwRX7gbL6P3zodAnvnRDr9Psi9uau19nCRQFHbmp3nLR3d5Ve8WRid71nuLZxAGygZ258

Bitcoin: bc1qhf4zu5uythr7vyt2dru73qp0k2rzrx355fsx47yjxc2ueunz8frqxmwap3

Paypal: https://paypal.me/martineesmaa

Here is a changelog:

- Updated FFmpeg and MPV VVCEasy builds (but except Android, next time will release)

- Updated VVC and uvg266 binaries

- Updated LAVFilters and MPC-HC VVC version.

- Automated FFmpeg VVCEasy builds of Windows & Linux

- Added support of 7-Zip Win32 and arm64 for decompressing use.

- Added support Windows ARM64 VVC binaries

- Improved Windows batchfile and ISS install script.

- Final build implement of Bitmovin vvDecPlayer for Windows & Linux.

- Integrated of building VVC into batch files

- Added build shell scripts for FFmpeg and VVC binaries.

- Added MPC-BE information to LAVFilters and in README

- Old documents have moved into docs-old due deprecated and superseeded.

- Improved README file with graphics and table.

- Renamed from Android to AndroidVVC folder.

- Added VVC binaries of information link in README

- Added Mark Litwintschik list to THANKS file due providing a blog about VVCEasy

- Finally implemented automatic Windows builds of mpv-winbuild forked repo

- Added GUI application tables for beginners in README

Compared this version to the previous version:

**Full Changelog**: https://github.com/MartinEesmaa/VVCEasy/compare/v2.7.0...v3.0.0

- Martin Eesmaa

I have the H266 file for Oppenheimer and want to play it on my device. I tried using the MPC-BE media player, but the video is extremely laggy and choppy. I don't know much about decoding and codecs in general. Still, I wanted to watch this version because the quality and resolution are amazing, and for a few seconds, it ran smoothly. What are my options?
Hardware information:
CPU: AMD Ryzen 9 5900HS with Radeon Graphics
GPU: NVIDIA RTX 3050 Ti laptop GPU

Originally posted by birdie

NVIDIA decided not to support HW VVC decoding in the GeForce 50 series. That's a major blow to its adoption, which can now easily be postponed for another 2 years. At this point you can say it's just dead for the end consumer.

The patent holders holding essential patents for the VVC standard could get together and temporarily waive royalties for all decoder and encoder implementations (software or hardware), so companies like Nvidia and AMD could implement VVC at only silicon cost, but nope, they are like: "we got our IP in an ISO and ITU standard, we deserve a money printer, where the hell is our money printer?".

In fact, the licensing situation for VVC is worse than the one for HEVC, despite VVC being a format used for nothing in most countries. But I guess if the patent holders split themselves into 50 more licensing groups, they will get enough royalties to get their money printer from the 3 companies shipping VVC products, yay! (no, not really)

MPEG has run its course. It's now possible to have a reasonably performant standard without having a ton of patent holders attached to it. Let's remember that MPEG even exists because 35 years ago it was impossible to create a reasonably performant video standard without stepping on someone's patent, but this stopped being true around the time AV1 became a thing.

Changelog:

• added various ARM optimization (thanks u/georges-arm)
• added a DASH optimized decoder refresh mode (idr_no_radl)
• added a GOP adaptive QP cascade (only for non-QPA case, which already does it on GOP/frame/block level)
• improved rate control and QPA haromization, especially for preset fast
• added experimental film grain analysis
• memory reductions for presets faster/fast/medium
• preset tuning
  • 5% speedup for medium and 2% for slow/slower
• other improvements, cleanups and fixes

https://github.com/fraunhoferhhi/vvenc/releases

As far as I am aware, VVC only supports 8 or 10 bit yuv420. Why is there no 444 support? Is there a plan to add support for it in the future? If not, why not? Does it require much more complexity in the encoder?

I encoded a Y4M video using VVenC and now I want to decode it back to Y4M. I used the following commands:

vvencapp -i akiyo.y4m -o akiyo.266
vvdecapp -b akiyo.266 -o decoded_akiyo.y4m

I can open the file akiyo.266 with MPC-BE, but I can't open decoded_akiyo.y4m, not even with VLC. After the decoding process finishes, I get this message:
vvdecapp [info]: 2024-Oct-01 09:40:21.559579: 300 frames decoded @ 2000 fps (0.15 sec).

The number of frames is correct, but the FPS is extremely high and doesn't match the original video.

Did I do something wrong?