

quality good -crf 31 -c:v libvpx-vp9 -c:a libopus \ minrate 900k -maxrate 2610k -tile-columns 2 -g 240 -threads 8 \ Here’s the recommendation from the Google Core Technologies blog:įfmpeg -i tearsofsteel_4k.mov -vf scale=1920x1080 -b:v 1800k \ There are several sources for command strings.

Table 1: These results show that the CRF setting in the Google command string had little impact on output quality.I’m updating the VP9 section of my course Streaming Media 101: Onboarding for Streaming Media Professionals and wanted to share three key findings. This should allow you to drop the data rate of your videos by 30 – 40% and deliver the same quality as H.264. One of the best options is to encode using the VP9 codec, which plays in most browsers, on Android devices, on Macs and iOS devices in Chrome, and on many OTT devices and SmartTVs. As always, if I’ve gotten anything wrong, please let me know at producers are exploring options to produce quality similar to H.264 at lower bitrates. The three key takeaways are 1) use the command script shown on the bottom of the page, 2) a speed setting of 2 offers the optimal quality/performance tradeoff, and 3) the row-mt setting improves performance significantly with zero quality loss when multiple unused cores are available. This is a long post only of interest to those attempting to optimize their VP9 encodes.
