madVR - high quality video renderer (GPU assisted)

[Manni]

What I meant is that maybe both win10 and the Nvidia custom solution might have small errors in their data (e.g. a rounding error) which might result in the Vertex not reporting anything. It's also possible that the data is completely empty (zeroed out), or just wrong. I don't know, any of that is probably possible. The only thing we know for sure is that neither win10 nor Nvidia output perfect gamut metadata. Maybe there's a small error, maybe they're completely wrong, we don't know that for sure right now. I suppose the Vertex isn't able to show the raw hex bytes?

See my post above re which values the Vertex supports.

The Vertex of course can show the raw metadata, just not on the OSD where it's more useful to have it decoded for human consumption :)

In any case, there is ZERO reason for any software to change the metadata in pass-though mode. I have validated playing the files with the UB900 that the metadata was present and correct in the files, so both MS and nVidia should not touch it in passthrough mode.

I'll post the full HEX for both modes when I find the time.

[madshi]

Full hex would be interesting. I should be able to decode it, if you can post the correct hex data for the UB900, too.

[Manni]

Full hex would be interesting. I should be able to decode it, if you can post the correct hex data for the UB900, too.

Yes, this is what I was planning to do :)

So here we go, starting with the Exodus trailer played by the UB900:
87:01:1a:91:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80:3e:13:3d:42:40:b0:04:c8:00:00:00:00:00

This is decoded by the Vertex as:
Exodus: ST2084 max 1200/ min 0.020 MaxCLL/FALL 0/0 mastering display primaries DCI-P3 white point D65

Playing the same file from the HTPC, with OS HDR Off:
87:01:1a:79:02:00:d0:84:80:3e:4c:1d:b8:0b:c2:33:c4:86:42:40:00:00:b0:04:c8:00:b0:04:b0:04

This, as already reported, is decoded by the Vertex as:
Exodus: ST2084 max 1200/ min 0.020 MaxCLL/FALL 1200/1200 mastering display primaries nothing white point nothing

Finally, playing the same file from the HTPC, with the OS set to HDR On:
87:01:1a:fb:02:00:d0:84:7f:3e:c2:33:c3:86:4b:1d:b7:0b:12:3d:42:40:e8:03:2c:01:e8:03:14:00

This, as already reported, is decoded by the Vertex as:
Exodus: ST2084 max 1000/ min 0.030 MaxCLL/FALL 1000/20 mastering display primaries nothing white point nothing

Note that if I stop playback when the OS HDR is set to on, the metadata stays the same, which proves that it's not content related and the the OS simply sends a fixed metadata whether content is playing or not.

If I stop playback when the OS HDR is set to off, the Vertex correctly reports no HDR metadata.

Hope this helps, I don't have the time to check the HEX data myself, please let me know if you find any error in the Vertex decoding vs the HEX data.

[Manni]

Forgot to say, ignore the first 4 hex values, I don't think they are part of the header, the header starts (I think) at 02:00 etc but I don't have time to check, let me know if you struggle and I'll take a closer look.

[oddball]

On HDR not working. I have a AMD MSI Radeon RX 480 8GB Gaming X. I am using the latest driver 17.8.1 (older drivers made no difference anyhow).

It's been the same way since HDR was introduced in MadVR. It only works with HDR enabled in Win10, FSE disabled and by clicking on certain system tray icons like MadVR and a couple of others. If I hover above the icons it works for a few seconds then goes back to being washed out. I have to click on the MadVR icon to bring up the menu options for it to stay in the correct color output. Also as stated the auto switching Win10 from SDR to HDR mode is not working.

Has anyone else successfully got HDR working correctly with auto switching in Windows using AMD GPU's?

I also have aufkrawall's issue with wrong 'dark' colors decoding HEVC using DXVA2.

[madshi]

@Manni, can you please post the hex data with this test build for both HTPC options?

http://madshi.net/madVRmanni.rar

@oddball, do you have D3D11 presentation activated, and the display properties set to 10bit? Only then dynamic HDR switching works with AMD.

[zapatista]

Hi Madchi,

in the last couple of years i have reliably used your program as an addon for MPC-HT, and thank you for the great program you made !

but since recently doing a repair on my win7 (64 bit) OS i am having problems re-installing madvr

am using win7 64 bit with an i7 , 32gb ram with amd 5770 card

MPC-HT runs fine (64 bit), and my amd catalyst drivers are correctly installed

when i run the installation of madvr it seems to run correctly (the usual dos box opens with the brief msg about file locations), but madvr doesnt show up on my right click options in MPC-HT anymore

i vaguely remember a few yrs ago having a similar problem (which i resolved, and it was something simple iirc) but i cant find any problem solving information text file online right now that might help me solve this. is there a Q&A file for errors i can check somewhere ? or some advice you can give me on what to check ?

[huhn]

if you mean mpc-hc with mpc-ht you have to select madVR under options -> Output -> DirectShow video -> madVR

[oddball]

@Manni, can you please post the hex data with this test build for both HTPC options?

http://madshi.net/madVRmanni.rar

@oddball, do you have D3D11 presentation activated, and the display properties set to 10bit? Only then dynamic HDR switching works with AMD.

But of course. Otherwise HDR would not work correctly even by clicking on the MadVR icon. I have tried with copy back and the new D3D11 options. Something is not working through the entire chain.

Note: Setting HDR to on in Win10 display settings causes the LG OLED55B6V to switch to HDR mode and the HDR logo displays on the TV. But simply playing back an HDR video results in washed out colors. FSE has to be disabled and I have to click on the MadVR icon to get the correct color output and brightness levels. If I leave HDR off in display settings it will not auto switch to HDR.

[oddball]

Hi Madchi,

in the last couple of years i have reliably used your program as an addon for MPC-HT, and thank you for the great program you made !

but since recently doing a repair on my win7 (64 bit) OS i am having problems re-installing madvr

am using win7 64 bit with an i7 , 32gb ram with amd 5770 card

MPC-HT runs fine (64 bit), and my amd catalyst drivers are correctly installed

when i run the installation of madvr it seems to run correctly (the usual dos box opens with the brief msg about file locations), but madvr doesnt show up on my right click options in MPC-HT anymore

i vaguely remember a few yrs ago having a similar problem (which i resolved, and it was something simple iirc) but i cant find any problem solving information text file online right now that might help me solve this. is there a Q&A file for errors i can check somewhere ? or some advice you can give me on what to check ?

Have you set MadVR as the default renderer in MPC? Did you run the install.bat as Administrator?

[zapatista]

thanks huhn !

it was indeed as simple as that, another RTFM error resolved :D

[zipeldiablo]

Hi guys, is there a compendium or an up-to-date tutorial somewhere on how to customize madvr + mpc-hc + lav filters (from what i found online those are the required tools?) in order to get hdr from hdr content (tried passthrough and stuff and colors are washed out) and upscaling properly non 4k content for a 4k oled hdr screen.

[Manni]

@Manni, can you please post the hex data with this test build for both HTPC options?

http://madshi.net/madVRmanni.rar



Sure, here you go :)

With test build, here is what I get with OS HDR Off:

87:01:1a:29:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80:3e:13:3d:42:40:b0:04:c8:00:b0:04:b0:04

The Vertex reports:
Exodus: ST2084 max 1200/ min 0.020 MaxCLL/FALL 1200/1200 mastering display primaries DCI-P3 white point D65
so all correct now apart from MaxCLL/FALL which are not supported yet by MadVR.

With OS HDR On:
87:01:1a:fb:02:00:d0:84:7f:3e:c2:33:c3:86:4b:1d:b7:0b:12:3d:42:40:e8:03:2c:01:e8:03:14:00

This is the same MS fixed metadata as with the non-test build, so the Vertex decodes the same:
Exodus/Anything/Nothing playing: ST2084 max 1000/ min 0.030 MaxCLL/FALL 1000/20 mastering display primaries nothing white point nothing

[Manni]

I also tested the two other files (Neo fire and RM Brightness) with OS HDR off, and all the metadata is now reported correctly (to the exception of the not-yet-supported MaxCLL/FALL of course) with the test build.

[Gee]

i dont have a HDR switch in my Win 10 Version.. its the actual 1703 Build.. :/

[madshi]

But of course. Otherwise HDR would not work correctly even by clicking on the MadVR icon. I have tried with copy back and the new D3D11 options. Something is not working through the entire chain.

Note: Setting HDR to on in Win10 display settings causes the LG OLED55B6V to switch to HDR mode and the HDR logo displays on the TV. But simply playing back an HDR video results in washed out colors. FSE has to be disabled and I have to click on the MadVR icon to get the correct color output and brightness levels. If I leave HDR off in display settings it will not auto switch to HDR.
Not sure what's wrong. You could try to remove and totally clean the AMD driver installation and then reinstall it. If that doesn't help, maybe an OS reinstall is the only solution. Not sure what else to suggest.

Hi guys, is there a compendium or an up-to-date tutorial somewhere on how to customize madvr + mpc-hc + lav filters (from what i found online those are the required tools?) in order to get hdr from hdr content (tried passthrough and stuff and colors are washed out) and upscaling properly non 4k content for a 4k oled hdr screen.
Which GPU?

The Vertex reports:
Exodus: ST2084 max 1200/ min 0.020 MaxCLL/FALL 1200/1200 mastering display primaries DCI-P3 white point D65
so all correct now apart from MaxCLL/FALL which are not supported yet by MadVR.
Great! :)

Now I wish you had an AMD GPU, so we could test that, too... :o

i dont have a HDR switch in my Win 10 Version.. its the actual 1703 Build.. :/
Which GPU?

[Manni]

Great! :)

Now I wish you had an AMD GPU, so we could test that, too... :o


I still have my HD7870 but I don't have the time to swap it with the 1080 Ti at the moment. I'll see what I can do and I'll let you know.

[Gee]

not sure what's wrong. You could try to remove and totally clean the amd driver installation and then reinstall it. If that doesn't help, maybe an os reinstall is the only solution. Not sure what else to suggest.


Which gpu?


Great! :)

now i wish you had an amd gpu, so we could test that, too... :o


which gpu?

gtx 950

[huhn]

and you have an HDR10 TV ?

[madshi]

I still have my HD7870 but I don't have the time to swap it with the 1080 Ti at the moment. I'll see what I can do and I'll let you know.
I'm not sure if the 7870 can do HDR at all, but it would be interesting to know!

and you have an HDR10 TV ?
Good question. Another question is if the HTPC is directly connected to the TV, or maybe there's an AVR in between? If the AVR doesn't support HDR, the HTPC might not know that the TV supports it.

[Razoola]

Interesting. Can you please double check the following:

madVR tries to get the EDID from the registry. The path is retrieved like this:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\DISPLAY\xxxxx\Device Parameters\EDID

The "xxxxx" is coming from the string that the madVR settings dialog shows for your monitor as the "Windows device path". It starts with "\\?\DISPLAY". I think on your PC it should be:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\DISPLAY\Default_Monitor\5&6dedc66&0&UID2097424\Device Parameters\EDID

Does this registry path exist and is there an "EDID" entry there?


I have had a look and at location

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\DISPLAY\Default_Monitor\5&6dedc66&0&UID2097424\Device Parameters\

there is just a BAD_EDID key and no EDID key.

However at location

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\VSC0E23\5&6dedc66&0&UID2097424\Device Parameters\

The EDID key and information is present.

[madshi]

I have had a look and at location

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\DISPLAY\Default_Monitor\5&6dedc66&0&UID2097424\Device Parameters\

there is just a BAD_EDID key and no EDID key.

However at location

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\VSC0E23\5&6dedc66&0&UID2097424\Device Parameters\

The EDID key and information is present.
Interesting. It seems that Windows has your monitor currently registered as the "Default_Monitor" and not the "VSC0E23" monitor, which is why madVR can't find the EDID. I'm not sure why, though. I suppose you could try deleting both monitors and let the OS redetect them.

[Razoola]

Interesting. It seems that Windows has your monitor currently registered as the "Default_Monitor" and not the "VSC0E23" monitor, which is why madVR can't find the EDID. I'm not sure why, though. I suppose you could try deleting both monitors and let the OS redetect them.

Would that simply be a case of deleting the registry keys and then uninstalling the driver?

[madshi]

I think you can delete the monitors in the device manager? I don't think you have to manually edit the registry.

[Manni]

I'm not sure if the 7870 can do HDR at all, but it would be interesting to know!


You are correct. The HD7870 can display HDR if you can force HDR manually on the display (I certainly did, although the framerate wasn't great and all settings had to be tuned down) but it wouldn't pass through the metadata as it's HDMI 1.4, not HDMI 2.0, so the drivers would not handle it. Sorry I can't help with that... :o

[madshi]

Too bad, thanks for trying, though! :) The OS didn't show the "HDR and Advanced Color" switch, either, correct?

[Manni]

Too bad, thanks for trying, though! :) The OS didn't show the "HDR and Advanced Color" switch, either, correct?

Oh sorry for the misunderstanding, I didn't try, I just think that you are correct and that the OS (and most likely drivers) would not support it like an HDR card, so the options wouldn't be there even if the monitor is HDR. Also I don't think the driver would know how to handle the metadata if the GPU doesn't have HDMI 2.0 capability. How could it? So while I know that it can (badly) display HDR content, I have no hope that I could help you with debugging the metadata. Given my lack of time at the moment, I'd rather save it for something more likely to help as we're talking a couple of hours to swap the two cards, test and put the 1080 Ti back given the way my rig is set up.

[madshi]

I'm not completely sure how much of a GPU HDMI port can be "updated" via software. I think a GPU HDMI port is much more flexible than a CE device HDMI port. So while a GPU HDMI port will not be able to suddenly passthrough more bandwidth with a driver update, additional "features" like an HDR metadata block is something that I could imagine to be upgradable via software. So in theory it might be possible for an older AMD GPU to still support HDR, but I don't really know for sure. And even if it's technically feasible, it's still a question if AMD wants to do such an upgrade. They might want to have HDR as an exclusive feature for newer GPUs.

Anyway, the reason I've asked about the OS switch is that the whole AMD dynamic HDR switching solution is much more picky than the Nvidia solution. Nvidia just switches the TV into HDR mode, if you ask it to, no questions asked. It works even if no video is running at all. In contrast to that AMD is very picky, it only activates HDR if you have an active fullscreen 10bit swapchain. Because of that it's easy to think that the AMD switching doesn't work, even if it might work with slightly tweaked settings. The OS switch is more "reliable" as a detection for the HDR capability of the GPU -> display chain.

All that said, I'm pretty sure you tested with 10bit fullscreen, so probably your test was already "final".

[Razoola]

I think you can delete the monitors in the device manager? I don't think you have to manually edit the registry.

I had a go but it did not help. For me though its ok because custom resolutions I more want on the displays that have an AVR between them and the PC rather than my PC monitor. So I can wait until you have support for that rather than spend more time understanding whats gone wrong with my win 7 display situation. Its a weird one, looking into it more even Monitor Asset Manager does not see the display as active when it is.

[Manni]

I'm not completely sure how much of a GPU HDMI port can be "updated" via software. I think a GPU HDMI port is much more flexible than a CE device HDMI port. So while a GPU HDMI port will not be able to suddenly passthrough more bandwidth with a driver update, additional "features" like an HDR metadata block is something that I could imagine to be upgradable via software. So in theory it might be possible for an older AMD GPU to still support HDR, but I don't really know for sure. And even if it's technically feasible, it's still a question if AMD wants to do such an upgrade. They might want to have HDR as an exclusive feature for newer GPUs.

Anyway, the reason I've asked about the OS switch is that the whole AMD dynamic HDR switching solution is much more picky than the Nvidia solution. Nvidia just switches the TV into HDR mode, if you ask it to, no questions asked. It works even if no video is running at all. In contrast to that AMD is very picky, it only activates HDR if you have an active fullscreen 10bit swapchain. Because of that it's easy to think that the AMD switching doesn't work, even if it might work with slightly tweaked settings. The OS switch is more "reliable" as a detection for the HDR capability of the GPU -> display chain.

All that said, I'm pretty sure you tested with 10bit fullscreen, so probably your test was already "final".

If you're talking about the test I did with nVidia, yes I tested in windowed 10bits full screen (see details of drivers config in my sig), so yes my test was final.

I didn't test with my decommissioned AMD 7870 because I don't believe AMD would handle the dynamic metadata on an HDMI 1.4, non HDMI 2.0a compliant GPU (although I agree it's probably possible technically). If someone confirms that they can get their display connected to an HD7870 (or HD7xxx) to switch to HDR automatically with MadVR (which means the metadata is carried through) on Windows 10 Pro x64, I'll give it a try if I can find the time (and if they provide the driver version).

Whenever I tried to play HDR on the HD7870, it never carried the metadata, I always had to switch the display to HDR manually. I didn't try recently though as I had no reason to, all my UHD/HDR content being played by the UB900 as there is no way to get legit consumer HDR content on our HTPCs yet.

[Q-the-STORM]

With OS HDR On:
87:01:1a:fb:02:00:d0:84:7f:3e:c2:33:c3:86:4b:1d:b7:0b:12:3d:42:40:e8:03:2c:01:e8:03:14:00

This is the same MS fixed metadata as with the non-test build, so the Vertex decodes the same:
Exodus/Anything/Nothing playing: ST2084 max 1000/ min 0.030 MaxCLL/FALL 1000/20 mastering display primaries nothing white point nothing

This string does have primaries and white point:

R: x=0.6800 y=0.3200
G: x=0.2650 y=0.6900
B: x=0.1500 y=0.0600

White point: x=0.3127 y=0.3290

[madshi]

Does anybody have an AMD 7xxx running with an HDR display?

[nsnhd]

So in theory it might be possible for an older AMD GPU to still support HDR, but I don't really know for sure.

I didn't test with my decommissioned AMD 7870 because I don't believe AMD would handle the dynamic metadata on an HDMI 1.4, non HDMI 2.0a compliant GPU (although I agree it's probably possible technically). If someone confirms that they can get their display connected to an HD7870 (or HD7xxx) to switch to HDR automatically with MadVR (which means the metadata is carried through) on Windows 10 Pro x64, I'll give it a try if I can find the time (and if they provide the driver version).

Whenever I tried to play HDR on the HD7870, it never carried the metadata, I always had to switch the display to HDR manually. I didn't try recently though as I had no reason to, all my UHD/HDR content being played by the UB900 as there is no way to get legit consumer HDR content on our HTPCs yet.

FYI, I'm watching HDR contents on my high-contrast 1080p monitor using downscaled 4k HDR or youtube 1080p HDR clips. So, I don't know about AMD but on my Intel HD4600 igpu with HDMI 1.4 when I choose "passthrough HDR to the display" the picture colors changes totally by select "send HDR metadata to the display" (by unselect that the picture washes out). Of course my monitor is a non-hdr one then colors are not quite correct, but they are nearly hdr colors. So at least, HDMI 1.4 might carry hdr metadata.

[Manni]

FYI, I'm watching HDR contents on my high-contrast 1080p monitor using downscaled 4k HDR or youtube 1080p HDR clips. So, I don't know about AMD but on my Intel HD4600 igpu with HDMI 1.4 when I choose "passthrough HDR to the display" the picture colors changes totally by select "send HDR metadata to the display" (by unselect that the picture washes out). Of course my monitor is a non-hdr one then colors are not quite correct, but they are nearly hdr colors. So at least, HDMI 1.4 might carry hdr metadata.

This doesn't mean that the metadata is sent, it means that the source sends ST2084/BT2020 and the display doesn't display it correctly because it doesn't have an HDR mode and can't switch to it.

We need confirmation from someone with an HD7xxx and an HDR monitor switching correctly and automatically when HDR content is sent to HDR mode.

Please only reply to Madshi's request if you do have an HD7xxx running on Win 10 Pro x64 (Creators Update) and an HDR monitor behaving as described above.

Thanks!

[Manni]

This string does have primaries and white point:

R: x=0.6800 y=0.3200
G: x=0.2650 y=0.6900
B: x=0.1500 y=0.0600

White point: x=0.3127 y=0.3290

Thanks, this should be reported as DCI-P3 and D65 if the data is correct. I'll double check next time.

[Oguignant]

Hi!

I have a question. I always use the settings of my tv like Chroma subsampling 4: 2: 2 10 bits to use the options of like TruMotion, Realcinema and noise reduction, etc. To be able to use 4.4.4 I must change the HDMI input to PC MODE, but I lose all those features. Also, I do not know why Calman RGB autocalibration does not work very well in 4.4.4. My question is, I lose a lot of quality using 4.2.2 10bits vs 4.4.4 8bits? Or what do I lose?

This!

[madshi]

This string does have primaries and white point:

R: x=0.6800 y=0.3200
G: x=0.2650 y=0.6900
B: x=0.1500 y=0.0600

White point: x=0.3127 y=0.3290
The actual values are not exactly like that. What you listed are the exact DCI-P3 coordinates, but the hex data is 1 too low for some values. Furthermore, and more importantly, the order of the channels is incorrect. It should be GBR, but win10 outputs RGB instead.

FYI, I'm watching HDR contents on my high-contrast 1080p monitor using downscaled 4k HDR or youtube 1080p HDR clips. So, I don't know about AMD but on my Intel HD4600 igpu with HDMI 1.4 when I choose "passthrough HDR to the display" the picture colors changes totally by select "send HDR metadata to the display" (by unselect that the picture washes out). Of course my monitor is a non-hdr one then colors are not quite correct, but they are nearly hdr colors. So at least, HDMI 1.4 might carry hdr metadata.
Current Intel drivers don't support HDR at all. If you activate "passthrough" mode with "send HDR metadata" it's actually win10 in this situation which performs a low quality HDR to SDR conversion.

[Manni]

The actual values are not exactly like that. What you listed are the exact DCI-P3 coordinates, but the hex data is 1 too low for some values. Furthermore, and more importantly, the order of the channels is incorrect. It should be GBR, but win10 outputs RGB instead.


Thanks, I was just in the process of checking this and reached the same conclusion. :)

[Ava Pug]

I thought I'd give an update about the issue I had. I 'fixed' it by enabling this option in the nvidia control panel.

When it's turned on (with any setting there) madvr now uses the custom resolutions it made with FSE off/on and DX11 off/on.

When I set it back to 'Use default color settings' it goes back to how it was before.

http://i.imgur.com/uAguCNb.jpg

Is this option ok to be left on?

[Damie]

HDR passthrough doesn't work (TV won't switch into HDR mode) with Intel i5-7600k iGPU (HD Graphics 630) even though it works with Nvidia GTX 1070.

Is this problem caused by MadVR, Intel drivers or Club3D Displayport 1.2->HDMI 2.0 adapter?

Edit: Solved, gotta wait for HDR support in Intel drivers :)

[dvd1]

scuste my English. I'm a disabled boy, I do not walk. My only fun is the TV and the PC. I do not have much money, so I have to keep my old gt730 for a long time. I would be happy if you help me get the most for DVD profiles, 720 and 1080p. How to set up nvideo control panel, set LAVs, and set madVR to save resources and have good video quality
thank you so much

Ps what graphics card recommend me. Good, but costs just over 150 euros
PCE 2.0

[zipeldiablo]

Which GPU?


I have a gtx 1080ti.
My os is win10 pro creators update 64bits.
And the tv is a lg oled55c6v .

[Dreamland]

Information about my monitor is not true with some parameters

https://t12.pixhost.org/thumbs/265/49852865_kkkk025.png (https://pixhost.org/show/265/49852865_kkkk025.png)

Bitdepths=10 bit
Widegamuts=Yes

thx Madshi

[Oguignant]

You are correct. The HD7870 can display HDR if you can force HDR manually on the display (I certainly did, although the framerate wasn't great and all settings had to be tuned done) but it wouldn't pass through the metadata as it's HDMI 1.4, not HDMI 2.0, so the drivers would not handle it. Sorry I can't help with that... :o

RGB Full 4:4:4 12bits... Manni, how is that?

[Manni]

RGB Full 4:4:4 12bits... Manni, how is that?

Great, why? :)

EDIT: Sorry you probably thought I was still using an HD7870. I don't. I have an nVidia 1080 Ti. I just haven't sold the HD7870, but it's not being used (I was talking about when it was used in the post you quoted, and of course that wasn't RGB Full 4:4:4 12 bits with the HD7870). See the rest of my sig :)

[Oguignant]

Great, why? :)

EDIT: Sorry you probably thought I was still using an HD7870. I don't. I have an nVidia 1080 Ti. I just haven't sold the HD7870, but it's not being used (I was talking about when it was used in the post you quoted, and of course that wasn't RGB Full 4:4:4 12 bits with the HD7870). See the rest of my sig :)

I also use all my content in 23 or 24 mhz with my gtx 1080 ti. But how do you make it switch automatically to 23mhz@12bits?

[Oguignant]

Does anyone clarify this for me? I always use RGB full 8 bits in D3d11 exclusive mode (10 bits) recently, I discovered that I can use for 23, 24, 25, 29, 30 mhz in 12 bits enabling RGB48 in Lav Video decoder and disabling all other options. I have to also change 12 bits to RGB full in 23, 24, 25, 29 and 30 mhz in nvidia control panel too? Is there a way to do it automatically from "display modes" from Madvr config? Or just modifying since Lav Video decorating is enough?

[Asmodian]

No, that is not the way to get 10-bit!

NEVER disable any color modes in LAV Video for maximum quality. nevcairiel has said before that conversion to RGB is not done at maximum quality in LAV (the chroma must be scaled by LAV to do this). You want madVR to receive the decoded but untouched video from LAV, not force LAV to do a quick and dirty conversion to RGB48 for no reason.

Only change the bit depth in the Nvidia control panel and madVR (the display's property).

Sadly madVR's new custom modes seem to only be 8-bit modes. However, if you set a standard 23-30Hz mode to 12-bit in the Nvidia control panel and then do not set the bit-depth to anything when switching back to 60Hz (the box goes blank on my system but is using 8-bit in >30Hz modes) when madVR automatically switches to a mode that supports 12-bit it does use 12-bit.

edit: The line in madVR's OSD that is confusing you is the one that looks something like: "h264 8 bit 4:2:0 -> NV12 8 bit, 4:2:0"?
That line is only discussing the source, in my example the video was H.264 8 bit 4:2:0 and madVR received it as NV12 8 bit 4:2:0 video data from LAV (madVR only reports the codec for H.264, everything else only has the bit depth and sub-sampling/RGB).

[Oguignant]

No, that is not the way to get 10-bit!

NEVER disable any color modes in LAV Video for maximum quality. nevcairiel has said before that conversion to RGB is not done at maximum quality in LAV (the chroma must be scaled by LAV to do this). You want madVR to receive the decoded but untouched video from LAV, not force LAV to do a quick and dirty conversion to RGB48 for no reason.

Only change the bit depth in the Nvidia control panel and madVR (the display's property).

Sadly madVR's new custom modes seem to only be 8-bit modes. However, if you set a standard 23-30Hz mode to 12-bit in the Nvidia control panel and then do not set the bit-depth to anything when switching back to 60Hz (the box goes blank on my system but is using 8-bit in >30Hz modes) when madVR automatically switches to a mode that supports 12-bit it does use 12-bit.

edit: The line in madVR's OSD that is confusing you is the one that looks something like: "h264 8 bit 4:2:0 -> NV12 8 bit, 4:2:0"?
That line is only discussing the source, in my example the video was H.264 8 bit 4:2:0 and madVR received it as NV12 8 bit 4:2:0 video data from LAV (madVR only reports the codec for H.264, everything else only has the color space).

Perfectly clear! Thks! Then the 12 bit change should do manual. Another question, In Lav Video decoder I use this option "Untouched (as input)", or I should use "PC (0-255)"

Another thing, when I change Nvidia cp 23 or 30 mhz 12 bits active HDR on my TV, I do not know why, what can be happening?

[Asmodian]

No need to quote me. :)

I leave it on PC (0-255) because this matches what I have madVR set to output, in the extremely unlikely event that LAV needs to covert to RGB for some reason. This usually has no effect when using madVR.

Maybe you have the Windows HDR option enabled? It auto disables itself if you switch to 8-bit explicitly and re-enables itself when you switch back. On my TV HDR only activates when I pass it metadata, either by using the option in Windows (which is only present in a 12-bit mode, or when that box is blank because I switched to 60Hz from 23Hz 12-bit), or by having madVR send it. 12-bit by itself doesn't switch my TV to HDR.