Learn FFmpeg - Modern Features & Roadmap

#Introduction

In episode 20 you saw FFmpeg from the programming side — how the libraries and wrappers merge with applications. Now we shift perspective: from how to use it to where it's going. FFmpeg isn't a static project; it releases new versions every few months with features that change how we work.

This episode reviews the three latest releases — 8.0 "Huffman", 8.1 "Hoare", and 9.0 "Lei" — then reads the roadmap direction. Understanding these releases is useful not just for updating the binary, but also for judging which features are worth waiting for and which are ready for production.

#The FFmpeg Release Rhythm

FFmpeg follows a predictable release pattern: a new major release every year, usually with sequential codenames (alphabetical and scientist-themed). In between are point releases containing backported bug fixes. Since 2023 the rhythm accelerated to roughly one major release per year, with version numbers now climbing quickly — from 6.x, 7.x, up to 9.0.

If you've followed this series, you've already used most of these features in previous episodes — now it's time to see them in full.

#FFmpeg 8.0 "Huffman" (August 2025)

The name "Huffman" refers to David Huffman, inventor of Huffman coding, the foundation of data compression. The theme fits: release 8.0 focuses on behind-the-scenes refinement. You can verify whether your local install has reached this release with apt-cache policy ffmpeg.

#AV1 Encoding Improvements

We already covered AV1 in episode 18 — and release 8.0 strengthens it. The bundled SVT-AV1 encoder was updated to a faster, more efficient version, and the built-in AV1 decoder got optimizations. The practical impact for you: the same preset produces smaller files, or encoding finishes faster for the same bitrate. This is a real example of why the FFmpeg version used affects production results — the advice to record the encode version in episode 18 wasn't just theory.

#Stricter FATE Testing

FATE (FFmpeg Automatic Test Environment) is the automated test suite that runs hundreds of decode/encode cases across various architectures and compares result checksums. Release 8.0 expanded FATE's coverage — meaning regressions (silently broken features) are caught faster before reaching users. For users, this means lower-risk upgrades.

#Libavcodec Updates

Dozens of codecs received fixes — from niche decoder bug fixes to DSP optimizations for ARM architectures (interesting for those developing for ARM-based devices like Raspberry Pi and embedded hardware). The key point: this release confirms that codec maintenance is continuous work, not a one-time done deal.

#FFmpeg 8.1 "Hoare" (March 2026)

The name "Hoare" honors Sir Tony Hoare, a computer science pioneer (inventor of quicksort and the null reference note). Release 8.1 brings features more oriented toward hardware and metadata.

#Vulkan Compute for ProRes & DPX

Vulkan, the cross-platform graphics API, is now used by FFmpeg for compute — not just rendering. In 8.1, the scale_vulkan filter and the ProRes/DPX encoding paths can use the GPU via Vulkan compute. For users, this adds acceleration options beyond the CUDA and VAAPI discussed in episode 14. Its greatest value is for pipelines that want to use GPUs not locked to a specific vendor.

#D3D12 H.264 and H.265 Encoding

On Windows, release 8.1 adds H.264 and H.265 encoding via Direct3D 12 — Microsoft's modern API. This completes the hardware acceleration path that previously relied heavily on QuickSync or NVENC. The consequence: modern Windows applications can use the same GPU for rendering and encoding without detours.

#EXIF Metadata

EXIF (photo metadata) is now handled more completely on the video side. Users absorbing frames from digital cameras can read and copy EXIF data — such as capture date and camera parameters — without losing information when frames are processed or muxed into video. Details like this keep FFmpeg a bridge between the photo and video worlds.

#LCEVC Metadata and Experimental xHE-AAC

We touched both in episode 18 — and this is the release: FFmpeg 8.1 began reading LCEVC metadata (enhancement layer) and added the xHE-AAC decoder (MPEG-H USAC with Mps212) in experimental status. These two things are proof that FFmpeg picks up new standards early — not waiting until they mature. Experimental means: use for exploration, but not for critical production.

#FFmpeg 9.0 "Lei" (August 2026)

The next major release, 9.0 "Lei", brings a bump in the main library version numbers: libavcodec 63, libavformat 63, libavfilter 12. This is the so-called major version bump — and it comes with an important rule you must understand.

#Why Do Library Numbers Go Up?

Each FFmpeg library has its own version number indicating API compatibility. If the minor number changes, old APIs still work; if the major number changes, there are changes that can break programs linking against that library. This is why episode 20, which discussed the API, is inseparable from this episode: applications using libav* must be retested on major releases — code that runs on 8.x may not compile on 9.x.

For those using the CLI, the impact is much smaller — the commands learned throughout this series keep working. For those developing libav-based applications, this is a reminder to record the library version at build time and prepare an upgrade cycle.

#Roadmap: Going Forward

From the release trajectory above, several directions are clear:

• VVC/H.266 encode. The VVC decoder has been stable since 7.1; the next step is the encoder. Don't be surprised if a few releases ahead bring an experimental VVC encoder — following the same pattern as AV1, which took years to mature.
• Continuous AV1 improvements. AV1 is still young. Encoder optimizations, new presets, and GPU profiles will keep coming. AV1's strategic position as a royalty-free codec guarantees long-term focus.
• Wider GPU utilization. From CUDA and VAAPI in episode 14, now Vulkan and D3D12. The direction is clear: more and more pipelines use GPUs for encoding, not just rendering.
• Richer metadata integration. EXIF, LCEVC, and other modern metadata show FFmpeg moving from "mere conversion" to "metadata-aware media management".

ffmpeg -version
ffmpeg -buildconf

ffmpeg -version gives the version number; ffmpeg -buildconf shows the complete build configuration — including which codecs are enabled. These two commands are the right starting point when checking whether a certain feature is available in your install, before blaming FFmpeg for an error actually caused by a stale binary.

#Conclusion

Episode 21 places you on the project's timeline:

• 8.0 "Huffman" improved AV1, expanded FATE, and maintained libavcodec.
• 8.1 "Hoare" opened Vulkan compute, D3D12 encode, EXIF/LCEVC metadata, and experimental xHE-AAC.
• 9.0 "Lei" marks the major bump to libavcodec 63, libavformat 63, libavfilter 12 — a compatibility reminder for API developers.
• The roadmap points toward VVC encoders, AV1 improvements, and ever-wider GPU utilization.

You now understand where FFmpeg came from and where it's heading. But a tool doesn't stand alone — it lives inside an ecosystem. In episode 22, the final episode of this series, we'll look at the ecosystem, alternatives & final reflections: yt-dlp, HandBrake, OBS, and VLC built on top of FFmpeg, comparisons with avconv and GUIs, plus a full recap of episodes 0–21 and a production checklist. See you in the closing episode.