MadVR in use with LG OLED Thread

[SamuriHL]

OTOH, new job and my birthday is in a few weeks. I've made a command decision I didn't think I'd make. I'm rebuilding the HTPC with my 2070 using a Ryzen 5900x. God help me.

[quietvoid]

Originally Posted by SamuriHL

That was a short lived attempt at madvr on my laptop. I've never gotten it to work right when outputting to the C8. This time was no exception. I can't get it to trigger HDR. I switch back to JRVR and it works perfectly fine. Whatever. I'm over trying to deal with that.

Does your laptop run an AMD/Nvidia GPU?
I read madVR only supports the driver APIs, instead of using Windows' APIs (DirectX/Direct3D, not sure).

Though I don't know what JRVR uses for HDR passthrough, it could either be Vulkan or D3D11. Both of which should have generic APIs.

[SamuriHL]

Originally Posted by quietvoid

Does your laptop run an AMD/Nvidia GPU?
I read madVR only supports the driver APIs, instead of using Windows' APIs (DirectX/Direct3D, not sure).

Though I don't know what JRVR uses for HDR passthrough, it could either be Vulkan or D3D11. Both of which should have generic APIs.

It's an alienware area-51m with rtx 2080, so, yea it's using the nVidia GPU. No idea why madvr didn't want to play nice. I don't care. I'm going to rebuild the HTPC after all this time and give myself some more options. Getting the new job this year allows me to splurge a little bit on some upgrades. So...screw it.

[nevcairiel]

Originally Posted by quietvoid

Though I don't know what JRVR uses for HDR passthrough, it could either be Vulkan or D3D11. Both of which should have generic APIs.

It favors D3D11 on Windows due to integration with hardware decoding and D3D11 video processing for deinterlacing. Technically both of those could still be used and then go Vulkan, but then I would first have to implement resource sharing between D3D11 and Vulkan, so more extra steps for probably no major gain.

[SamuriHL]

No need to change it. It works very well as is.

Sent from my SM-G998U1 using Tapatalk

[SamuriHL]

For the love of all things holy, nVidia. So it turns out my HTPC issues were again caused by the 2nd 2070 card they RMA'd to me failing in the EXACT SAME WAY as the previous 2. To their credit they are sending me yet another one once I RMA this one back. I really hate the people that have driven up the prices of new RTX cards as I would have simply upgraded at this point. So I can fix my old HTPC (the ram is indeed still defective and won't post above 2133 which is bad....oh Corsair! LOL) and have that for my bedroom when I upgrade to a new display later this year. Assuming, you guessed it, I can find it a video card. LOL

[SamuriHL]

My patience finally ran out. Given my b-day is this weekend and I wanted a newly rebuilt HTPC (plug gaming), and given that the 2070 is dead for the 3rd time now and I just sent it back today, I opted to go the more....exotic approach to acquiring a new video card. Short version is I'll have enough parts left over to rebuild my old machine for the 2070 for my bedroom and I will have a brand new ASUS 3080 by Thursday. I will have a brand new 5900x, pc3600 ddr4 32 gigs, 980 pro 1tb nvme pci 4, water cooled machine with a 3080 TUF card in it. Happy birthday to me. LOL

[huhn]

there is an Samsung OEM disc which is the same as the samsung pro 980 just cheaper (even "faster" on paper).
the PM9A1
do your self a favor and get an i5-i7 12000 series clearly better for gaming. yes times can change pretty fast.
the water "cooling" is beyond me but do what you like.

welcome back until your UPS goes on a killing spree again.

[SamuriHL]

I got the 980 on sale so I did well with that.

The new machine I just bought has an 11xxx Intel chip. If I decide to stick with Intel I could use that but I'm pretty sure the 5900x will be just fine. The 11xxx will upgrade the old machine for the bedroom.

As for the ups no doubt on that. It's been replaced for a few months now so I should be good.

Sent from my SM-G998U1 using Tapatalk

[SamuriHL]

It's so nice to be back up and running. Got the 3080 yesterday. I tweaked madvr a bit and watched jurassic world on it. Very nice. I have absolutely no idea what settings are going to be best for oled right now. But I have a long weekend coming up so I'll play around.

Sent from my SM-G998U1 using Tapatalk

[pragmatick]

I have a new LG C1. I configured madVr to pass through HDR content and enabled some display modes, e.g. 2160p23. Playing a 4K video sets the resolution to 2160p with 23hz. The nvidia control panel says as much, with RGB full output at 12 bit. The madvr OSD says "NV HDR, 12 bit, RGB, full" and "D3D11 windowed (8 bit)". But the colors are all wrong and the image is way too dim.

If I change the color output depth in the nvidia control panel and reopen the file then the colors are correct. It doesn't matter if I change it to 10 bit or 12 bit, in both cases the colors are correct and madvr will show the appropriate value in the OSD. When I close the media player (and the desktop resolution is restored to 2160p120) and reopen the file (and the resolution is changed again to 2160p23) the colors are wrong again and I can fix it by changing the output bit.

Does anybody have any ideas what's going on and how I can make it work instantly? I mean, the workaround kinda fixes it, but it's really a hassle and I'd like it to work from the start... Thanks.

[chros]

Which OS, GPU and driver?

[quietvoid]

There seems to be a bug with madTPG + HDR and the latest beta(s). It's sending something close to 2.2 instead of PQ.
Maybe intentional? No idea.

If I had the TV in 2.2 mode, the measurements were linear.

[chros]

Originally Posted by quietvoid

There seems to be a bug with madTPG + HDR and the latest beta(s). It's sending something close to 2.2 instead of PQ.
Maybe intentional? No idea.

If I had the TV in 2.2 mode, the measurements were linear.

Hm, report it to madhsi. Do you know which version it started with?

[quietvoid]

I don't, I just reverted back to the latest non-beta version.

[chros]

Originally Posted by quietvoid

I don't, I just reverted back to the latest non-beta version.

That's what I did as well when I did calibration. I reported your bug to him.

[ashlar42]

Say I don't particularly care for HDR, I have a 77C1 calibrated to 107 nits in SDR and would like to tonemap 4K HDR content in order to view it in SDR, is there a suggested set of settings for pixel shader tonemapping I could use? The panel to configure HDR is such a smorgasbord of options I wouldn't know where to begin.

[huhn]

you start by typing peak nits 107 in but else no one really agrees on everything.

[ashlar42]

Originally Posted by huhn

you start by typing peak nits 107 in but else no one really agrees on everything.

Yup, that's what I did. Results were most definitely acceptable. I hoped there was some sort of "middle ground" consensus on what good settings for the rest of the options would be.

I mean, I doubt that Envy does not have sensible defaults to offer. Are they opaque to end users?

(It's not that I don't think HDR makes a difference, it definitely does. It's just that it's a difference I often don't particularly like. Typical interior scenes with blinding windows in the background are an example, neon lights equally blinding in nighttime settings are another)

[SamuriHL]

Go to the avs thread and look for neoxp and javs settings. Right now there's no concensus on "best" settings because they're currently trying to figure out what luminance methods are providing the best quality at various nit levels and options. With your display, however you should set madvr to output rec.2020 or dci-p3. It really depends on how you've calibrated your display. But using one of their settings as a base will be a good starting point. Other than that you'll have to massage the options to find what you like. Yes envy offers a curated set of settings but we aren't privy to what they are.

Sent from my SM-G998U1 using Tapatalk