New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 19 users
Status: WontFix
Owner:
Closed: Jul 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature

Blocking:
issue 459408



Sign in to add a comment
Provide a disable VP9 decode in chrome://flags
Project Member Reported by renganat...@chromium.org, Feb 18 2015 Back to list
Provide a chrome://flags option to disable VP9 decode for future experiments. 

VP9 decode is great for YouTube. YouTube has published multiple times how it is a better experience overall for users as it reduces bandwidth requirements, provides a better streaming experience, and lowers the requirements for HD. 

However, we have are getting increasing reports on poor VP9 decode performance, especially in low power notebooks for HD @ 60fps. To better understand real world decode performance we want to add a chrome://flags "Disable VP9 decode" to run experiments across different architecture, network and battery conditions. 

Additionally, this also allows power users an escape hatch if they have a preference on codecs supported by Chrome.
 
Blocking: chromium:459408
Comment 2 by cont...@ekimia.fr, Feb 21 2015
I second this : would be very useful to test video decode corretly on chromium.
Comment 3 by thakis@chromium.org, Feb 25 2015
about:flags isn't for users to tweak settings. Flags on there are either for debugging, or temporary to turn on in-development features.

It's ok to temporarily add a flag if that helps with collecting perf data (but just uma should give you that already), but it's not for "escape hatches".
@thakis - duly noted. It is not intended as a user setting as much as requirement for running experiments to collect perf data. However, analyzing the ways to collect the data, it did require a chrome://flags. Happy to chat more / listen for any advice if you have experience in collecting the data we require here. Thanks.
Comment 5 by thakis@chromium.org, Feb 25 2015
You might want to talk to asvitkine about using uma/finch for your stuff – I'd be surprised if you needed a flag for this, and you don't need an about:flags entry for sure.
Juste a note : 99% of users don t have a GPU that can accelerate vp9. Disabling vp9 enable them to Get h264 accelerated vidéos ( like in YouTube)
Comment 7 by make...@gmail.com, Feb 26 2015
I would welcome this, watching 1080p and also 720p videos on Chrome lets my Ivy Bridge Ultrabook burn at 72-77°C and 80-90% CPU usage, where IE11 just uses 6-14% CPU.
Comment 8 by lena...@gmail.com, Feb 27 2015
Yoga 3 Pro seems to have no hardware acceleration for VP9. So watching 4K video in Youtube in Google Chrome is not possible, staggering, unwatchable.

Same video, same machine, in IE11 butter smooth. It uses the H.264 codec.

Please make an option to disable VP9 or choose the codec the user prefers.
Comment 9 by tork...@gmail.com, Apr 5 2015
Lets us use h.264 or make vp9 use gpu.

for now IE is best for youtube :-(
Status: WontFix
Given the presence of the h264ify extension and recent performance numbers for vp9, it doesn't make sense to implement this.
Comment 11 by x.ran...@gmail.com, Jul 17 2015
h264ify doesnt work.
Comment 12 by lena...@gmail.com, Jul 17 2015
For me (on a Yoga 3 Pro) h264ify does indeed work - at least partially. The video is reported to be x264 and not vp9. But it doesn't change the fact that the video is not hardware accelerated for some reason. Same video on IE is butter smooth, cpu at most 30%-40%. On Chrome cpu is 100% and frames are dropped like crazy. 
Comment 13 by lena...@gmail.com, Jul 17 2015
So maybe problem is not with actual codec but rather hardware acceleration support in Chrome?
Comment 14 Deleted
That is a distinct possibility. I'm also curious: how many of you are experiencing issues at resolutions higher than 1080p? I'm using an ultrabook which has a 3200x1800 resolution, and wondered if that could be having an effect, since I don't experience VP9 issues on other machines of lesser power. I also use the Windows 8.1 scaling feature, which I believe is simply called "zoom." Likewise, I get "butter smooth" frame-rates at ALL resolutions and 60 FPS on Internet Explorer. I think the most likely reason, from my experiments, is that hardware acceleration can't /really/ be disabled in Chrome, no matter what I try.
If you have a newer intel ultrabook you may be hitting another problem, issue 499696. To see if a given video has hardware acceleration find the player in chrome://media-internals and see if "GpuVideoDecoder" is present in the properties section.

Unfortunately, at present, our h264 hardware decoder implementation uses copy-back, so it may not work as smoothly as IE in this case ( issue 464774  tracks this to some extent).
Comment 17 by x.ran...@gmail.com, Jul 19 2015
Lena, no idea how it works for you, when I still have forced vp9 with h264ify enabled. Win7\8.1\latest Chrome. Absolutely useless plugin.
Sign in to add a comment