New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 623962 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Vp9 decoder mft support for AMD gpu/apu

Reported by kyle.plu...@amd.com, Jun 28 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Example URL:

Steps to reproduce the problem:
1.
2.
3. 

What is the expected behavior?

What went wrong?
Upcoming AMD drivers will ship with a vp9 decoder mft installed in C:\Program Files\Common Files\ATI Technologies\Multimedia. Support is initially limited to Bristol Ridge platforms, but will be expanded in the future.

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A 

Chrome version: 51.0.2704.103  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0
 
Cc: ananta@chromium.org jbau...@chromium.org ericde@chromium.org
Cc: -ericde@chromium.org dalecur...@chromium.org sande...@chromium.org
Owner: ericde@chromium.org
Status: Assigned (was: Unconfirmed)
this is a feature request. Eric, can you assess it?
Project Member

Comment 3 by bugdroid1@chromium.org, Aug 24 2016

I'm encountering a bug with DXVA decoding (stable channel). I dug a bit and noticed the --enable-accelerated-vpx-decode switch. However, the value of GpuPreferences::enable_accelerated_vpx_decode is initialized to VPX_VENDOR_MICROSOFT, so the switch seems to be a no-op. If this feature is supposed to be behind the flag, please change the initial value and merge the change to the release branches.

Comment 5 by kyle.plu...@amd.com, Oct 31 2016

My change didn't modify the default value. The MS decoder was enabled by default prior to my change, albeit in a less obvious way (imo). I believe this feature is enabled intentionally, but jbauman/dalecurtis can confirm expected behavior.

The way to completely disable this feature is to set --enable-accelerated-vpx-decode=0.
Owner: dougman@chromium.org
@dougman : do we have an AMD system we can verify / repro this on?

Sign in to add a comment