[Bug] Green screen at right side of video

[bibsp]

MPC VR can not play one of my videos properly when D3D11 is checked in renderer settings. Which is enabled by default in the latest version you know. When I unchecked D3D11 in renderer settings then the problem is gone.

Why is it happening? This needs to be fixed or D3D11 should be disabled by default as before it was.

[Using win 10, MPC HC x64 latest. Don't know the problem is there in MPC BE or not? I use MPC HC only]

[Klaus1189]

Upload sample file to google drive or similar

[bibsp]

I have trimmed the video to save my mobile data, without re encoding using Avidemux. The trimmed video is also having same issue, so you can check this.

https://drive.google.com/file/d/1YX7Jxs0jiZEKOS1NJKTQRLXUCOFKbLw6/view?usp=sharing

[And also you are aware of the issue that MPC HC freezes randomly when using MPC VR. CPU usage drops to zero at that situation. Audio stills plays. No such problem when using EVR CP. I have seen that many people reported that issue at different places but no proper solution found]

[Klaus1189]

I tested it using MPC-BE with internal Filters and with external LAV Filters with both EVR custom and MPC Video Renderer in both D3D9 and D3D11 and never experienced an problem.

What GPU do you use? What driver is installed? Can you please download the latest stable or nightly to test with MPC-BE: latest stable: https://sourceforge.net/projects/mpcbe/files/MPC-BE/Release%20builds/1.6.1/ latest nightly: https://disk.yandex.com/d/hlf1lfC8mKU58/1.6.2.6893

Forgot to mention: I use latest stable MPC Video Renderer 0.5.6.1807

[Klaus1189]

I just googled the Nikon and found a videoclip straight from the cam: https://img.photographyblog.com/reviews/nikon_coolpix_l26/sample_images/nikon_coolpix_l26_01.avi

[bibsp]

Intel hd graphics 4400 Driver 10.18.15.4248

This version is download from hp's driver page. There is a newer version available in intel website but that version has something issue with my laptop. Doesn't work properly. So i use that version instead of newer one.

[bibsp]

I just googled the Nikon and found a videoclip straight from the cam: https://img.photographyblog.com/reviews/nikon_coolpix_l26/sample_images/nikon_coolpix_l26_01.avi

Same issue in this video. If I untick Direct3D 11 in MPC VR settings then there is no issue.

If the issue is only in my system then it must be some driver related issue. Leave it. Thanks for your time.

[Aleksoid1978]

Enable statistics in MPC VR - "Show statictics" in options. And take a screenshot.

[clsid2]

4:2:2 chroma is probably what make this file different from others.

[bibsp]

MPCVR default settings vs Direct3D 11 unchecked

[bibsp]

4:2:2 chroma is probably what make this file different from others.

That MJPG codec is very rare. Is that a problem?

[Klaus1189]

D3D11VP caused already some problems on old GPUs.

[bibsp]

Then default settings of MPCVR should be reverted to that of previous version. Because DXVA2 does not have problem with old GPUs.

[Aleksoid1978]

No, we will not remake for old hardware/drivers. This is not a renderer issue, but a video driver issue. You can uncheck "YUV2" in MPC VR settings to disable D3D11 VP(video processor).

[clsid2]

Try if disabling "Contrast Enhancement" in the Intel driver settings helps. That is buggy with some drivers.

[bibsp]

That settings is already disabled, as you told before. Disabling Direct3D 11 fixed the problem for me.

[v0lt]

I cannot reproduce the problem. Intel HD 4000, Win10 x64, MPC VR 0.5.7.1813

[clsid2]

Maybe the target resolution is the issue? 1365x768 is uneven width.

[v0lt]

Changing the target resolution does not cause a bug.

[bibsp]

There are so many videos of same res. 1280x720. Same target res. 1365x768 No issue with them. Driver bug may be or input format

[Aleksoid1978]

As i say before - You can uncheck "YUV2" in MPC VR settings to disable D3D11 VP(video processor).

[bibsp]

As i say before - You can uncheck "YUV2" in MPC VR settings to disable D3D11 VP(video processor).

Yes I have done it. No issue when YUV2 is unchecked. Working well.

Basically my last comment was reply to clsid2's last comment. Close the issue if u want.