MadVR in use with LG OLED Thread

[SamuriHL]

I agree. I want all the info before I drop that kind of coin on a new display. I've been holding off until things improved but I'm at the point now where the c8 needs to be replaced and moved. So I'm hoping the g2 hits it out of the park this year.

Sent from my SM-G998U1 using Tapatalk

[chros]

Originally Posted by Hammy

@chros Great work! ...

And here's a temporary solution for HLG2HDR10, until madshi finally adds it into madvr.
Not sure whether it's perfect, it results in way oversaturated image using DTM, but strangly not with passthrough. Maybe another file tag is needed for the source colorspace?

[Kuler087]

Originally Posted by chros

And here's a temporary solution for HLG2HDR10, until madshi finally adds it into madvr.
Not sure whether it's perfect, it results in way oversaturated image using DTM, but strangly not with passthrough. Maybe another file tag is needed for the source colorspace?

Hi thank you and sorry for my ignorance but how do you use the code in madvr?
What tag? transfer=hdr and matrix=2020 ?

I would like to compare it with my method which involves re-encoding.
https://slow.pics/c/5nkGDpBZ ----> this is frame 4304 of The Green Planet S01E01 2160p HLG

[chros]

Originally Posted by Kuler087

... how do you use the code in madvr?
What tag? transfer=hdr and matrix=2020 ?

- as madshi suggested: rename to filename to include "hdr=on" in it
- - not sure about the matrix tags, we have to play with it
- save the code as a text file e.g. "convert_hlg_to_pq.hlsl" into "MPC-BE\Shaders" directory
- - then right-click during playback -> Shaders -> select it at Pre-Resize shader -> add and enable it

Also, check which profile is selected in madvr (if you have multiple ones), I think there's a bug with profile selection when file tags are used, so switch it manually if it's needed.

Originally Posted by Kuler087

I would like to compare it with my method which involves re-encoding.
https://slow.pics/c/5nkGDpBZ ----> this is frame 4304 of The Green Planet S01E01 2160p HLG

How do you reencode it?

Also, you can check mpcVR how it looks like.
Lemme know your findings ...

[Kuler087]

Originally Posted by chros

- as madshi suggested: rename to filename to include "hdr=on" in it
- - not sure about the matrix tags, we have to play with it
- save the code as a text file e.g. "convert_hlg_to_pq.hlsl" into "MPC-BE\Shaders" directory
- - then right-click during playback -> Shaders -> select it at Pre-Resize shader -> add and enable it

Also, check which profile is selected in madvr (if you have multiple ones), I think there's a bug with profile selection when file tags are used, so switch it manually if it's needed.

Thank you!

I don't have an HDR monitor at work to test passthrough but as you said, HDR to SDR clearly is not working: oversaturated (no color difference with the shader or not ? I might not be using it right?). I'll take a look mpcVR.

resolve / madvr / HLG / mpcVR


mpcVr looks too bright to my taste but if I try to match brightness in madvr (150nits static):



Resolve Dolby vision SDR tonemapping from HLG-HDR10:

Originally Posted by chros

How do you reencode it?

Also, you can check mpcVR how it looks like.
Lemme know your findings ...

With Davinci Resolve HLG in, HDR10 out. it's quite easy to do but time-consuming. But I can then generate DV.

[chros]

Originally Posted by Kuler087

With Davinci Resolve HLG in, HDR10 out. it's quite easy to do but time-consuming.

I see, cheers.

Originally Posted by Kuler087

I don't have an HDR monitor at work to test passthrough

Well, that's what we want to use/test

Originally Posted by Kuler087

but as you said, HDR to SDR clearly is not working: oversaturated (no color difference with the shader or not ? I might not be using it right?).

Thanks for the images, yes, I think it's oversaturated a bit: why I think it is because with normal HDR10 content I have to add +5 saturation in madvr (I use the synthetic 3dlut with hdr output), while with this I have to remove it

It should be a clear color difference on-the-fly when you enable the shader with hdr output: without the shader it crushes black and blows out highlights.

I tried the matrix and source_primaries as well, but they don't do anything good.
I also tried to decrease saturation (in madvr, e.g. -5), but fire starts to become pink, so it's a no go.
Maye this saturate line is the issue? They added a comment here why they use it with d3d11 shaders (but this use different math):
"use saturate(), because pow() can not take negative values"
So I'll try it out with pow() instead ...

Let's use madmeasure v145 for testing, that looks to be a good build ...

EDIT: I tried "pow(color, 1.0)" instead of saturation but the image is the same, so that's not the issue.
Maybe this one is?

[quietvoid]

I don't really care about madVR anymore but I was curious about the mercury curve.
Overall it's pretty similar to my last custom curve, with a slight emphasis on highlight detail and contrast (therefore slightly dimmer midtones).

I'd say it's pretty much equivalent at punch 20, with defaults (HSTM limit) and HSTM Log Very Low.
I think most of the early feedback was around 12 for lower nits, which still looks very close to 20 at 870 nits.

[Magik Mark]

Quietvoid

Did you delete your madvr HDR Tone mapping settings?

[Magik Mark]

Chros

Do you still play around with new beta of madvr?

[chros]

Originally Posted by quietvoid

mercury curve.
Overall it's pretty similar to my last custom curve, with a slight emphasis on highlight detail and contrast (therefore slightly dimmer midtones).
I'd say it's pretty much equivalent at punch 20, with defaults (HSTM limit) and HSTM Log Very Low.
I think most of the early feedback was around 12 for lower nits, which still looks very close to 20 at 870 nits.

Thanks. What does the punch value does actually? Is it for the steepness of the curve? If so, higher value equals to higher steepness?

I don't like HSTM with high display peak and hdr passthrough, so it's disabled here.

Originally Posted by quietvoid

I don't really care about madVR

Why is that, out of curiousity?

[quietvoid]

Originally Posted by chros

Thanks. What does the punch value does actually? Is it for the steepness of the curve? If so, higher value equals to higher steepness?

I don't know what base algo is behind the curve, it may or may not be the same as custom curves (which were limited to 2-line and bt.2390).

Higher punch usually means brighter and more contrast.
With mercury nowadays there isn't any highlight detail loss even at punch 20 for our target nits.

Originally Posted by chros

I don't like HSTM with high display peak and hdr passthrough, so it's disabled here.

Have you tried the HSTM limit? It seems to solve the problem where HSTM would blow out highlights

Originally Posted by chros

Why is that, out of curiousity?

Mostly it's not convenient for me to use a PC for playback. Plus my TV's HDMI cable always falls off my GPU

Also, HDR10 is pretty much unwatchable for me either because of bad factory PQ tracking, or the 1D LUT issues I mentioned before.

Originally Posted by Magik Mark

Quietvoid

Did you delete your madvr HDR Tone mapping settings?

No I haven't deleted anything.

[Magik Mark]

Quietvoid

Where is it located? Can't seem to find it

[quietvoid]

I don't know, it's outdated anyways.

[quietvoid]

@chros Have you tried this? https://www.avsforum.com/threads/201...#post-61381379

[Magik Mark]

quietvoid,

If you have the time to play around with the new madvr beta, pls do so. Tried it using most of your last setting and it looks promising. The setting being shared in the avs forum are mostly for front projectors. We need something that is for OLED

[quietvoid]

Originally Posted by Magik Mark

quietvoid,

If you have the time to play around with the new madvr beta, pls do so. Tried it using most of your last setting and it looks promising. The setting being shared in the avs forum are mostly for front projectors. We need something that is for OLED

I have no interest in using madVR so I won't be testing new settings. Sorry.

[SamuriHL]

I may poke around with it over the next few days. I just ordered a longer HDMI cable so I can hook my laptop up to my VRROOM for testing. Ultimately I've not been using a PC solution for quite a few months now and honestly haven't missed it much.

[VBB]

Seems to be a trend

(at least among those of us whose video cards died an untimely death)

[SamuriHL]

Yea I'm honestly more interested in saving up for a new G2 (potentially) than I am a new HTPC. There are differences in using madvr dtm, there's no question. But I'd argue, as many others have, that if you're watching mostly 1000 nit content on a 870 nit screen, the benefit to dtm is not going to be super huge. Hence, I don't really miss it much.

[chros]

DoVi perfect black with 2018 models, 2nd round