madVR - high quality video renderer (GPU assisted)

[madshi]

@SamuriHL, just to get a speed impression, with your 1060, I suppose you can do the following with ease:

1) "NGU High" Luma upscaling with 1080 -> 4K at 60fps? (Chroma set to "normal").
2) Tone mapping including highlight recovery and measurements at 4K 60fps?

Correct? Thanks!

[Siso]

Originally Posted by SamuriHL

On my 6gb 1060 I stick with medium. It's very subjective but most people aren't going to see a HUGE difference between medium and high and on lower end equipment where performance matters more it's certainly not worth it IMO.

Good point.

[mytbyte]

Originally Posted by Warner306

Bad metadata or lack of metadata. The measurement would be more accurate. The metadata is just available to assist with tone mapping.

Well, I took the HDR clipping pattern that is also marked as 1000 nits max and when I set peak brightness in MadVR to 10000 nits, I get visible flashing bars all the way accross so there IS data all the way up to 10000 nits in the file and madVR detects that, apparently.

Originally Posted by Warner306

I would doubt you are crushing black given the accuracy of your calibration.

Just measured that my near black tracking is rising slower than the BT.2390 reference (up to 8% stimulus), so it is darker than it should be, but data is there.

[SamuriHL]

Originally Posted by madshi

@SamuriHL, just to get a speed impression, with your 1060, I suppose you can do the following with ease:

1) "NGU High" Luma upscaling with 1080 -> 4K at 60fps? (Chroma set to "normal").
2) Tone mapping including highlight recovery and measurements at 4K 60fps?

Correct? Thanks!

1) Rendering is hanging out around 27ms or lower average with NGU Sharp HIGH luma upscaling 1080 -> 4k 60. Chroma set to normal.

2) Rendering is about 35ms or so at 4k 60 with tone mapping highlight recovery measurements and 65% desat.

Of note I am using D3D11 decoding not doing any copy back.

P.S. All trade quality options are disabled.

[Balthazar2k4]

Out of curiosity what is the state of madVR with an AMD Vega solution for 4K HDR material? I am looking to replace my HTPC with a Hades Canyon NUC (8809G) and want to understand what issues I might run into. I saw a post way back about madVR being unable to autoswitch HDR mode in Windows with AMD cards. Has this changed?

I am presently using a GTX960/Pentium G4600 based machine now and want to get a similar experience... just smaller.

Edit: I see that AMD now has a private HDR API that madVR will utilize. That answers that, but is there anything else that might be an issue?

[Alexkral]

Hi Madshi,

I'm sorry to be late for your request of feedback about NNEDI3, like many others I don't update madVR very often (I'm still using 0.92.2 now), neither read this thread, but I think there was a good reason to keep it. Maybe nobody else noticed, but it is/was the only doubling algorithm capable of independent width or height doubling. I encode my BD3Ds to 1920 x 2160 OU for viewing on my FPR UHD TV. This way there is no need to upscale the height, the TV just take the available lines and reorder them in a line alternative scheme. When I play these videos in fullscreen with madVR using NNEDI3 for doubling, I can see in the OSD that after chroma upscaling, luma x (or the whole image x depending on settings for chroma doubling) is upscaled with NNEDI and image y is left untouched. But if I choose super-xbr or NGU for doubling, I can see that after chroma upscaling, both image x and image y are upscaled and then image y is downscaled with the algorithm chosed.
I understand that you had reasons to remove NNEDI3 so I'm not going to ask for it back, but maybe this feature could be added to NGU. Anyway I suspect that image y doubling to 4320 and then downscaling back to 2160 should not mean a significant quality loss, but given that it is not necessary in this situation, maybe I should just forget about doubling and use one of the other upscaling algorithms.

Also, I don't understand if the new option "tone map HDR using external 3DLUT" is just for processing HDR, or for both processing HDR and converting HDR to SDR.

[422415]

Originally Posted by Asmodian

I can set RGB Full 12 bpc in 1809 and 416.34. I simply change the refresh rate first, setting it to RGB Full 8 bpc 340x2160p23, and then after I am in 23 Hz I can set 12 bpc, this lives through reboots and similar without issue. However, this is not with a custom 23 Hz mode, with a custom mode I simply cannot use >8 bit at all.

I just updated to Windows 1809 and 416.34 and it still will not switch to 12bpc. Incredibly frustrating.

[el Filou]

On my my 1050 Ti on 1080 display I have to check 'compromise on mapping accuracy' for 60p HDR content. With 24p it's fine.
Not a big deal for me as most HDR content besides demos still is 24p movies at the moment.

[ryrynz]

HDR looks terrible with that enabled.. Compromise on anything else..

[Warner306]

Originally Posted by el Filou

On my my 1050 Ti on 1080 display I have to check 'compromise on mapping accuracy' for 60p HDR content. With 24p it's fine.
Not a big deal for me as most HDR content besides demos still is 24p movies at the moment.

If you create a profile for 4K60 with scale chroma separately checked under trade quality for performance, you should be able to enable everything again, save highlight recovery.

[Warner306]

Originally Posted by Balthazar2k4

Out of curiosity what is the state of madVR with an AMD Vega solution for 4K HDR material? I am looking to replace my HTPC with a Hades Canyon NUC (8809G) and want to understand what issues I might run into. I saw a post way back about madVR being unable to autoswitch HDR mode in Windows with AMD cards. Has this changed?

I am presently using a GTX960/Pentium G4600 based machine now and want to get a similar experience... just smaller.

Edit: I see that AMD now has a private HDR API that madVR will utilize. That answers that, but is there anything else that might be an issue?

It will work fine. However, the NUC is expensive and has an overpowered CPU for a HTPC. A Zotac Zbox with a GTX 1060 would be a better choice.

[Warner306]

Originally Posted by SamuriHL

2) Rendering is about 35ms or so at 4k 60 with tone mapping highlight recovery measurements and 65% desat.

Of note I am using D3D11 decoding not doing any copy back.

P.S. All trade quality options are disabled.

What are your rendering times when chroma upscaling is set to something like Lanczos3 and dithering set to Ordered Dithering?

[SamuriHL]

Oh hell, that's right, I did set dithering to ordered a couple weeks ago and forgot about it. As for chroma I'd have to check and I don't know if I'll have time to test tonight. I should be able to tomorrow.

[Warner306]

Just curious. I thought the GTX 1060 was faster than that.

[SamuriHL]

Originally Posted by SamuriHL

1) Rendering is hanging out around 27ms or lower average with NGU Sharp HIGH luma upscaling 1080 -> 4k 60. Chroma set to normal.

2) Rendering is about 35ms or so at 4k 60 with tone mapping highlight recovery measurements and 65% desat.

Of note I am using D3D11 decoding not doing any copy back.

P.S. All trade quality options are disabled.

So this was with ordered dithering. However, changing it to error diffusion 2 didn't seem to make much difference. I'm still kicking around 30ms for 4k 60.

Changing to laczos3 as Warner306 suggested (still with error diffusion 2) lowers it down to ~20ms.

And changing THAT to ordered dithering lowers it to ~18ms.

Hope this helps!

[Axelpowa]

Hi,

I'm trying to set multiple profiles in madVR under the device settings for HDR taking hdrpeaknit of a movie in account.

Like this

If (hdrpeaknit <=1000) "275" (275 would be a profile)
Else if.....
Else if....
Else...

The problem I have is that my Projector jvc x7500 switches to HDR profile as if I were sending metadata to the projector instead of staying in my sdr2020 profile.

Any way to avoid this?

Regards!

[Manni]

Are you sure you've selected pixel shader in each of your HDR profile? There shouldn't be any HDR metadata sent with pixel shader, unless you've selected the "output video in HDR" option.

Otherwise you might want to try checking the "report BT2020" box in the calibration tab if you have an nVidia GPU. Or if it's checked, try uncheking it. But it shouldn't force HDR mode in the JVCs either way.

[Axelpowa]

Originally Posted by Manni

Are you sure you've selected pixel shader in each of your HDR profile? There shouldn't be any HDR metadata sent with pixel shader, unless you've selected the "output video in HDR" option.

Otherwise you might want to try checking the "report BT2020" box in the calibration tab if you have an nVidia GPU. Or if it's checked, try uncheking it. But it shouldn't force HDR mode in the JVCs either way.

Hi Manni,

Yes, I've checked it. Was the first thing I thought, but it is correct. I created every profile duplicating the one I use for sdr2020 pixel shader. After that I just changed the peak nits target for every profile.

Regards!

[Manni]

Originally Posted by Axelpowa

Hi Manni,

Yes, I've checked it. Was the first thing I thought, but it is correct. I created every profile duplicating the one I use for sdr2020 pixel shader. After that I just changed the peak nits target for every profile.

Regards!

Did you check that the profile that should be enabled with your logic is indeed enabled? Otherwise it could be another profile that's selected for whatever reason.

If your sdr2020 pixel shader profile behaves correctly and you've simply copied it to create the others, then I have no idea, except checking every single option.

If you enable a copy where nothing is changed from your original profile, does it behave as the original or does it not work?

Apart from that I can't think of anything else. I have an X7000 and I use a Vertex to disable the HDR metadata anyway, so I don't have this problem.

[Warner306]

Originally Posted by SamuriHL

So this was with ordered dithering. However, changing it to error diffusion 2 didn't seem to make much difference. I'm still kicking around 30ms for 4k 60.

Changing to laczos3 as Warner306 suggested (still with error diffusion 2) lowers it down to ~20ms.

And changing THAT to ordered dithering lowers it to ~18ms.

Hope this helps!

So the GTX 1060 is just slightly too slow for tone mapping at 4K 60 fps. This is helpful because I am often talking to people building PCs at AVSForums, mostly for madVR. The GTX 1060 still seems like a good choice, but the GTX 1070 is required for 4K 60 fps with extra sauce.