Changes between Version 10 and Version 11 of Encode/VP9


Ignore:
Timestamp:
Dec 29, 2017, 9:59:24 PM (20 months ago)
Author:
Darxus
Comment:

Added Compatability section, mentioning vp8 and 4:2:0 are more widely supported

Legend:

Unmodified
Added
Removed
Modified
  • Encode/VP9

    v10 v11  
    126126When the deadline/quality is set to `realtime`, the encoder will try to hit a particular CPU utilization target, and encoding quality will depend on CPU speed and the complexity of the clip that you are encoding. See [https://www.webmproject.org/docs/encoder-parameters/ the vpx documentation] for more info. In this case, the valid values for `-cpu-used` are between 0 and 15, where the CPU utilization target (in per cent) is calculated as `(100*(16-cpu-used)/16)%`.
    127127
     128== Compatability ==#compatibility
     129
     130As of December 2017, some browsers do not support VP9, and more phones support hardware decoding of VP8 than VP9, so for greater support you may wish to use [[Encode/VP8|VP8]]: 
     131
     132{{{
     133ffmpeg -i input.mp4 -c:v libvpx output.webm
     134}}}
     135
     136
     137Also, 4:2:0 chroma sampling is more widely supported than the default 4:4:4:
     138
     139{{{
     140ffmpeg -i input.mp4 -c:v libvpx-vp9 -pix_fmt yuv420p output.webm
     141}}}
     142
     143
    128144== Also see ==
    129145