[vlc-devel] [PATCH 00/14] Handle native Windows 10 transfer functions

[Hugo Beauzée-Luyssen]

On Mon, Mar 20, 2017, at 05:28 PM, Steve Lhomme wrote:
> In Windows 10 it's possible to force the transfer function and colorspace
> if the hardware supports it. This set of patches make use of this
> possiblity.
> It gives much better result than manually handling them in the pixel
> shader.
> 
> I also reworked the range handling as it should be done after everything
> is
> done, just before displaying.
> 
> The first few patches are doing some cleaning to prepare the next patches
> and
> make debugging a little nicer.
> 
> Steve Lhomme (14):
>   direct3d11: factorize the same string usage
>   direct3d11: log the Pixel Shader stages in debug builds
>   direct3d11: avoid passing through all the code for nothing in debug
>     builds
>   direct3d11: rename COLORSPACE_RGB_FULL as it's used for other things
>   direct3d11: add a function to determine if a shader will be for RGB or
>     YUV
>   direct3d11: fix typos in ST2084 pixel shader
>   direct3d11: add support for transfer conversion for BT.709 and sRGB
>     sources
>   direct3d11: do the tone mapping for HLG sources too
>   direct3d11: fix the HLG to Linear luminance
>   direct3d11: only saturate before delivering the RGBA
>   direct3d11: list the colorspaces supported by the swapchain
>   direct3d11: pick the best swapchain colorspace for the source video
>   direct3d11: rework the full/studio range adjustement
>   direct3d11: adjust the max luminance based on the source and output
>     transfers
> 
>  modules/video_output/win32/direct3d11.c | 461
>  +++++++++++++++++++++++++-------
>  1 file changed, 362 insertions(+), 99 deletions(-)
> 

Pushed, except for patch 2 (former patch 3)

Thanks!

-- 
  Hugo Beauzée-Luyssen
  hugo at beauzee.fr