Search the Community
Showing results for tags 'vp9'.
Found 2 results
I've noticed that in both the latest Chrome, Firefox and Edge browsers that Emby performs a transcoding process instead of direct play to these browsers. These browsers have supported VP9 for some time now and in fact websites like YouTube have been sending direct VP9 streams to users for well over a year now. I would like to know if this is something that we can get fixed? I have found VP9 to be far superior when it comes to 4K content than H264 and it doesn't make sense to transcode VP9 for browsers when the browsers already support VP9
It would be great if the Chromecast Ultra profile would be updated to allow direct playing of VP9, Opus, and mkv/webm containers. They all definitely work, as I can direct play them with all transcoding turned off. The reference VP9 encoder (libvpx in ffmpeg) pushed out an update in October that allows for much faster encoding than before, making VP9 a useable codec for me (and others). All of those codecs and containers are open and freely licensed as well, which is a great thing to support. Also, VP9 + Opus + webm is directly playable in Chrome, Firefox, and Opera (as well as Edge if an experimental flag is enabled) which makes up a large percentage of browser use.