The current chromium ebuild says: # TODO: re-enable on vp9 libvpx release (http://crbug.com/174287). myconf+=" -Dmedia_use_libvpx=0" This is problematic because http://www.youtube.com/html5 thinks that VP9 is available, so many videos fail to play. If I install libvpx-9999 and change the above option to =1, then VP9 works correctly. I would like some way to enable this without having to edit the ebuild, either by setting a USE flag, or having it auto-detect the presence of libvpx-9999.
Ah ha! So that's why HTML5 on Youtube stopped working. Yeah, we either need to enable VP9 decoding, or fix the capabilities that Chrome sends to reflect that we don't actually support it. I don't think a USE flag really makes sense.
From http://crbug.com/174287, it seems like upstream has no interest in cutting new releases of libvpx. Let's take a snapshot, or go with the bundled copy in chromium.
(In reply to Mike Gilbert from comment #2) > From http://crbug.com/174287, it seems like upstream has no interest in > cutting new releases of libvpx. They do, but they're taking their time. :) Most likely I'll do the release but need to get the green light for that. > Let's take a snapshot, or go with the bundled copy in chromium. Oh, I completely missed the bits in net/base/mime_util.cc that claim vp9 support. Yeah, I'm kind of leaning towards bundled copy. Ideally we could do that before next M30 stable release...
15 Oct 2013; Pawel Hajdan jr +chromium-30.0.1599.66-r1.ebuild, +chromium-31.0.1650.12-r1.ebuild, +chromium-32.0.1664.3-r1.ebuild: Fix vp9 support by switching to bundled libvpx (bug #487926 by Paul Marks).
Thank you, it's working now. Tested URLs: - http://base-n.de/webm/VP9%20Sample.html - http://www.youtube.com/watch?v=EUlzg-fkHak
