madVR - high quality video renderer (GPU assisted)

[JaylumX]

Originally Posted by interpolation

I'm trying to passthrough HLG using madvr, mpc-bc, and the latest Win 10. I can see that it says "transfer HLG" in the madvr info, but HDR doesn't switch on the TV. Of course, the file plays properly when played on the TV's internal player via USB.

If HLG passthrough isn't currently supported with madvr, is there any way to get it to work in Win 10? I saw a custom Kodi build that claims to trick Windows into outputting HLG as HDR10, but haven't tried it.

The MPC Video Renderer supports HLG. Just go to video renderer in the link.

Linkage

[huhn]

mpcVR does not support HLG passthrough output is uses the HLG to HDR 10 for passthrough.

[Aleksoid1978]

Originally Posted by huhn

mpcVR does not support HLG passthrough output is uses the HLG to HDR 10 for passthrough.

And it's "normal" working

[Sunspark]

Is MadVR not very compatible with Windows 10?

I have GPU usage of approx 28% (9% in Windows 7) and it doesn't seem to be related to the LAV filters decoding mode (tried them all as well as 3 different versions of LAV) or various madvr output settings (exclusive, windowed, overlay, backbuffers, etc). CPU usage is also higher than in 7 as well (13% vs 3%).

I copied over my Windows 7 MadVR install using an older version with different settings and it did not change the %s. So we know it's not specific to .92.17 here. It's not the player, because when I changed it to EVR-CP CPU, GPU %s then dropped to a more normal number.

Using DXVA2 for the downscaling and upscaling. Changing to something else like Lanczos does not improve things. All other players not using MadVR have significantly lower CPU and GPU usage.

So, what's different about the Windows 7 environment that it doesn't stress the system as much when playing a video? In Windows 10, the fans start whining because even though the CPU usage is about 13% the integrated GPU is at 28%.

[huhn]

window mode can easily add a overhead bigger than audio decoding you can observe this with the DWM process.

i get down to ~1% CPU cpu usage at below 800 mhz peak so basically 0 the % number is pointless here.

try overlay rendering and make sure you have driver supporting the current WDDM.
win 7 can't read the hardware decoder but 10 can that is far far higher then my idling GPU so the taskmanager shows 15 % from the decoder.
to test real power saving i need to disconnect displays i'm not going to do that.

[Matias]

Originally Posted by CZ Eddie

I tried DVBViewer but it doesn't seem to work for USA. Anyone know of any LiveTV software that can play DRM protected channels and works with MadVR?

Or even something that doesn't work for DRM playback but does support MadVR (other than JRiver)?

I don't have any DRM protected channels but maybe ProgDVB can do this, you must try.

[Sunspark]

Originally Posted by huhn

window mode can easily add a overhead bigger than audio decoding you can observe this with the DWM process.

i get down to ~1% CPU cpu usage at below 800 mhz peak so basically 0 the % number is pointless here.

try overlay rendering and make sure you have driver supporting the current WDDM.
win 7 can't read the hardware decoder but 10 can that is far far higher then my idling GPU so the taskmanager shows 15 % from the decoder.
to test real power saving i need to disconnect displays i'm not going to do that.

Thanks, and I actually am using D3D9 overlay rendering. I found it to present a smoother display which is why I am using it. Video driver is the one that Windows installed itself, and dxdiag confirms that it is WDDM 2.0. Possible it's a video driver issue, but odd in that it is only the madvr module that has the problem in 10.

GPU-Z will work in Windows 7 to show GPU % (as the task manager won't show it in that version). Also shows power watts. Not sure how accurate it is, but it's useful all the same.

The software is working and presents well, it just uses a lot of resources in Windows 10 and makes the fans spin up.

[huhn]

your WDDM version is 4-5 years old which suggest the driver is also that old.
the current release wddm is 2.7 the newest test is 3.0.
but this is a best a guess based on the fact that the WDM shows quite some CPU/GPU usage when an windowed image is shown.

there are some game tests which show that win 10 is clearly superior in performance and my systems has such low GPU and CPU usage that it's hard to make anything out of it.

[el Filou]

Whatever is the cause, 28% Vs 9% for GPU and 13% Vs. 3% for CPU (assuming the clocks are the same as huhn said) is a much bigger difference than anything possibly due to the OS, especially the GPU because WDDM 2.x is supposed to be more resource efficient than WDDM 1.1.

What hardware do you have?
When I set madVR to DXVA scaling on my desktop (1440p), it uses only 17% at 450 MHz on my old Radeon 7870 i.e. nothing, and my 4690K is only at 4,8% at lowest clock 800 MHz.

[Sunspark]

Originally Posted by el Filou

Whatever is the cause, 28% Vs 9% for GPU and 13% Vs. 3% for CPU (assuming the clocks are the same as huhn said) is a much bigger difference than anything possibly due to the OS, especially the GPU because WDDM 2.x is supposed to be more resource efficient than WDDM 1.1.

What hardware do you have?
When I set madVR to DXVA scaling on my desktop (1440p), it uses only 17% at 450 MHz on my old Radeon 7870 i.e. nothing, and my 4690K is only at 4,8% at lowest clock 800 MHz.

It's an Intel Core i5-5250U (Broadwell, 2 cores, 4 threads) using integrated graphics Intel HD Graphics 6000 (Broadwell GT3).

Turning off image scaling (Normal size vs touch window from inside) does not change the 28%.

Likewise, this high utilization does not happen with any other video renderer.. MpcVR, EVR-CP, whatever VLC uses, whatever Windows Film & TV uses, etc. only specifically with MadVR and it's not limited to .92.17 because I tried an older version (.90.17).

The issue does not occur on Windows 7. It's so strange, I can't figure it out.

Who knows, maybe it's a bug in Windows 10 itself.. MS has had a run of breaking things lately.

I suppose I should try installing the Windows 11 preview (if it lets me) into a partition and see if anything changes.

[el Filou]

Can you try to change Windows power plan from Balanced to High performance, just for a test? Or just change the power balance setting (forgot what it's called) in the Intel Graphics control panel ?

That's a 15W part which is not a lot, maybe it's getting in some power save mode where the clocks are much lower? Are you sure the playback clocks are the same as on Win7?
The utilization percentages are not a bad thing per se, it all depends on how much power it actually uses, but I don't see why they would differ so much.

[bitterman]

Originally Posted by Sunspark

Is MadVR not very compatible with Windows 10?

I have GPU usage of approx 28% (9% in Windows 7) and it doesn't seem to be related to the LAV filters decoding mode (tried them all as well as 3 different versions of LAV) or various madvr output settings (exclusive, windowed, overlay, backbuffers, etc). CPU usage is also higher than in 7 as well (13% vs 3%).

I copied over my Windows 7 MadVR install using an older version with different settings and it did not change the %s. So we know it's not specific to .92.17 here. It's not the player, because when I changed it to EVR-CP CPU, GPU %s then dropped to a more normal number.

Using DXVA2 for the downscaling and upscaling. Changing to something else like Lanczos does not improve things. All other players not using MadVR have significantly lower CPU and GPU usage.

So, what's different about the Windows 7 environment that it doesn't stress the system as much when playing a video? In Windows 10, the fans start whining because even though the CPU usage is about 13% the integrated GPU is at 28%.

I encounter the exact same issue.

Using:
Windows 10 21h1 (latest build)
MPC-HC 1.9.14
madVR 0.92.17
Nvidia drivers 471.11 (with a GTX 970)

[huhn]

check what part of the GPU it could be easily the hardware decoder.

[nevcairiel]

Percentages can also be rather misleading if the GPU has a dynamic clock. It could run at what seems a high percentage but run at a lower clock because the driver/OS figured out that this is plenty to do the task at hand.
If you really want to check, collect more data points with actual GPU monitoring tools (eg. GPU-Z might be the simplest that shows much more data), not task manager.

[ryrynz]

Anyone had any luck with automatic profile selection on a mounted ISO? I'm only using location and resolution as the conditions and both are correct but it's not taking.
MPC-BE even specifies the location in it's recent files list so it appears to be parsing this location correctly but madVR isn't having a bar of it.

[brazen1]

If I understand you correctly, auto profile selection has always worked perfectly for mounted iso's using resolution here.

if (srcWidth > 1920) and (deintFps < 25) "2160p 24fps"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p 24fps"
else if (srcheight <= 2160) and (deintFps > 58) "2160p 60fps"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "540p"

[ryrynz]

No issues with resolution, location is the problem.

if (srcHeight <= 480) and (filepath = "E:\*.*")
"480"

E: is the ISO mounted location.
I've also tried E:\Video_TS\*.* but that doesn't work either. I've had to resort to using an else statement to get it to select the appropriate profile.

Can anyone else confirm this?

[el Filou]

It works for Blu-ray ISOs but not DVDs.
I think it's because the DVD Navigator doesn't pass filename/path information (when opening VOB files directly, it works)?
I can see that also in ReClock, it says File: DVD from DVD drive (in mpc-hc) whereas with a BD ISO it shows the path of index.bdmv even when opening as disc.
I've tried with filename = "*DVD*" but it doesn't work either.

[Sunspark]

el Filou: I did try High Performance, it didn't change anything.

nevcairiel: These two images show the same file being played. It seems that something in Win10 is triggering heavier power consumption with madVR but I don't have an understanding as to what it could be.

[el Filou]

@Sunspark: can you create a file named ShowRenderSteps (with no file extension) in madVR's program files folder, and then take screenshots of madVR OSD during playback (wait for the clocks and GPU utilization to stabilize) on both Win7 and Win10 and compare the figures? To check if the GPU utilization is due to one particular step of madVR's pipeline or if all steps have higher rendering times on Windows 10.
(I know it's cumbersome, but I don't see another way to find out what is causing that much higher usage)