Changes between Version 11 and Version 12 of Encode/VP9


Ignore:
Timestamp:
Jan 22, 2018, 9:02:08 AM (9 years ago)
Author:
slhck
Comment:

clarify availability of VP9 decoders (most browsers support it, except IE, but that doesn't support VP8 either)

Legend:

Unmodified
Added
Removed
Modified

  • Encode/VP9

    v11 v12  
    128128== Compatability ==#compatibility
    129129
    130 As 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]]: 
     130As of 2018, [https://en.wikipedia.org/wiki/HTML5_video#Browser_support most browsers] support VP9. Many recent [http://wiki.webmproject.org/hardware/socs phones and other embedded systems] also support VP9. If for some reason VP9 is not supported on your target device, you may fall back to [[Encode/VP8|VP8]] encoding, which offers higher compatibility but lower compression efficiency / quality.
    131131
    132 {{{
    133 ffmpeg -i input.mp4 -c:v libvpx output.webm
    134 }}}
    135 
    136 
    137 Also, 4:2:0 chroma sampling is more widely supported than the default 4:4:4:
     132If your input source is using 4:2:2 or 4:4:4 chroma subsampling, some players might not be able to handle the output that libvpx produces. Use 4:2:0 chroma subsampling in such a case:
    138133
    139134{{{