0000604: madVR can use DXVA for chroma upscaling in 8bit (NV12 and RGB32) and in 16bit (P016) but not in 10bit (P010)

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000604

madVR

bug

public

2019-03-10 12:32

2019-09-10 20:40

Reporter

vanden

Assigned To

Priority

normal

Severity

minor

Reproducibility

always

Status

new

Resolution

open

Platform

DL580G5+GTX650Ti

Windows 10 Ent x64

OS Version

1809

Summary

0000604: madVR can use DXVA for chroma upscaling in 8bit (NV12 and RGB32) and in 16bit (P016) but not in 10bit (P010)

Description

For all the tests following LAV is in SOFTWARE Decoding Mode, File 1440p 10bit HDR (MPCHC x64).

If I uncheck P010 in LAV : LAV makes the converssion 10bit->16bit and in madVR I enter in 16 bit 420 (P016) and madVR makes a chroma upscaling in DXVA Mode !!!
I guess the HDR ton mapping is done in 16bit in this case ? but it does not have to be really embarrassing.
it works well GPU stable @ 58% CPU @ 15% :
https://imagizer.imageshack.com/img921/6238/o79YuP.jpg [^]

If I uncheck P010 and P016 in LAV : LAV makes the convention 10bit->16bit in madVR I enter in 8bit 420 (NV12) and madVR makes a chroma upscaling in DXVA Mode !!!
I guess the HDR ton mapping is done in 8bit in this case ? Not ideal if that's the case.
it works well GPU stable @ 55% CPU @ 12% :
https://imagizer.imageshack.com/img923/9442/UcpGTF.jpg [^]

If I uncheck all 420 (NV12, YV12, P010 and P016) and 422 (YuY2, UyUV, P210, v210 and P216) in LAV : In madVR I enter in RGB32 (LAV does chroma upscaling with I do not know what algorithm + convention YUV to RGB).
I guess the HDR ton mapping is done in 8bit in this case ? Not ideal if that's the case.
it does not work well, some presentation glitches GPU @ 79% CPU @ 19% :
https://imagizer.imageshack.com/img922/3079/WpxyNY.jpg [^]

If I have everything checked in LAV : in madVR I enter in 10bit 420 (P010) and madVR does a chroma upscaling using TextureUnits/PixelShader (Bilinear, Cubic ...) and it does not work GPU @ 92% CPU @ 17% :
https://imagizer.imageshack.com/img924/3286/fv9OiE.jpg [^]

If I have everything checked in LAV and screen set @ 2944x1656 : in madVR I enter in 10bit 420 (P010) and madVR makes a chroma+Luma upscaling (2560x1440->2944x1656) in DXVA Mode.
it works well GPU stable @ 71% CPU @ 16%
https://i.goopics.net/wEv2y.jpg [^]

So madVR can use DXVA for chroma upscaling in 8bit (NV12 and RGB32) and in 16bit (P016) but not in 10bit (P010) ! it's very weird anyway !

[U]Edit :[/U]
For all tests following LAV is in SOFTWARE Decode Mode, File 3840x1606 10bit HDR (MPCHC x86 + Reclock). Screen in 3104x1756 and in MPCHC : Video Frame/Normal Size.

All the tests by modifying LAV does not work (NV12, P016, RGB32), example in NV12 :
https://imagizer.imageshack.com/img921/8541/1MFFhC.jpg [^]

On the other hand If everything is ticked in LAV (P010) and I put -2% on the zoom in MPCHC (the image is resized in 3766x1576 / via DXVA chroma+Luma upscaling) it goes :
https://imagizer.imageshack.com/img922/2303/Fw3uXy.jpg [^]

I guess in P010 and just DXVA choma upscaling it would be perfect ...

Steps To Reproduce

alway with all P010 files

Tags

No tags attached.

madVR Version

0.92.17

Media Player (with version info)

MPC HC x64 1.84 + MPC HC x86 1.8.4

Splitter (with version info)

LAV 0.73.1

Decoder (with version info)

LAV 0.73.1

Decoding

Software

Deinterlacing

none (progressive)

DXVA2 Scaling Active

yes

Aero / Desktop Composition

Problem occurs with mode

windowed mode

GPU Manufacturer

NVidia

GPU Model

GTX650Ti

GPU Driver Version

417.71

Attached Files

Relationships

Notes
(0002500) vanden (reporter) 2019-03-10 12:37 edited on: 2019-03-10 16:10	if I uncheck P010 and P016 in LAV : LAV makes the convention 10bit->8bit i't's not 16 but 8 .... Scaling algorithms (For all tests) : - chroma upscaling = Bilinear - image downscaling = DXVA2 - image upscaling = DXVA2

(0002554) vanden (reporter) 2019-09-10 20:40	No news ??

Issue History
Date Modified	Username	Field	Change
2019-03-10 12:32	vanden	New Issue
2019-03-10 12:37	vanden	Note Added: 0002500
2019-03-10 16:10	vanden	Note Edited: 0002500	View Revisions
2019-09-10 20:40	vanden	Note Added: 0002554