There may be situations where we need to play video as RGBA16F (DXGI_FORMAT_R16G16B16A16_FLOAT), depending on surface promotion decisions - as in sotaro's testing, Windows DWM seems to flicker if using more than one swapchain, so more than one video would be an issue, in which case we'd still want to promote the video for HDR reasons, but as a surface rather than a swapchain. For now I am prototyping video using RGBA16F as it has the least considerations to deal with (e.g. we don't have to call [IDXGISwapChain3::SetColorSpace1](https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_4/nf-dxgi1_4-idxgiswapchain3-setcolorspace1), DWM knows that RGBA16F is always scRGB).
Bug 1977746 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There may be situations where we need to play video as RGBA16F (DXGI_FORMAT_R16G16B16A16_FLOAT) if it has transparency (AV1 I believe supports that?) - this also technically means it could be displayed as a surface rather than a swapchain if that is useful, surfaces can't be DXGI_FORMAT_R10G10B10A2_UNORM format but they can be DXGI_FORMAT_R16G16B16A16_FLOAT). For now I am prototyping video using RGBA16F as it has the least considerations to deal with (e.g. we don't have to call [IDXGISwapChain3::SetColorSpace1](https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_4/nf-dxgi1_4-idxgiswapchain3-setcolorspace1), DWM knows that RGBA16F is always scRGB).