Possible it's a video driver issue, but odd in that it is only the madvr module that has the problem in 10. Video driver is the one that Windows installed itself, and dxdiag confirms that it is WDDM 2.0. I found it to present a smoother display which is why I am using it. Thanks, and I actually am using D3D9 overlay rendering. To test real power saving i need to disconnect displays i'm not going to do that. 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. Try overlay rendering and make sure you have driver supporting the current WDDM. I get down to ~1% CPU cpu usage at below 800 mhz peak so basically 0 the % number is pointless here. Window mode can easily add a overhead bigger than audio decoding you can observe this with the DWM process. 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%. All other players not using MadVR have significantly lower CPU and GPU usage. Changing to something else like Lanczos does not improve things. Using DXVA2 for the downscaling and upscaling. It's not the player, because when I changed it to EVR-CP CPU, GPU %s then dropped to a more normal number. I copied over my Windows 7 MadVR install using an older version with different settings and it did not change the %s.
CPU usage is also higher than in 7 as well (13% vs 3%). 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). Is MadVR not very compatible with Windows 10?
0 kommentar(er)
