Media Player Classic - BE Win32/x64

[v0lt]

Support for Super Resolution appeared after the implementation in Chromium. The file swap_chain_presenter.cc contains the functions ToggleIntelVpSuperResolution and ToggleNvidiaVpSuperResolution. There is no solution for AMD.

[butterw2]

For Nvidia Video SuperResolution, there has been an Nvidia blog post and very mixed user reviews. For Intel, there was just some press coverage of the chromium commit.

[butterw2]

Using mpc-be with mpc-vr dx11, I've noticed that when I open the shader combiner interface "Shaders > Select Shaders..." the combo-box always starts on dx9. However, the user would need to use dx11 shaders in this case. Would it be possible to modify so that the selector is set to the display mode currently in use (ie dx11) ?

[v0lt]

Originally Posted by butterw2

Would it be possible to modify so that the selector is set to the display mode currently in use (ie dx11) ?

The problem here is that MPC VR can be inactive. And I don't want to look for renderer settings in the registry.

In commit 9643c21 I made it so that the choice of DX9/DX11 depends on the renderer selected in the settings and the Windows version. This will close the issue on typical configurations.

[hajj_3]

dav1d v1.2.1 is out

[ashlar42]

Is there a way to play HLG files in HDR10 or HLG passthrough? Tried a couple of HLG files that Kodi handles well and they played back in SDR.

[Aleksoid1978]

Originally Posted by ashlar42

Is there a way to play HLG files in HDR10 or HLG passthrough? Tried a couple of HLG files that Kodi handles well and they played back in SDR.

Yes - use MPC VR.

[ashlar42]

Originally Posted by Aleksoid1978

Yes - use MPC VR.

Right. I had tried but I made a dumb mistake... it works. Thanks a lot.

[ashlar42]

Hmmm... it works with some files and not with other files. I uploaded here two very small videos, one working, the other not working. Meaning one activates HDR and the other doesn't. Both work fine in Kodi 20.1.

https://easyupload.io/zai05t

Let me know if any other info is needed to help solving this.

[huhn]

one file is not HLG it is BT 2020 (what ever that means for transfer).

https://en.wikipedia.org/wiki/Rec._2...haracteristics

do not forget wikipedia is not reliable for video specs.

[ashlar42]

Originally Posted by huhn

one file is not HLG it is BT 2020 (what ever that means for transfer).

https://en.wikipedia.org/wiki/Rec._2...haracteristics

do not forget wikipedia is not reliable for video specs.

Mediainfo for "non working" file states:

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : BT.2020 (10-bit)
transfer_characteristics_Original : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

Mediainfo for "working" file states:

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : HLG
transfer_characteristics_Original : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

Now, I have zero knowledge about the implications but the "non working" file is displayed in HDR through Kodi and it's quite clear that HDR picture information is there.

So, maybe the "transfer_characteristics_Original" value is the correct one, I don't know.

One extra question, on MPC VR:

I don't see where to set range output. I need limited range, that's how I have calibrated my display. But MPC VR is outputting full range and I don't see where I could change that.

In madVR I have set "The display expects the following RGB output levels:" to TV levels (16-235) and colors are correct.

[huhn]

i get this for not working:
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : BT.2020 (10-bit)
transfer_characteristics_Origi : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

and this is not HLG the mpcVR is also seeing this as none linear bt 2020 (pretty much means ~gamma).

mpcVR doesn't have a range option(and i support this).
you can still do this using shaders.
should be the first one under shader make sure you match the DX version.

[ashlar42]

Originally Posted by huhn

i get this for not working:
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : BT.2020 (10-bit)
transfer_characteristics_Origi : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

and this is not HLG the mpcVR is also seeing this as none linear bt 2020 (pretty much means ~gamma).

As stated, I don't understand what all this means. I'm simply reporting that in Kodi I get correct HDR output for the non working file. Now, it might be an incorrect tagging/encoding/whatever. But Kodi makes it work just the same. If there are cons to that approach I don't know. Which is why I prepared the files, etc. Hoping to help in making MPC-BE work better (if it makes sense).

mpcVR doesn't have a range option(and i support this).
you can still do this using shaders.
should be the first one under shader make sure you match the DX version.

Yeah, I see there's a bit of a "religion war" on the subject. If one calibrates their TV correctly, limited range is the way to go but I absolutely don't want to go into that, since I got the impression it's already been debated to death. If you want to explain in a PM what it is all about, I'd appreciate it. But I don't wanna clutter the discussion here. :-)

If the shader approach is correct, I'll use that (I discovered it after writing the previous message).

[huhn]

Originally Posted by ashlar42

As stated, I don't understand what all this means. I'm simply reporting that in Kodi I get correct HDR output for the non working file. Now, it might be an incorrect tagging/encoding/whatever. But Kodi makes it work just the same. If there are cons to that approach I don't know. Which is why I prepared the files, etc. Hoping to help in making MPC-BE work better (if it makes sense).

i can not tell you if transfer bt 2020 is brighter than 120 nit or if kodi just supports SDR -> HDR conversation or if the wiki is correct with this is watch on bt 1886 calibrated devices (gamma 2.4 120 nits).
under the current information on the wiki it is plain SDR.

Yeah, I see there's a bit of a "religion war" on the subject. If one calibrates their TV correctly, limited range is the way to go but I absolutely don't want to go into that, since I got the impression it's already been debated to death. If you want to explain in a PM what it is all about, I'd appreciate it. But I don't wanna clutter the discussion here. :-)

there are spec and they are very easy to follow especially with a meter and a spec like PQ.

If the shader approach is correct, I'll use that (I discovered it after writing the previous message).

should be but i will not try it... because limited range on a video renderer on the desktop side is just dumb maybe with a black hole TV this changes.

[ashlar42]

Originally Posted by ashlar42

Mediainfo for "non working" file states:

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : BT.2020 (10-bit)
transfer_characteristics_Original : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

Mediainfo for "working" file states:

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : HLG
transfer_characteristics_Original : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant

Using mkvtoolnix I tested remuxing the "non working" files, changing the "Transfer Characteristics"value in the header from 14 to 18. That makes it HLG, according to Mediainfo. And it appears to be working just fine (visually, that is).

Which leads me to believe the problem was probably just in the muxing process for whomever encoded those files.

[Starks]

Are there any oneVPL implementations on Windows?