Media Player Classic - BE Win32/x64

[ryrynz]

I have a Dolby Vision Profile 5 file which looks more accurate when I select 'convert to SDR' in MPC-VR.
Putting Windows into HDR mode didn't change the colors at all.
The TV has Dolby Vision support so I can compare directly.

[Aleksoid1978]

I have a Dolby Vision Profile 5 file which looks more accurate when I select 'convert to SDR' in MPC-VR.
Putting Windows into HDR mode didn't change the colors at all.
The TV has Dolby Vision support so I can compare directly.

There is no need to compare how a TV plays Dolby Vision and how a renderer does it as a result of transformations - this is already completely different.

Support for Dolby Vision has been added as Windows doesn't natively do this. Well, you can watch on SDR devices.

[budgy]

Just testing MPC-VR and am having some problems with trying to figure out how to get my settings correct so that the video levels follow what I am doing with madVR. After lots of testing, with the help of many suggestions (on AVS and other places) that are not madVR specific, I have my chain set up as Limited -> Full -> Limited:

madVR TV Levels (16-235) -> NVIDIA GPU Full (0-255) -> TV Limited

Can I, and if so how, do this with MPC-VR? I cannot find the equivalent output level setting. There's a setting in the Video Decoder for setting the RGB output levels, but it doesn't seem to have any effect. Is MPC-VR output Full only? The only thing that seems to stop my blacks from being completely crushed is to change my TV black level settings to Full, but this would be changing my whole chain to Full -> Full -> Full.

I only use this (OLED) TV as a HTPC display. I don't mind that the levels are restricted and it is set to limited as instructed for calibration (ColourSpace ZRO) so I don't really want to change it if possible. I do want to change from madVR though, so would prefer to switch to something like MPC-VR. Does anybody know if this is possible?

[Alexkral]

I have a Dolby Vision Profile 5 file which looks more accurate when I select 'convert to SDR' in MPC-VR.
Putting Windows into HDR mode didn't change the colors at all.
The TV has Dolby Vision support so I can compare directly.

If you also have mpv, you could try the different tone mapping algorithms to see which one produces the most similar result. You should look at the brightness and contrast, not the saturation.

[huhn]

use full range setup.

limited range stuff is a mystic a very dumb mystic.

[ashlar42]

MPC Video Renderer 0.6.9 receives a MediaSideDataDOVIMetadata structure (https://github.com/Aleksoid1978/VideoRenderer/blob/41f38aa46ab9f8d6614930985031412f683b4818/Include/IMediaSideData.h#L139) from MPC Video Decoder 1.6.9 (or LAV Video Decoder). MPC Video Renderer uses some data from this structure to render the frame.

There is no need to compare how a TV plays Dolby Vision and how a renderer does it as a result of transformations - this is already completely different.

Support for Dolby Vision has been added as Windows doesn't natively do this. Well, you can watch on SDR devices.

So does the metadata read from DoVi files get used when outputting HDR10? Or does using an HDR10 native file provide the best quality? Having the choice, I mean.

limited range stuff is a mystic a very dumb mystic.
We discussed this in the past. But I still see this as an opinion of yours, not shared by any pro calibrator I’ve read around…

I would love to see you discuss this with pros on AVS, to settle this. Why don’t you open a discussion about it, there? I know you can quote stuff, etc. it might be interesting.

[huhn]

So does the metadata read from DoVi files get used when outputting HDR10? Or does using an HDR10 native file provide the best quality? Having the choice, I mean.
depends on mastering in theory there is no difference up to 4000 nits in practice user like to say dovi is superior.

We discussed this in the past. But I still see this as an opinion of yours, not shared by any pro calibrator IÂ’ve read aroundÂ…
from colorspace zro: https://www.lightillusion.com/assets/img/multi-point-csv.png
either they don't measure black because it is not at 20 or it is lossy compressed when displayed... for a limited full limited pipe (madTPG will it has to and BTB and WTW are never calibrated anyway.) just saying.
I would love to see you discuss this with pros on AVS, to settle this. Why donÂ’t you open a discussion about it, there? I know you can quote stuff, etc. it might be interesting.
outside of PC and gaming consoles as a source stuff is different...

yes i can quote and link some facts that are more then "interesting" about this topic. this will go no where anyway.

[v0lt]

As always, users on doom9 are dissatisfied. :-|

So does the metadata read from DoVi files get used when outputting HDR10?
Only MaxMasteringLuminance and MinMasteringLuminance are calculated, other values are default. Full support for DolbyVision is not possible on a PC.
Or does using an HDR10 native file provide the best quality? Having the choice, I mean.
Whatever you like best will be the best choice for you.

[Sunspark]

I am curious to know what is the technical reason that it's not possible on a PC?

[huhn]

GPUs don't support it openly.

they can not add something they don't have an API for.
there is also the entire problem of how dumb dolby vision and there level is and how much has been leaked, revers engineered and such.

it's proprietary to milk end user as much as possible.
supposedly media foundation supports some kind of dolby vision...

[v0lt]

I am curious to know what is the technical reason that it's not possible on a PC?
To end the thread of questions, here is a starting link for you to study the issue - IDXGISwapChain4::SetHDRMetaData (https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_5/nf-dxgi1_5-idxgiswapchain4-sethdrmetadata). I did not find support for Dolby Vision displays there.
You can also read the specification of your video card.

[ashlar42]

As always, users on doom9 are dissatisfied. :-|


Only MaxMasteringLuminance and MinMasteringLuminance are calculated, other values are default. Full support for DolbyVision is not possible on a PC.

Whatever you like best will be the best choice for you.
Thanks a lot. I don't know if you were talking about me but I was simply curious to understand. I was and I am not dissatisfied with a nice product that's being shared for free.

[Sunspark]

@huhn Because I can only use mpc-vr with 10-bit hevc anime on this broadwell cpu, I have been testing out different combinations of settings to see which delivers acceptable cpu/gpu load and picture quality. My preference is for picture quality without turbine fan mode activating. I have been using the shaders a lot lately with mpc-vr. Just now I tried 16-bit floating point and it seems to have improved the appearance a little as opposed to auto 8/10 integer.

Doing a thread search, I see back in 2019 it was discussed that 16-bit fp works well with mpc-vr in dx9 video processor mode.. so now I am wondering, should I just leave it in VP, or are there further advantages to be gained by using the shaders with 16-bit fp instead of the dxva2/d3d11 video processor in 16-bit floating point? It doesn't seem to make a difference in cpu/gpu load using either.

I can't use d3d11 hevc decoding because due to the weird hybrid decoding that only broadwell does, it crashes. Only dxva2 decoding seems to work without a crash. The renderer however can operate in d3d11 mode fine if I want it to, just not the decoder. I usually have it in d3d9 mode for consistency in the chain.

[Sunspark]

I am pleasantly surprised at the results of this thing we like to do, pixel peeping. Looking at some old comments, I came across 2160p_Gradient_Split_10bit_8bit.mp4 (https://drive.google.com/file/d/0B68jIlCvW85gWFp0NVUwTFdTNFE/view?usp=sharing) where according to huhn the top half is 10-bit (likely dithered) and the bottom half is 8-bit rounded. I guess I am lucky that Intel doesn't trash the chroma in dxva2-native since it is all I can use for HEVC Main 10. I actually don't normally use dxva2 chroma/image scaling because I feel it introduces noise, but for a resource-constrained dual-core system trying to use HEVC, it seems to be ok.

1-evrcp (https://dl.dropboxusercontent.com/scl/fi/uakaf5m18jf8arx84aate/1-evrcp.png?rlkey=giv026oiye1snqcsb0g2hktnq) (dxva2-native mpc-be d3d9 decoding, flip presentation, 16-bit fp surface, michell-netravali resizer)
2-dxva2nmpcvrd3d9vp (https://dl.dropboxusercontent.com/scl/fi/ic47ds8unbjvp3i7yw57a/2-dxva2nmpcvrd3d9vp.png?rlkey=vhd3uxz8tzs67xmppjsl9xdbd) (dxva2-native mpc-be d3d9 decoding, dxva2 video processor, flip swap effect, 16-bit floating point texture format)
3-dxva2nmpcvrd3d9shaders (https://dl.dropboxusercontent.com/scl/fi/czq4pv22fjkqnk2s1ljtb/3-dxva2nmpcvrd3d9shaders.png?rlkey=vhvhha904d87dlq323e1w9shf) (dxva2-native mpc-be d3d9 decoding, mpc-vr bilinear chroma and mitchell-netravali resizer, flip swap effect, 16-bit floating point texture format)
4-madvrsoftwared3d9 (https://dl.dropboxusercontent.com/scl/fi/nt5sqkbnv7wfi0lym8dm4/4-madvrsoftwared3d9.png?rlkey=glnuubu2hbfmzaxkifhxf31kk) (software decoding, madvr d3d9 presentation with mitchell-netravali AR chroma resizer, mitchell-netravali AR LL downscaler)

On a grayscale gradient test, 3 and 4 are very similar which speaks well of mpc-vr. 1 cannot do 10-bit but that's well known. 2 has a surprisingly good showing with Intel, especially compared to huhn's AMD dxva2-native image (https://abload.de/img/amddxvanativebug4gkwu.png). His software decoding AMD image (https://abload.de/img/amddxvabug2bqkm5.png) for reference. The Intel image has slightly stronger banding and the hardware vp leans toward green but it doesn't have the chroma subpixel issue that AMD and Nvidia do.

I know everyone is using D3D11 now, but this was still fun for me and it means there is still life in this machine yet. :)

PS. With the above settings, mpc-vr dxva2 video processor 25% cpu 41% gpu, mpc-vr shaders 55% cpu, 41% gpu, madvr 90% cpu, 75% gpu. Numbers are high because this is upscaling chroma on a 4K file and downscaling the image to a lower resolution that isn't an integer multiple of 4K. A different 10-bit HEVC file of resolution 1920x1080 presented at 1920x1080 only had dithering done, so approximately 25% cpu 23% gpu for the VP and 25% cpu 20% gpu for the shaders. Madvr had 40%+ cpu and 15% gpu. This is an igpu so no separate card. HEVC decoding is partial on this cpu with the mpc decoders. The madvr number is only software decoding, no partial HW decoding due to crashes.

[Sunspark]

Not that it matters for most since I am probably the only one here on Broadwell, but I have solved the hybrid HEVC decoder crash in D3D11. It works if "Discard" is the swap effect in the renderer. "Flip" will crash. Flip will work in D3D9 mode fine.

MPC-VR lets you choose the swap effect, MadVR does not.

[huhn]

madVR let you choice the render type too.
it has FSE or WFS backbuffer or present in advance.

i do not have the information if this has anything todo with a flip discard or overlay or what ever.

[Sunspark]

@huhn The animated show Star Trek: Lower Decks has a great gradients test for banding in S01E09 0:23:25-0:23:56 (if you have a high bitrate encode from the bluray). The funeral scene has a pale powder blue sky background which displays gradient banding with mpcvr's default settings. The banding can be made to go away via changing settings.

[Sunspark]

I have a question about a presentation difference between evr-cp and mpc-vr.

Both are on the d3d9 dxva2-native decoder path, 16-bit, no resolution scaling is being performed. Yet, I can see a difference with anime. Neither are wrong or bad, just different.

I find that mpc-vr is presenting with a softer focus. The colours might be a tiny bit better, but primarily I notice the slightly softer focus. Evr-cp presents the lines with a sharper definition. Do they use a different type of dithering pattern and this is the reason? Or is it something else?

[huhn]

dxva processing is altered by the GPU driver.
if you want an accurate image just avoid it.

in my limited experience they are 100 % the same on nvidia and that's no fluke because nvdia barely changes the image and has image damaging algorithm off by default.

on AMD evp cp was altered in colors and mpcVR not so take that as it is.
AMD DXVA processing is so broken it doesn't have an off switch anymore you need the registry to disable it.

[Sunspark]

Am I correct in assuming that it's unnecessary to check "VSync" in frame synchronization for evr-cp if one is already using autochange fullscreen to match refresh rates?

I don't see any change in the red lines with the ctrl-t test with VSync checked or unchecked.

When is it best used?

[v0lt]

When is it best used?
There is no best solution. If you have problems with the smoothness of frame output, then you can try turning on the "VSync" settings. Which combination will be best for your configuration is determined by tests.

[Sunspark]

Color management checkbox for evr-cp doesn't work here. Shifts the hue to yellow whether windowed or fullscreen. Exclusive mode on or off doesn't make a difference.

[v0lt]

Color management checkbox for evr-cp doesn't work here. Shifts the hue to yellow whether windowed or fullscreen. Exclusive mode on or off doesn't make a difference.
It works. For the window it is used twice (using a shader and display profile). For a full screen once (using a shader).
I could probably fix this (turning off for the window), but users will be unhappy. This issue was discussed several times in the topic.

[Sunspark]

I do use a colour profile and have it applied system-wide (as well as a non-2.2 gamma). Are these users who would be unhappy, users that don't have colour profiles?

I did look at the search, but it wasn't clear to me what the issue is that it functions in this manner. My assumption is that the code would simply just call and check if there's a profile installed, and if so, take it into account, else proceed as it has been doing already.

[v0lt]

If a display profile is not used, MPC-BE will not be able to use Color Management.
Which display profile Color Managment uses will be visible in the EVR-CP statistics in MPC-BE 1.6.9.103.

[s0meone_new]

Hungarian translation updated:
https://easyupload.io/dsw16y

[Klaus1189]

Updated german translation (https://drive.google.com/file/d/1NwBzp70DqbsN-NeKUsrorOgUedPyb_nu/view?usp=sharing) :)

[cmhrky]

Will there be "App paths" support for ffmpeg.exe?

[v0lt]

Will there be "App paths" support for ffmpeg.exe?
Do you need it?

[cmhrky]

If it can be used for youtube-dl and yt-dlp, it might be good to support ffmpeg as well.

[wushantao]

https://files.catbox.moe/q9yzk3.7z

Update Simplified Chinese：）

[v0lt]

Thanks everyone. Translations have been updated.

"App paths" support for "ffmpeg.exe" has been added.

[cmhrky]

It would be nice to set a location for ffmpeg.exe with "App Paths" (https://forum.doom9.org/showthread.php?p=1955078#post1955078).

Thank you @v0lt. Another wish of mine has come true. 🎉

[wushantao]

https://files.catbox.moe/l7wpev.7z

Update Simplified Chinese：）

[Klaus1189]

Updated german translation (https://drive.google.com/file/d/1NwBzp70DqbsN-NeKUsrorOgUedPyb_nu/view?usp=sharing) :)

How do I enter the dialog with the new translation? I need to check if it fits.

[s0meone_new]

Hungarian translation updated:
https://easyupload.io/bpgo4h

[v0lt]

Thanks everyone. Translations have been updated.

[v0lt]

How do I enter the dialog with the new translation? I need to check if it fits.
This is for the YouTube clip saving dialog. You probably won't see the "Merging files..." line because ffmpeg.exe merges DASH streams very quickly.

[beter]

Translation Update for Traditional Chinese and Dutch:
https://www.sendspace.com/file/3jj0et

[cmhrky]

This is for the YouTube clip saving dialog. You probably won't see the "Merging files..." line because ffmpeg.exe merges DASH streams very quickly.

Where will "Merging files..." appear? I didn't see it when merging files. I tried with 1080p and a long video.

[v0lt]

@beter
Thanks. Translation updated.

@cmhrky
Thank you. Fixed.

[v0lt]

Release MPC-BE 1.6.10 (https://github.com/Aleksoid1978/MPC-BE/releases/tag/1.6.10)

MPC-BE Nightly builds:
Яндекс.Диск (https://yadi.sk/d/hlf1lfC8mKU58), Яндекс.Диск 2 (https://yadi.sk/d/AjAXDDHtHRIELg)
MEGA (https://mega.nz/folder/cQsn1TKJ#sT9sS6ywvmNqjz6B4RaK5Q), Google Drive (https://drive.google.com/drive/folders/1u84bY2n6fPAvM5n5mJvQBSDv6BKut-RY?usp=sharing), Pcloud (https://u.pcloud.link/publink/show?code=kZ2gNeVZjGcpVOgg3Rkxxln2U2itBSxW2IUy), Filen Drive (https://drive.filen.io/f/e104a83b-41f3-4bd1-8477-4b8838eb5986#qOhqvOnNY6lFLDu6ETjOtu8jT9KvbS7e), Icedrive (https://icedrive.net/s/jCSTVwvB3YXAwfVxu6x5WNziwDgj)
Night builds are provided by volunteers.

Also new and old versions can be found on VideoHelp.com (https://www.videohelp.com/software/MPC-BE).

Donate (https://mpc-be.org/forum/index.php?topic=240.0).

[wushantao]

https://files.catbox.moe/fjei23.7z

Update Simplified Chinese：）

[Klaus1189]

Updated german translation (https://drive.google.com/file/d/1NwBzp70DqbsN-NeKUsrorOgUedPyb_nu/view?usp=sharing) :)

[Klaus1189]

Reupload for wushantao
https://drive.google.com/file/d/1k7_irLbLGpvGVVbWQjtim0TiWfe6bQCI/view?usp=drivesdk

Seems like the hoster can not be viewed by devs.

[s0meone_new]

Hungarian translation updated:
https://easyupload.io/gct95s

[kryptonite]

Hi,
Thank you for the amazing work being done on MPC-BE and MPC Video renderer, especially the ability to transcode DV into HDR10 on the fly for us PC/Windows users.

Just checking to see if HDR10+ video support on MPC-BE/MPCVR is in the works, now that the NVIDIA Drivers support HDR10+, and some PC Games support it as well.
This would be very useful for those of us with Samsung displays, as there's quite a bit of HDR10+ video and game content available now.
https://www.youtube.com/watch?v=UwQ5uJ-Yjyc

Also with respect to DV->HDR, I was also wondering if it would be possible to extend this to transcode DV into HDR10+ in the future, i.e. 'DV dynamic metadata' into 'HDR10+ dynamic metadata'.
Perhaps I'm wishing for too much and this is not doable, I just wanted a better understanding of the possibility, limitations, etc

Cheers, and appreciate all your hard work.

[Aleksoid1978]

Hi,
Thank you for the amazing work being done on MPC-BE and MPC Video renderer, especially the ability to transcode DV into HDR10 on the fly for us PC/Windows users.

Just checking to see if HDR10+ video support on MPC-BE/MPCVR is in the works, now that the NVIDIA Drivers support HDR10+, and some PC Games support it as well.
This would be very useful for those of us with Samsung displays, as there's quite a bit of HDR10+ video and game content available now.
https://www.youtube.com/watch?v=UwQ5uJ-Yjyc

Also with respect to DV->HDR, I was also wondering if it would be possible to extend this to transcode DV into HDR10+ in the future, i.e. 'DV dynamic metadata' into 'HDR10+ dynamic metadata'.
Perhaps I'm wishing for too much and this is not doable, I just wanted a better understanding of the possibility, limitations, etc

Cheers, and appreciate all your hard work.

Windows don't have API for HDR10+.

[wushantao]

Reupload for wushantao
https://drive.google.com/file/d/1k7_irLbLGpvGVVbWQjtim0TiWfe6bQCI/view?usp=drivesdk

Seems like the hoster can not be viewed by devs.

THX!

next time i‘ll try other host

[Ceppo]

Is there an example C++ plugin for plugin development?