Open Bug 1932998 Opened 1 year ago Updated 1 year ago

Refactor DXVA2 manager

Categories

(Core :: Audio/Video: Playback, task, P3)

task

Tracking

()

People

(Reporter: alwu, Assigned: alwu)

References

Details

We have this DXVA2Manager base class because we were used to support both D3D9 and D3D11, but now we only support D3D11. DXVA2Manager is lacking of the explanation about how this class should be used, and also doesn't mention if its functions are thread-safe or not. Some of its functions even have dependency but you can't tell that by simply checking its declaration, ie, you have to call function A before calling function B in order to get a proper result.

Sotaro, I wonder if we have any plan to use D3D12? I know that Chromium has a D3D12 decoder but I don't know if they use D3D12 for rendering or not. Thanks!

Flags: needinfo?(sotaro.ikeda.g)

There is a plan to use wgpu as WebRender's low level api instead of OpenGL in future. In this case, DX12 will be used on Windows. But Firefox still does not release WebGPU that uses wgpu. Then I am not sure when the plan will start.

chromium uses DX12 for WebGPU. Other graphics parts seems not use DX12, since video overlay and related part still uses DX11 APIs.

Flags: needinfo?(sotaro.ikeda.g)
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.