Use D3D11 DXVA on Windows 7




3 years ago
2 years ago


(Reporter: mattwoodrow, Unassigned)


Firefox Tracking Flags

(Not tracked)



(2 attachments)



3 years ago
Created attachment 8731021 [details] [diff] [review]

We currently don't use D3D11 DXVA on Windows 7, since the MediaFoundation Transform we use for converting from YUV -> RGB isn't available.

The underlying DXVA APIs have all backported though (as of the Platform Update), so it should be possible to get things to work.

The attached patches attempt to do this, but seem to randomly pick between 0-255 and 16-235 color spaces on the machine I was working with at least.

It seems like this might be a bug in the driver, or DXVA.
We need this because it fixes a bunch of the D3D9 DXVA issues.
Priority: -- → P1
Mass change P2 -> P3
Priority: P2 → P3
Hi, Matt,

I would like to help this bug, but I don't know what's the main problem now, because you already have done the patch. Does the problem now is "randomly pick between 0-255 and 16-235 color spaces"? 

In addition, could you give me some suggestions for this bug if I want to take it and move it forward?
Flags: needinfo?(matt.woodrow)

Comment 5

3 years ago
Hi Alastor,

I got stuck (which is why this never got finished), so it's hard to say exactly what needs to be done next.

A good start would be to take the patches and getting them to build again and work again.

I'd then test them out of various Win7 machines (with different GPU manufacturers, drivers etc) and see if you can reproduce the problem (color space changes randomly, so you see color flicking while playing video).


If the issues persist on every machine, then start looking into ways to fix it. I got really stuck with this, but you might be able to think of something. Contacting Microsoft to ask them (assuming it's their problem if it affects all GPUs) might be worthwhile.

If it's only limited to specific GPU/drivers, then we could look at adding blacklisting/whitelisting as necessary so at least some users can have this.
Flags: needinfo?(matt.woodrow)
You need to log in before you can comment on or make changes to this bug.