Media Player Classic - BE Win32/x64

[Aleksoid1978]

Originally Posted by LuckyJim

Speaking of youtube videos, something strange is going on.

Using the built-in web page parser:
When the video finishes playing, MPC-BE freezes and stops reacting. Clicking the close button does nothing. Clicking it a second time pops up a dialog "The application is not responding. Do you want to end this process?".
No stacktrace files or minidumps are created. No errors in the Event Viewer either.

When using the yt-dlp parser everything is fine, no freezes etc.

MPC-BE x64 v1.8.3.9 dev Portable
MPC VR x64 v0.9.4.2365
NVIDIA Driver v572.16
Win11 24H2, build 26100.3194

Any ideas?

Can't confirm, all is good.

[LuckyJim]

Originally Posted by Aleksoid1978

Can't confirm, all is good.

Thanks for looking into this, Alex! Mea culpa! I reset my settings and now everything is perfect, no freezes. I wonder what went wrong.

Regards!

[LuckyJim]

Sorry for the spam, folks! Just wanted to let you know, that the culprit for the freezes at the end of the videos was LAV Splitter Source (v0.79.2.27).
Disabling it and enabling the internal source filters fixes the problem.

Regards!

ETA: LAV version

[Megalith]

Two questions:

1. What exactly do the swap effect (discard/flip) options do? Does it have any effect on video quality?

2. For MPC Video Decoder, what is the best decoder option to use? Is NVDEC preferred if I'm on an NVIDIA GPU?

[v0lt]

Originally Posted by Megalith

1. What exactly do the swap effect (discard/flip) options do?

For D3D11 see DXGI_SWAP_EFFECT
For D3D9 see D3DSWAPEFFECT

Does it have any effect on video quality?

No. It does not affect the picture quality.

2. For MPC Video Decoder, what is the best decoder option to use?

This is a stupid question because all decoders usually produce the same picture. We recommend D3D11 decoder for better performance.

Is NVDEC preferred if I'm on an NVIDIA GPU?

Usually no. But you can have your own opinion.

[huhn]

discard d3d11 is bugged and will produce massive banding in 10 bit mode.

[Klaus1189]

Updated german translation

[cmhrky]

Updated Turkish translation.

[wushantao]

Updated Simplified Chinese
：）
https://files.catbox.moe/4on2ob.7z
https://seyarabata.com/67bd425887309

[ikarad]

Good morning.
I have one question about mpc video renderer.
Is there a tutorial explaining how the MPC Video Renderer options work?
Thanks by advance and Excuse me if this is not the right place to ask this question.

[huhn]

maybe just ask what you want to know.
the default are fine the video renderer doesn't need special setup it works on pretty much everything and is the definition of efficiency.

[v0lt]

Thanks. Translations have been updated.

Originally Posted by ikarad

Is there a tutorial explaining how the MPC Video Renderer options work?

There is a brief description of the settings in Russian.
https://mpc-be.org/forum/index.php?t...sg3522#msg3522

[ikarad]

Originally Posted by v0lt

Thanks. Translations have been updated.


There is a brief description of the settings in Russian.
https://mpc-be.org/forum/index.php?t...sg3522#msg3522

Thanks but I don't read russian. Sorry.

I have tried to translate with ia chatbot.
"Settings Description
Use Direct3D11

The video renderer will use Direct3D 11 instead of Direct3D 9 whenever possible. Requires Windows 7 SP1; Windows 8.1 or newer is recommended.
Texture format

Specifies the texture format used for storing intermediate processing results.
Note: The 16-bit Floating Point format increases video memory consumption.
Show statistics

Displays an overlay with various statistics on top of the video frame. It is recommended to enable this option when taking a screenshot to diagnose issues.
DXVA2 and D3D11 Video Processor
Use for: NV12, P010/P016, YUY2, Other supported formats

Defines which formats will use the DXVA2 or D3D11 video processor when possible.
DXVA2 and D3D11 video processors are typically faster than shaders and also support deinterlacing.
Note: Interlaced frames are usually in NV12 or YUY2 format.
Double the frame rate when deinterlacing

When deinterlacing, the output frame rate will be doubled.
Use for resizing

The DXVA2 or D3D11 video processor will be used for resizing frames.
This method is fast but may reduce quality.
For example, Nvidia GPUs use bilinear interpolation (lower quality), while Intel GPUs use bicubic interpolation (better quality).
Request Super Resolution

Requests the use of Super Resolution if supported by the graphics adapter and drivers.
Expected to work on Intel Gen10+ and RTX 30/40 series GPUs with updated drivers.
Shader Video Processor
Chroma scaling

Algorithm for upscaling the chroma component from 4:2:0 and 4:2:2 to 4:4:4.
Upscaling

Interpolation algorithm used for enlarging frames.
Downscaling

Algorithm used for reducing frame size.
Use the "Upscaling" method to reduce the frame to 50%

The Upscaling algorithm will also be used when reducing the frame size to 50%.
Use dithering

Enables dithering when reducing color depth from 10-bit/16-bit to 8-bit.
Dithering can improve the display of smooth gradients. However, the effect may not be noticeable on small screens.
Use Blend deinterlacing for YUV 4:2:0

Applies simple Blend deinterlacing to frames marked as interlaced.
HDR Settings
Prefer Dolby Vision over PQ and HLG

This option prioritizes Dolby Vision over PQ (Perceptual Quantizer) and HLG (Hybrid Log-Gamma) formats.
By default, this is disabled, as the image quality change is minimal, but GPU load increases significantly.
Passthrough to display

Passes HDR video metadata directly to the display.
Requirements:

Windows 10
HDR10-compatible display
GPU supporting HDMI 2.0b or DisplayPort 1.4

Windows HDR

Automatically switches the display to HDR mode.
Requirements:

Windows 10
HDR10-compatible display
GPU supporting HDMI 2.0b or DisplayPort 1.4

Subtitle and OSD brightness

Adjusts the brightness of subtitles in HDR videos when Passthrough to display is enabled.
Convert to SDR

Converts HDR video to SDR for proper display on non-HDR screens.
SDR display nits

Defines the estimated brightness level (in nits) of the SDR display, used for HDR-to-SDR conversion.
Other Settings
Swap effect

Determines how frames are displayed on the desktop.

Discard mode is generally more stable.
Flip mode can be faster.

Use exclusive fullscreen

May resolve stuttering playback issues on additional monitors.
Wait for V-Blank before Present

Ensures precise frame output timing, which may improve playback smoothness.
This setting helps the SyncOffset graph better reflect frame timing irregularities.
Reinitialize D3D device when changing display

When moving the window to another monitor, the Direct3D device will reset and reinitialize.
This helps resolve issues in multi-monitor setups.
"
Is it a correct translation ?

[s0meone_new]

Hungarian translation updated:
https://easyupload.io/44yzyk

[y8jhoM]

Why does madVR report doubled vertical resolution when used with MPC-BE built-in filters? With LAV filters, a 1920x800 video is seen as 1920x800 by madVR (in Ctrl+J overlay), but with MPC-BE filters the same video is seen as 1920x1600 (in Ctrl+J overlay). No upscaling is applied in either case.

Also, is there performance benefit to using MPC-BE native video filter DirectX 12 Copy-Back compared to LAV video filter DirectX 11 native? I use madVR that does not utilize DirectX 12 (yet).

[v0lt]

@ikarad
I don't see the point in writing a machine translation here. Windows has the Edge browser, which has a built-in web page translator.

@s0meone_new
Thanks. Updated.

@y8jhoM
The "Copy-Back" mode for the hardware decoder will always be slower than the "Native" modes. It's obvious.

[beter]

Update for translation of Chinese Traditional and Dutch

https://mega.nz/file/ubY3mKII#7LMUux...m9iTv97gaXZixE

[huhn]

what does "wait for vblank before presentation" and "adjust the frame presentation time" exactly do?

[v0lt]

@beter
Thanks. Updated.

@huhn

Wait for V-Blank before Present
The renderer will wait for a V-Blank event before calling Present. This allows for more accurate frame output timing. This allows the SyncOffset graph to more accurately reflect frame output jitter.
This setting may affect video smoothness. Disabled by default to avoid annoying users with a sawtooth graph.

Adjust the frame presentation time
The renderer will wait additionally before displaying a frame to more accurately hit the required display refresh time. This setting helps smoothly play interlaced video with double the frame rate (50/60 fps) on displays with a high refresh rate (120 Hz and higher).

[huhn]

first of all thanks for your time.

Originally Posted by v0lt

Wait for V-Blank before Present
The renderer will wait for a V-Blank event before calling Present. This allows for more accurate frame output timing. This allows the SyncOffset graph to more accurately reflect frame output jitter.
This setting may affect video smoothness. Disabled by default to avoid annoying users with a sawtooth graph.

does it simply display a frame every let's say 25 sec with a 25 FPS source and the windows "DWM" to handle that. or is some type of sync still done but not shown?

Adjust the frame presentation time
The renderer will wait additionally before displaying a frame to more accurately hit the required display refresh time. This setting helps smoothly play interlaced video with double the frame rate (50/60 fps) on displays with a high refresh rate (120 Hz and higher).

can it even do that with the Wait for "V-Blank before Present" aren't these very fixed timings?

or is this more of a case to even have proper frame times instead of it been presenting the frames when it is done rendering?

example 240 hz monitor 24p source and video render times are 1-5 ms if it would take 5 ms and it would directly present the frame after rendering it will create some "judder" in the process because it is now a vsync interval late?