hn.today

Optimizing x264 settings and per-title ladders

streaminglearningcenter.com3 points0 comments
Screenshot of Optimizing x264 settings and per-title ladders

This work evaluates how far x264 can be pushed and what per-title encoding ladders deliver, using FFmpeg/x264 on 13 diverse 1080p clips and VMAF as the quality metric. Incremental tuning - veryslow preset, a 10s GOP, two-pass, extra reference frames - plus switching from a fixed Netflix-style ladder to per-title ladders increased average VMAF by 0.66 points while cutting average bitrate from 4.90 Mbps to 3.27 Mbps (≈33%). Encoding time grew 3.2× on an Intel Core i9-14900 workstation; baseline ladder cost ≈$1.25/hr of content encoded, optimized ≈$3.99/hr, so the extra encoding expense is recovered after about 186 hours of viewing at $0.02/GB bandwidth. Results use a Top-Heavy viewer distribution (≈71.6% on top rungs) and tune top rungs to VMAF≈93 because quality above 93 is visually indistinguishable.

The practical conclusion is clear: implement per-title encoding before assuming gains from HEVC/AV1, since untuned H.264 leaves significant bandwidth on the table. Benefits scale with how inefficient the existing ladder is (big wins if current 1080p top rungs are 5.5-6.5 Mbps) and with clip complexity (news/animation gain more than sports). For mobile-heavy audiences the VMAF gain grows but bandwidth savings shrink, extending the breakeven point, so per-title tuning should be judged against audience profile and encoding throughput.

Read on streaminglearningcenter.com0 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.