Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MPC Video Renderer: Frequently Asked Questions #2869

Open
clsid2 opened this issue Jun 24, 2024 · 0 comments
Open

MPC Video Renderer: Frequently Asked Questions #2869

clsid2 opened this issue Jun 24, 2024 · 0 comments

Comments

@clsid2
Copy link
Owner

clsid2 commented Jun 24, 2024

For additional questions or bug reports, go to this topic.

Does this renderer support HDR video?

Yes!
It supports both HDR passthrough to a HDR display, as well as tonemapping to SDR for older displays.

Does this renderer support Dolby Vision?

Yes. It supports most (but not all) variants of Dolby Vision.
DV gets converted into HDR or tonemapped to SDR (depending on your settings).

Why does my screen go black for a (few) second when playing HDR video?

That means that your display is switching display mode to HDR.

If you do not like this behavior, you have the following choices:

  1. Turn on HDR permanently in Windows settings.
  2. Turn off HDR passthrough in MPC Video Renderer settings. Then HDR video will get tonemapped into SDR video.

Tip: in the Windows HDR dropdown setting in MPCVR settings, you can adjust when the renderer is allowed to switch display mode. For example you can allow it only when going fullscreen.

4k video has bad quality when downscaled (to 1080p)

This is a "bug" in NVIDIA driver. It uses a bad quality scaling algorithm when using the D3D11 video processor. I suggest reporting this bug to NVIDIA so that they can improve their driver.
EDIT: This reportedly has been fixed in 560.70 driver.

Workarounds:

  1. Turn off Use Direct3D 11 setting in MPC Video Renderer options. Then it will use DXVA2 scaling instead of D3D11. That might work better on your system.
  2. Uncheck Use for resizing in the video processor section. Then the video renderer won't use DXVA2/D3D11 at all for scaling, but uses PixelShaders instead. You can then adjust scaling algorithm in Shaders section. Tip: the bottom choices are generally the best quality algorith. Using Shaders does means a bit higher GPU usage.

HDR video is a bit too dark (or too bright) when tonemapped to SDR

You can use the SDR Display Nits option to adjust the tonemapped brightness. Lower value means brighter.

Default value is 125. Older monitors are often 100 nits. Projectors even lower.
Modern monitors can have higher brightness.
If you have significantly reduced brightness setting of your monitor, then a lower display nits setting may look better.

Which hardware decoder should I use in LAV Video?

If you use Direct3D11 in the video renderer, then recommended choice is D3D11.
Otherwise use DXVA2 Native.
Note that modern GPUs which support hardware decoding of AV1 video, usually only support it with D3D11.

How can I see debug details about the input video and renderer processing?

Press Ctrl+J to show the renderer debug OSD.

When you are submitting a bug report or question, the developers usually want a screenshot with this information enabled.

I get a black screen when playing 10-bit video

This may happen with for example AMD Vega and RX5xx GPUs. I suggest reporting this bug to AMD so that they can improve their driver.

Workaround:
Uncheck P010 in the video processor section of MPC Video Renderer options. It will then use Shaders to process 10-bit video. Instead of unchecking P010, you can also try unchecking Use Direct3D 11 first.

Color controls in player do not work with 10-bit video

Another AMD bug. Same workaround as above.

Deinterlacing does not work with AMD GPU

Deinterlacing with AMD GPUs requires Future Frames implementation when using the D3D11 video processor. Currently MPC Video Renderer does not support Future Frames.

Workaround is to uncheck Use Direct3D 11.

Repository owner locked and limited conversation to collaborators Jun 24, 2024
@clsid2 clsid2 pinned this issue Jun 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant