David Ronca Details VCAT Beta 4.0 with VVC Decode

On February 12, I interviewed David Ronca, formerly of Netflix and Meta, now RoncaTech, about the latest Beta version of his Video Codec Acid Test, or VCAT, which now includes VVC decode courtesy of Fraunhofer’s open-source VVeC decoder. The interview is available here on YouTube. Here’s an overview of the highlights we covered, with timestamps for the video.

To get a copy of VCAT, check out the release notes (with download link) here. You can contact Ronca on LinkedIn here.

Here are the notable points in the interview with the VCAT demo available below.

00:00:00 — Introduction. Jan introduces David Ronca: per-title encoding pioneer at Netflix, key figure in AV1 adoption at Meta, now running his own development company RoncaTech and the VCAT project.

00:00:32 — What VCAT is and where it came from. VCAT (Video Codec Asset Test) is a decoding benchmarking tool that encapsulates the manual device testing Meta did over five years to achieve 75% AV1 reach on Facebook and Instagram globally. The goal: make that level of benchmarking accessible to anyone without the pain.

00:01:29 — Why software decoding demands its own benchmarking approach. Hardware decoders announce their capabilities via levels. Software decoders don’t. A device with a 1080p screen may have no business software-decoding 1080p AV1 or VVC. Battery drain, thermal events, and system overload are the real metrics — and they require long-duration tests, not short synthetic ones.

00:05:04 — The global Android problem. US deployments are relatively easy — iPhones dominate, high-end Androids fill the gaps. Go global and you’re dealing with $100-$150 Android devices running software decoders on modest SoCs. That’s where VCAT earns its keep.

00:07:02 — Level-aware playback and the benchmarking case. The principle David applied at Meta: benchmark devices, establish what each class of device can actually handle, then enforce level-equivalent restrictions in software. VCAT gives any operator that same capability.

00:08:50 — Who else should be using this? Network operators evaluating which low-cost handsets to bundle, handset vendors wanting to prove their $150 device is competitive, and SoC vendors pitching to those handset vendors. Video quality is the dominant user experience metric, so video decode performance should inform device selection.

00:12:42 — How VCAT ended up open source under RoncaTech. Meta decided that VCAT didn’t fit into its open source portfolio. David took it on himself because he believes it matters to the ecosystem. Released under GPL, available as APK or source.

00:15:40 — Beta 4: what’s new. Two main additions: test vector management (shareable, standardized benchmark sets that any company can publish for their specific content profile) and VVdeC integration, enabling VVC software-decoding benchmarks for the first time.

00:22:27 — VVdeC vs. AV1 benchmark results. On a test device, AV1 (using the VVdeC-equivalent AV1 decoder) ran about 21 hours before hitting 15% battery. VVdeC drained roughly three times faster, with occasional thermal events. Fraunhofer acknowledged their decoder isn’t optimized — a private commercial VVC decoder would likely show better numbers.

00:27:27 — VCAT Demo. Showing test configurations, VVC playback, and telemetry captured during testing.

Commenting on how VVC playback compared to AV1, Ronca said that on his test device, Dav1d 1.5 delivered around 21 hours of playback before hitting 15% battery, while VVdeC 3.0 drained roughly three times faster. He noted occasional thermal events with VVdeC but no thermal shutdowns.

He added a caveat that when he published the results, a Fraunhofer engineer acknowledged that VVdeC is nowhere near as optimized as Dav1d, so the numbers weren’t a surprise — and that a commercial VVC decoder from a company like Tencent or TikTok would likely show considerably better performance.

00:34:00 — Future directions: encoder, GPU, and AI benchmarking. David sketched out a roadmap: a VCAT encoder variant to measure the cost side of the codec efficiency equation, GPU benchmarking for compositing and rendering scenarios, and AI codec testing—specifically, whether NPU-accelerated AI decoders deliver real battery-life gains or just paper bitrate savings.

00:44:31 — How to get VCAT. APK and GitHub source via David’s LinkedIn post. Test vector toolset available as Python scripts. Not on the Play Store due to file system access requirements. David is open to 30-minute conversations with anyone who has a use case — no NDA required.

About Jan Ozer

Avatar photo
I help companies train new technical hires in streaming media-related positions; I also help companies optimize their codec selections and encoding stacks and evaluate new encoders and codecs. I am a contributing editor to Streaming Media Magazine, writing about codecs and encoding tools. I have written multiple authoritative books on video encoding, including Video Encoding by the Numbers: Eliminate the Guesswork from your Streaming Video (https://amzn.to/3kV6R1j) and Learn to Produce Video with FFmpeg: In Thirty Minutes or Less (https://amzn.to/3ZJih7e). I have multiple courses relating to streaming media production, all available at https://bit.ly/slc_courses. I currently work as www.netint.com as a Senior Director in Marketing.

Check Also

Computing VMAF: How Missing Color Metadata Tanked the Score

Developing a metrics tool is the easy part. Wire up FFmpeg, shell out to libvmaf, …

How Fast Will AV2 Deploy?: Ask Joe Sixpack

The AV2 spec went final in late May 2026, AOMedia announced it on June 9, …

Three Paths to Compression for Machine Vision: VCM, FCM, and the V-Nova Wild Card

Video is increasingly captured primarily or exclusively for machine viewing, including applications like surveillance cameras, …

9 comments

  1. Clarification on the ownership of VCAT. The original intent was to build on VLC Benchmark, and VCAT would remain under VideoLabs license. When VCAT was rewritten we needed a different ownership model. META decided vcat did not fit in their OSS portfolio. Since I wrote most of the code, they let me release under RoncaTech.

  2. that a commercial VVC decoder from a company like Tencent or TikTok would likely show considerably better performance.

    • Avatar photo

      So what? As a group, AOMedia invested to provide all AV1 implementers with a high-performant solution, advancing the AV1 standard for all. VVC patent holders are like little islands, guarding their own advancements for their own use while the standard itself languishes. A rising tide raises all boats. A divided fleet founders in the shallows.

  3. Thanks for the detailed write-up on VCAT 4.0, Jan. The level-aware playback enforcement and real-device battery/thermal methodology that David drove at Meta are exactly the kind of metrics that push codec evaluation beyond synthetic benchmarks. Excited to see VVdeC folded in alongside x265 and SVT-AV1 so we can compare VVC efficiency in the same harness. We benchmark similar open decoder stacks on AI video workflows over at Bernini Video and the level/thermal framing is hugely useful for our pipeline.

  4. Great get with Ronca — VVC decode in VCAT Beta 4.0 is a big deal for anyone validating next-gen encode ladders, and his points on decode complexity were clear. I’ve actually been stress-testing AI-generated clips from renderflowai.com through codec comparisons like this, which makes tools like VCAT even more useful to me. Thanks for the detailed Q&A.

  5. Solid interview — hearing Ronca walk through VVC decode support and the benchmarking philosophy behind VCAT was genuinely informative for my encoding tests. Off-topic but practical: I track hardware restocks for my test bench via restockalerts.com, which emails when items return (even Hermès, amusingly). Keep these engineer interviews coming.

  6. that a commercial VVC decoder from a company like Tencent or TikTok would likely show considerably better performance.

    • Avatar photo

      Yeah, of course. But the fact that AV1 has Dav1d (an open source high performance decoder) and VVC doesn’t is a real strength for AV1 that the VVC patent owners have decided not to match.

Leave a Reply

Your email address will not be published. Required fields are marked *