madVR - high quality video renderer (GPU assisted)

[Sunspark]

Thanks for animating it. At first glance the 1070 looks fine, but when you see it popping back and forth, you can really see that it's almost like they placed a blur filter after the initial rendering. Shocking that a graphics company like NVIDIA could trip over their feet like this, and for years apparently.

You can still use the DXVA2-Native decoding, as long as you don't use the chroma or image scaling which is easy enough to set with every directshow renderer.

So where power consumption comes into play, this is tricky.. mpcvr has lower power consumption than madvr by a lot, but it's dxva all the way unless you disable dxva scaling in the filter options.. in which case it will use shaders instead.. but the only option there is catmull-rom (bicubic 50, and I don't know if they do anti-ringing or not). I didn't test the power consumption of the shaders. I think they are working on adding more. Maybe you could test this.

Madvr power consumption.. I was taking notes on that for my stuff.. it's tricky.. there's a lot of output paths.. d3d9 overlay, d3d9 exclusive, d3d11 exclusive, d3d9 windowed, d3d11 windowed, (each of these 2x, because you have old path which is backbuffers and new path which is frames in advance) so there are in total nine different output paths to check the power on against 4 different decoders (software, cb, dxva2 native, d3d11) so 36 combinations. You can't use DXVA scaling in D3D11 presentation, it will use bilinear for image scaling, but using dxva2 as the decoder works just fine with d3d11 for presentation. I'm using d3d9 overlay, but it's not actually the best power consumption, it's actually twice the gpu load of some of the other paths, but I am using it because I was doing extensive testing of a panning movement segment and found that this particular setting was "smoother" in motion than others. Was really tough, because in a regular window it was smooth, but as soon as it goes fullscreen it's not as smooth anymore and it's not related to the refresh rate, it's something to do with the compositor. So, I can have less power consumption if I use dxva2-cb because it uses half the gpu load with overlay but it won't be as smooth looking as when native is used. The extra conversion work madvr has to do has some kind of beneficial quirk that makes it smoother on this hardware.

d3d9 overlay w/ copyback, d3d11 presentation windowed and exclusive w/ d3d11 decoding used the least power for me. This is for madvr chroma scaling not dxva scaling. All the rest used more power. Nvidia will be different.

GPU-Z is good for viewing gpu load.

[huhn]

even if you don't scale chroma with DXVA native it will still move the image. this is a basic problem with madVR and DXVA processing using a an NVIDIA card.

mpcVR will move the chroma to but only if also some kind of DXVA processing is used.

[flossy_cake]

Originally Posted by huhn

even if you don't scale chroma with DXVA native it will still move the image. this is a basic problem with madVR and DXVA processing using a an NVIDIA card.

mpcVR will move the chroma to but only if also some kind of DXVA processing is used.

Forgot to check that combination (DXVA2-native decode + MadVR chroma) and it appears to be shifted even worse -- diagonally down and to the right.
https://i2.lensdump.com/i/t7qJUm.png
https://i3.lensdump.com/i/t7qVZi.png

Originally Posted by Sunspark

I was doing extensive testing of a panning movement segment and found that this particular setting was "smoother" in motion than others. Was really tough, because in a regular window it was smooth, but as soon as it goes fullscreen it's not as smooth anymore and it's not related to the refresh rate, it's something to do with the compositor.

Not sure if it's related, but I recently solved a long standing issue with dwm stutter on Windows 7 by adding this regkey
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM\Schedule]
"FrameRateMin"=dword:000000c8

(c8=200fps)

[Sunspark]

flossy_cake, well that's it for NVIDIA then. For MadVR in LAV video settings, hardware decoder to use either "None","DXVA2 (copy-back)" or "D3D11" (not Automatic in drop-down to force copy-back) and for MPCVR uncheck the first 4 boxes in the "DXVA2 and D3D11 video processor" group which will force shader processing instead since huhn indicated native decoding would still work just not the processing.

That should simplify power testing a bit.

I wonder why one of the big tech sites never embarrassed NVIDIA over this. One would think this would be great marketing for AMD.

[huhn]

i guess it is better to not tell you about amd...

[bob88]

Hello,
Please help me get HDR working with MPC-HC and madVR.
I have all the required hardware and am running Windows 11 with an HDMI hooked up to an HDR movie projector. Widows HDR checkbox is on.
Here is the info that I get:

As far as I understand BT.2020 is being converted to DCI-P3. Why? Why does it not remain at BT.2020?
Also why is it rendered at 8 bit when I have set madVR like this:

and the projector should work at 10bit:

and the movie is also 10bit:

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 42 min
Bit rate : 16.9 Mb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.115
Stream size : 12.1 GiB (71%)
Title :
Writing library : x265 2.8+54-79c76e42cb28:[Windows][GCC 7.3.1][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=16 / numa-pools=24,24,24,24 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x1600 / interlace=0 / total-frames=0 / level-idc=51 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / repeat-headers / annexb / aud / hrd / info / hash=0 / no-temporal-layers / no-open-gop / min-keyint=1 / keyint=24 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / radl=0 / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=3 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / no-sao / no-sao-non-deblock / rd=3 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=16.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=160000 / vbv-bufsize=160000 / vbv-init=0.9 / crf-max=0.0 / crf-min=0.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=1 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50) / max-cll=1000,986 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / opt-qp-pps / opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / hdr / hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-mv-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primar : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Le : 986 cd/m2

Also on a sidenote, is there a way to convert SDR movies to HDR via a filter. I have pixel shader pack for MPC-HC. It has filters that are BT.709 to BT.601 but there is no BT.709 to BT.2020... Know where I can get one?
Thank you.

[varekai]

@bob88
Be quick and edit out this: Title : ***

[bob88]

Originally Posted by varekai

@bob88
Be quick and edit out this: Title : ***

haha! thanks...
any ideas on the HDR thing?
please guys help me. I am tortured by this for weeks...

[Alexkral]

About the color conversion:

https://forum.doom9.org/showthread.p...55#post1840255

[bob88]

Originally Posted by Alexkral

About the color conversion:

https://forum.doom9.org/showthread.p...55#post1840255

Thank you for replying.
So from what I understand regardless of the DCI-P3 thing its working properly.
The post also talked about some calibration which I had not done. I set it up like this but Im not sure it makes a difference. Is this proper:

Also do I need to do anything with this:

And what does this do?

[Alexkral]

For HDR passthrough these settings are not used, so there is no difference between specifying them as you do, or disabling calibration.

Gamma processing is also for SDR output, and is usually not needed.

"disable desktop composition" disables Aero on Vista and Windows 7.

[bob88]

Originally Posted by Alexkral

For HDR passthrough these settings are not used, so there is no difference between specifying them as you do, or disabling calibration.

Gamma processing is also for SDR output, and is usually not needed.

"disable desktop composition" disables Aero on Vista and Windows 7.

Ah ok!
Well after further testing I can confirm that regardless of it saying "-> DCI-P3" HDR is working! YAY!
Thank you for your help.
The only question I remain with is is there anywhere I can find a BT709 to BT2020 hlsl filter which I can use in MPC-HC? If anyone knows where I can find it I would love to try it out.
Thanks!

[huhn]

device-> "device name" -> calibration -> this display is already...
set it to bt 709 and it will turn everything to bt 709 except HDR passthrough which needs bt 2020 to be send at all times.

[bob88]

Originally Posted by huhn

device-> "device name" -> calibration -> this display is already...
set it to bt 709 and it will turn everything to bt 709 except HDR passthrough which needs bt 2020 to be send at all times.

Ah Ok I understand how that works. But perhaps you did not get my question. I want to turn BT709 movies to BT2020 via an MPC-HC shader.
I have a pixel shader pack for MPC which has a BT601 to BT709 shader.
I am looking for the next step...
But since I dont understand how the whole thing works perhaps using such a shader is pointless and it will not turn my SDR movies to HDR... so tell me if my request is dumb.

[huhn]

you set that setting to bt 2020 and that's what will happen.

and no this will not turn it to HDR because HDR is not bt 2020 that's a gamut.

[clsid]

Disable HDR in Windows, and let madVR turn it on only when needed.

You can not turn SDR video into HDR.

[Siso]

Originally Posted by clsid

Disable HDR in Windows, and let madVR turn it on only when needed.

You can not turn SDR video into HDR.

Very well said.

[70MM]

Would some of the experts here who use 113 mind sharing their HDR to SDR settings page please?
Im curious why many untick most boxes and others have most ticked, can you explain the reasons please?

[SirMaster]

Originally Posted by 70MM

Would some of the experts here who use 113 mind sharing their HDR to SDR settings page please?
Im curious why many untick most boxes and others have most ticked, can you explain the reasons please?

This is what I use on my projector that is about 85 nit peak white.

https://nicko88.com/misc/madVR%20set...%20-%20hdr.png

I quite like the effect of putting a lower peak nits and using the no compression limit to compensate. This helps increase the effect and the effective range of contrast recovery while still using a lower strength curve option.

[Sunspark]

I was checking something with ShowRenderSteps and there is a line that says chroma 4:2:0 -> 4:2:2.

I do not have full understanding of this.. my display is 4:4:4 (verified) and I have made the observation that if I deselect the 4:2:0 and 4:2:2 rows in LAV it does not label or use the chroma upscaling algorithm and the HUD appears as "h264, 8 bit, 4:2:0 -> RGB32, 8 bit, RGB". What am I missing here?

Ideally, chroma would upscale to 4:4:4 if possible.