SShortSingh.
Back to feed

Build a capped-CRF ABR ladder with FFmpeg and prove it with VMAF (x264, NVENC, SVT-AV1)

0
·1 views

TL;DR We'll convert a 4-rung CBR ladder to capped CRF, write a small Python sweep that encodes a set of clips at several CRF and cap values, score each with VMAF, and report average VMAF, lowest-frame VMAF, bitrate, and the share of seconds that hit the cap. Then we'll port the winning settings to NVENC and SVT-AV1. A fixed-bitrate ladder spends the same on every second of every title. Capped CRF lets the encoder spend less on easy content and holds a ceiling on hard content. The catch is that it has two knobs (the CRF value and the cap) and most people only tune one.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

I built a Chrome Extension to extract Tailwind & Figma tokens (and got blocked by Reddit bots 🤖)

As someone who constantly jumps between UI/UX design in Figma and writing Tailwind components, I was wasting hours manually inspecting computed CSS to extract hex codes and build tailwind.config.js files. Over the weekend, I built Token Inspector, a 100% client-side Chrome extension to automate this. In one click, it exports ready-to-use Tailwind configs, Tokens Studio JSON, and zips all inline SVGs. I tried sharing it on Reddit this morning to get my first 20 users, but the automods instantly nuked my post because of the link. So, I’m giving the promo code I made for them to the Dev.to commun

0
ProgrammingDEV Community ·

Building a Multilingual Documentation Pipeline for EU Battery Regulation (2023/1542) Compliance

If you're shipping batteries into the EU, or you work on the tooling that generates compliance documentation for hardware products, Regulation (EU) 2023/1542 just became your problem. It requires technical documentation (declarations of conformity, safety instructions, battery information sheets, carbon footprint declarations, and eventually digital battery passport data) to exist in the official language of every member state where the product is sold. The legal and terminology side of this is covered well in this breakdown of what the regulation requires. This post is about the other half of

0
ProgrammingDEV Community ·

What Is HTTP/3? Why Most of the Web Still Isn't Using It

Every major browser decided HTTP/3 was ready years ago. Chrome, Edge, Firefox and Safari have all shipped full support since 2022, and caniuse.com puts global browser support at 94.55% as of October 2026. Yet according to W3Techs, only 40.8% of websites actually served pages over HTTP/3 as of October 2026. That gap, not the protocol itself, is the real HTTP/3 story: browsers have been ready for years, and most servers still are not. Key takeaways Browser support for HTTP/3 sits at 94.55% globally (caniuse.com, October 2026), but only 40.8% of websites actually serve traffic over it (W3Techs, O