Media Player Classic - BE Win32/x64

[Siso]

No. This is a feature of the built-in EVR-CP.

Can you do it for mpc video renderer too?

[v0lt]

Can you do it for mpc video renderer too?
No. I do not get the point of it.

Enabling Color Management makes Direct3D 9 exclusive full screen color as for a window without this option. Essentially, it applies the current color profile of the display. I think that this option does not work correctly for windowed mode (the display profile is applied twice).

The main mode of MPC Video Renderer is Direct3D 11. The colors of the video in the window and the Direct3D 11 exclusive full screen are the same for me. Therefore, this feature will not be implemented.

[Siso]

No. I do not get the point of it.

Enabling Color Management makes Direct3D 9 exclusive full screen color as for a window without this option. Essentially, it applies the current color profile of the display. I think that this option does not work correctly for windowed mode (the display profile is applied twice).

The main mode of MPC Video Renderer is Direct3D 11. The colors of the video in the window and the Direct3D 11 exclusive full screen are the same for me. Therefore, this feature will not be implemented.

Of course it won't be implemened. By the way how much are the default nits for hdr to sdr convertion?

[Sunspark]

@v0lt Out of curiosity, how come you never implemented D3D9 Overlay mode as an option? I know you aren't going to, just curious because it seems like it bypasses a lot of stuff.

[v0lt]

By the way how much are the default nits for hdr to sdr convertion?
Look in ps_convert_pq_to_sdr.hlsl (https://github.com/Aleksoid1978/VideoRenderer/blob/master/Shaders/d3d11/ps_convert_pq_to_sdr.hlsl).

@v0lt Out of curiosity, how come you never implemented D3D9 Overlay mode as an option? I know you aren't going to, just curious because it seems like it bypasses a lot of stuff.
Because I'm not interested in implementing all possible options, simply because someone wanted it.

We have implemented D3DSWAPEFFECT_DISCARD because it is simple and has already been used in EVR-CP. We have implemented D3DSWAPEFFECT_FLIPEX because it may be the most efficient and it was also used in EVR-CP. I don't know anything good about D3DSWAPEFFECT_OVERLAY and haven't seen any implementations.

PS: Let me remind you that Direct3D 9 and Windows 7 are outdated.

[Sunspark]

You have seen one implementation, madvr has overlay as one of the options. I use it with Windows 10. I feel that given what MS has done to damage fullscreen exclusive mode, that overlay bypasses it.

"enable windowed overlay (Windows 7 and newer): [Disabled] Only available on Nvidia and Intel GPUs. Uses a low level overlay method which bypasses the GPU LUT (monitor profile) so madVR emulates it when using this option, this is done in 16-bit so madVR can provide better quality than the GPU. Overlay also bypasses the OS to a large extent; screen-shots are not possible. D3D9 Only. Incompatible with 'fullscreen exclusive mode'."

For mpcvr I use d3d9 with flip and exclusive fullscreen on this older intel gpu, but when I tested windows on the steam deck which uses amd, I think d3d11 worked and d3d9 didn't.. no point using windows with that system though, no hardware acceleration in the drivers.

[huhn]

overlay is a total dead end it is disabled in all current AMD and nvidia drivers.

was it the best rendering mode yes but just let it be.

[butterw2]

Would it be of interest to add local file support for the youtube url?timestamp format in mpc-be ?

ex: CTRL+O > C:\Vids\island.mp4?t=27 would open and play the file starting at 27seconds.
or maybe C:\Vids\island.mp4?t=00:00:07 which would be pretty close to what is currently available in the favorites.mpc_lst file.

[kirakami]

Microsoft has broken something in the d3d11 and dxva hardware acceleration so every time you play a video in MPC-BE, colors become washed-out. Same thing happens when using Chrome browser, colors become washed-out whenever a video is played on Youtube, but in case of Chrome, you can fix it by selecting OpenGL or D3D11on12 in chrome://flags/#use-angle (OpenGL better than D3D11on12 as it lets you keep hardware acceleration on in chrome). This is why i wanted option to choose Vulkan in MPC Video Renderer, OpenGL option would be fine too as it might fix the washed-out color issue in MPC-BE. Currently switched to using MPV as it doesn't have washed-out color issue.

[Klaus1189]

Can you upload a small sample file and what GPU and what driver do you use?

[Aleksoid1978]

Microsoft has broken something in the d3d11 and dxva hardware acceleration so every time you play a video in MPC-BE, colors become washed-out. Same thing happens when using Chrome browser, colors become washed-out whenever a video is played on Youtube, but in case of Chrome, you can fix it by selecting OpenGL or D3D11on12 in chrome://flags/#use-angle (OpenGL better than D3D11on12 as it lets you keep hardware acceleration on in chrome). This is why i wanted option to choose Vulkan in MPC Video Renderer, OpenGL option would be fine too as it might fix the washed-out color issue in MPC-BE. Currently switched to using MPV as it doesn't have washed-out color issue.

This is 100% not Microsoft, but a driver for a video card or some settings in it. Otherwise, everyone would have the same effect.

There will be no addition of Vulkan or OpenGL.

[kirakami]

It seems it is Nvidia driver issue after all, from Nvidia's side. I went to Nvidia Control Panel, in Change Resolution and changed setting to Use Nvidia Color settings instead of default color settings, and then set Output dynamic range from Limited to Full. Did same in Adjust video color settings. This mostly fixed the issue but not entirely. Now the colors don't appear washed-out but brightness still slightly changes. Almost not noticeable now though, whereas before both washed-out color and brightness change was annoyingly noticeable.

[Klaus1189]

Do you use a monitor or a TV? Limited range vs. Full range is mandatory to be set correctly.

[kirakami]

It is monitor.

[Sunspark]

I know what you're talking about, that happened on the Deck when I tried Windows on it. I blamed the broken unsupported AMD drivers because some combinations of settings in the video player renderers worked to get rid of the washed out colours. Those drivers I mentioned have no control panel with settings I can change or hardware acceleration for that matter.

I would have to re-attach the drive to see what settings I chose, but for now I would suggest you try using exclusive mode and swap effect flip in the renderer.

[v0lt]

I don't understand what "colors become washed-out" means.

About the levels. Advising to set the full level for the display is usually a good thing. But users often force the full level in the video settings, this has a bad effect on the correct operation of the DXVA2 VP (and possibly D3D11 VP).

[huhn]

amd has been broken for like 5 years now where most driver give you wrong ranges...

this happens with mpcVR too.
nvidia 4060 536.40
d3d9 and d3d11 processor both produce the correct ranges.
luckily you can just disable the video processor in this player and workaround these issues.

[Sunspark]

The washed-out colours, what that means is basically the same thing as the 0-255/16-235 issue.

I plugged in the drive and did some testing and identified the trigger (on the system I observed it). It's the "Use D3D11 decoder" checkbox for MPC's internal decoder. If the box is checked, no issue with any of the MPC video renderer's settings. If you uncheck that decoder checkbox, then it will break on this AMD driver and you will get the washed out levels where black is displayed as grey.

Issue doesn't happen with LAV decoder on the AMD because no matter what is chosen in the drop-down, it will go to software decoding mode because it can tell the driver has no hardware support at all (this is the Steam Deck's unsupported Windows driver) so MPC-VR displays the correct video levels.

This decoder issue doesn't happen on my other machine using Intel iGPU. It will play fine with the box unchecked.

My advice to those using the internal MPC video decoder experiencing this washed-out problem, check and see if "Use D3D11 decoder" is checked or not.

Edit: Ok this is weird, I was reverting the settings back to the way they were after experimenting with LAV, and now it's not doing it anymore even with D3D9 decoding. I suppose I would have to reboot the system to see if it comes back. The issue is a mix of both the video driver and whatever fail mode paths the decoder takes.

[thrawnrulz68]

Is anyone else able to get the option to "Show milliseconds" to be enabled permanently? This option is turned off whenever I open the player.

[v0lt]

Is anyone else able to get the option to "Show milliseconds" to be enabled permanently?
Anyone can't. Enabling the display of milliseconds is not saved anywhere.

[SeeMoreDigital]

I play my audio files using a cue sheet file to access the individual tracks.

Is there a way to configure the player to permanently display the track name that's playing?

[v0lt]

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

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).

[Scoty]

When use LAV Video Decoder and use DXVA2 (copy-back) AV1 is selected but when select Nvidia CUVID AV1 is not aviable. I have a RTX 4070 Ti and this can use AV1. Is there a way to use newer Nvidia CUVID with AV1 Support? Where can I get this FLVSplitter?

[v0lt]

When use LAV Video Decoder and use DXVA2 (copy-back) AV1 is selected but when select Nvidia CUVID AV1 is not aviable. I have a RTX 4070 Ti and this can use AV1. Is there a way to use newer Nvidia CUVID with AV1 Support?
There is no LAV Filters support here.

[Scoty]

There is no LAV Filters support here.

It's also about MPC and how to best use your Hardware.

[v0lt]

@Scoty
We do not support the legacy Nvidia CUVID and do not plan to support it.

I think developer LAV Filters doesn't plan to improve Nvidia CUVID either and he marked it "old" because Nvidia doesn't support CUVID for a long time (there can't be AV1).


We recommend the default settings in the built-in video decoder. In this case, the D3D11 decoder will be used whenever possible (for MPC VR or madVR). If this is not possible, then an attempt will be made to use the DXVA2 decoder. If this is not possible, then connect the software decoder.
This solution is the most optimal in terms of performance and compatibility.

[huhn]

you may should rethink the default for madVR it can't deint with d3d11 native it will just weave.
while dxva2 native will degrade the image slightly you can not win here...

[Scoty]

@Scoty
We do not support the legacy Nvidia CUVID and do not plan to support it.

I think developer LAV Filters doesn't plan to improve Nvidia CUVID either and he marked it "old" because Nvidia doesn't support CUVID for a long time (there can't be AV1).


We recommend the default settings in the built-in video decoder. In this case, the D3D11 decoder will be used whenever possible (for MPC VR or madVR). If this is not possible, then an attempt will be made to use the DXVA2 decoder. If this is not possible, then connect the software decoder.
This solution is the most optimal in terms of performance and compatibility.

Ok thx. I use d3d11 (standard setting) with DXVA2 (copy-back).

[Sunspark]

@Scoty If you're talking about the LAV decoder, you should look at the filters while a video is playing.. if it says avcodec, you're in software decoding mode despite the dropdown selection so be careful.

[Siso]

What gamma is used when watching bt.709 content in mpc video renderer? 2.4 gamma or no gamma at all?

[SirMaster]

What gamma is used when watching bt.709 content? 2.4 gamma or no gamma at all?

Technically, BT.1886 gamma which is actually 2.4 gamma on a display with perfect black (oled).

[Siso]

Technically, BT.1886 gamma which is actually 2.4 gamma on a display with perfect black (oled).

Nah, I know how BT.1886 looks on a lcd display. I guess it is some other gamma.

[huhn]

you can only calibrate a device to bt 1886 a video render can not do that blindly and if a device is calibrated to bt 1886 it will automatically use it.

it is doing unmodified as all renderer should.

only for tonemapping gamma matter what so ever outside the device gamma.

[Siso]

you can only calibrate a device to bt 1886 a video render can not do that blindly and if a device is calibrated to bt 1886 it will automatically use it.

it is doing unmodified as all renderer should.

only for tonemapping gamma matter what so ever outside the device gamma.

I don't think it's a good idea to watch unmodified gamma, in a dark room.

[huhn]

than change the gamma on your device problem solved.

[Siso]

than change the gamma on your device problem solved.

Come on huhn, even EVR-CP has gamma options, not to mention madvr.

[huhn]

EVR-CP assumes 2.2 and you are back to the same point at the start so you cna only make it worse for a dark room if you follow normal gamma you are supposed to be using...

with madVR you have a target gamma and a device gamma so it at least makes sense when you have calibrated the device properly.

because asking for the gamma and talking about "unmodified gamma is not a good idea in dark room" is none sense.

if you just want to randomly change gamma here you go: https://github.com/VoidXH/Cinema-Shader-Pack/blob/master/Shaders/Gamma%20Correction.hlsl
you can actually do more than madVR. and no i didn't test it.

defining a device gamma for tone mapping would be useful or peak nits but that's about it.

[Siso]

This gamma correction shader doesn't work. Tried it last night.

[v0lt]

This gamma correction shader doesn't work. Tried it last night.
I do not confirm. Shader works for DX9 mode.

[huhn]

in the end it is just very simple math.

unmodified turned to linear using device gamma and then linear to wanted gamma. and real programmer may find a way to do that directly not a hoax like me.

so something like this:
dispalygamma = 2.2
wantedgamma =1/ 2.4
var =power(var, displaygamma);
var =power(var, wantedgamma);

[Siso]

I do not confirm. Shader works for DX9 mode.

It doesn't work in mpc-hc.

[SirMaster]

I thought you meant what should the gamma be used when watching BT.709.

[v0lt]

It doesn't work in mpc-hc.
I do not confirm. Shader works for DX9 mode in MPC-HC. :p

PS: EVR-CP only works in DX9 mode. The folders for DX9 and DX11 shaders are different.

[Siso]

I do not confirm. Shader works for DX9 mode in MPC-HC. :p

PS: EVR-CP only works in DX9 mode. The folders for DX9 and DX11 shaders are different.

I put it in the shaders folder. Not dx11 shaders folder. And it says "failed to set post-resize shaders". I've managed to get it working.

[Mercury_22]

@ Alex

After commit 67ccc57 mpc-be_setup.iss won't compile (I think you need to change COPYING.txt → LICENSE.txt in build.bat & mpc-be_setup.iss too )

[Aleksoid1978]

@ Alex

After commit 67ccc57 mpc-be_setup.iss won't compile (I think you need to change COPYING.txt → LICENSE.txt in build.bat & mpc-be_setup.iss too )

Thanks :)

[ashlar42]

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


Added export of Dolby Vision metadata via the IMediaSideData interface.

Does this have any effect on DV files playback?

[v0lt]

Does this have any effect on DV files playback?
Yes. https://forum.doom9.org/showthread.php?p=1990500#post1990500

[ashlar42]

Yes. https://forum.doom9.org/showthread.php?p=1990500#post1990500
I had seen your post but thought that mpc-be release was in addition to that. Instead it’s probably support for that feature. Thanks for clarifying.

Just to be sure, does it in any way make use of DV extra metadata? I suppose not but it’s worth asking… Thanks again!

[v0lt]

Just to be sure, does it in any way make use of DV extra metadata?
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.