madVR - high quality video renderer (GPU assisted)

[SamuriHL]

Limited in the GPU or limited in madVR is fine, it is limited in both that is wrong. You get double range compression, madVR sends 16-235 to the GPU and the GPU compresses that again assuming it is full range. It may be an acceptable hack to get your 3D looking better but it isn't correct no matter what settings your TV has.

If you need this double compression to get an image without "ghosting" you are probably getting 3D crosstalk in shadows, a common problem with TVs with pixel response times that are a little too slow for 3D.I'm going to have to mess with it again to figure out what is going on. I had 2d working very well with full set everywhere. I don't think the Panasonic plasma is slightly too slow for 3d. I've never had this problem with it before so something screwy is going on. I may have an idea about that and if I'm right it's a setting I changed on the TV recently. I'll take a look.

Sent from my Pixel XL using Tapatalk

[dvd1]

yes, but on 1080p I do not have D3D11 but always D3D9
because?
nobody knows the problem?

[huhn]

you can share your settings.bin. but why are there profiles in rendering in the first place?

[dvd1]

you can share your settings.bin. but why are there profiles in rendering in the first place?
you want to see my setting. bin?
how do you do it?

[dvd1]

please see if there is any mistake

[SamuriHL]

That attachment is going to take forever to get approved. You're better off hosting it somewhere and linking to it.

[steakhutzeee]

Sorry, I should have used link instead of images.

No "Tick, tick, tick", i simply followed @Asmodian guide as a reference and now i'm testing these settings. If I had thought that these settings was totally ok, I would not have written here for suggestions.

MadVR noticed me to disable SuperRes in Upscaling Refinement if i use NGU, so i disabled.

It doesn't noticed me nothing about SuperRes in Chroma Up.

What should disable? Or change?No suggestions?

Inviato dal mio ASUS_Z00LD utilizzando Tapatalk

[SamuriHL]

Limited in the GPU or limited in madVR is fine, it is limited in both that is wrong. You get double range compression, madVR sends 16-235 to the GPU and the GPU compresses that again assuming it is full range. It may be an acceptable hack to get your 3D looking better but it isn't correct no matter what settings your TV has.

If you need this double compression to get an image without "ghosting" you are probably getting 3D crosstalk in shadows, a common problem with TVs with pixel response times that are a little too slow for 3D.

I'm going to have to mess with it again to figure out what is going on. I had 2d working very well with full set everywhere. I don't think the Panasonic plasma is slightly too slow for 3d. I've never had this problem with it before so something screwy is going on. I may have an idea about that and if I'm right it's a setting I changed on the TV recently. I'll take a look.

Sent from my Pixel XL using Tapatalk

Alright, I managed to get it working better with:

madvr: limited
gpu: full
tv: limited

I've read that this is an acceptable config so if someone wants to confirm or deny that for me I'd appreciate it. It seems to be working.

[x7007]

Alright, I managed to get it working better with:

madvr: limited
gpu: full
tv: limited

I've read that this is an acceptable config so if someone wants to confirm or deny that for me I'd appreciate it. It seems to be working.

For me it's

Madvr - 0-255
gpu - limited
Tv - Low which is 0-255

Everything seems fine , better than the 16-235 I had in MadVr on the old LED philips TV .
On my LED TV I had

Madvr- 16-235
gpu - limited
TV - I didn't have any option to really choose, only Computer/PC Mode or Game Mode which just reduce the lag input but Computer mode couldn't do good in 3D with the gamma or the black, so it made it too dark instead keeping in properly. hard to explain, but Game was the proper for PC/Game Console or anything on the AUTO Working side, or else on Computer just changing a lot things manually and even though it wouldn't work.


If you want new drivers to test , maybe if you have also WDDM 2.3 check this which on the Insider /Fast update

https://forums.guru3d.com/threads/windows-update-nvidia-display-9-3-2017-12-00-00-am-23-21-13-8768.416859/page-4

[SamuriHL]

For me it's

Madvr - 0-255
gpu - limited
Tv - Low which is 0-255

Everything seems fine , better than the 16-235 I had in MadVr on the old LED philips TV .
On my LED TV I had

Madvr- 16-235
gpu - limited
TV - I didn't have any option to really choose, only Computer/PC Mode or Game Mode which just reduce the lag input but Computer mode couldn't do good in 3D with the gamma or the black, so it made it too dark instead keeping in properly. hard to explain, but Game was the proper for PC/Game Console or anything on the AUTO Working side, or else on Computer just changing a lot things manually and even though it wouldn't work.


If you want new drivers to test , maybe if you have also WDDM 2.3 check this which on the Insider /Fast update

https://forums.guru3d.com/threads/windows-update-nvidia-display-9-3-2017-12-00-00-am-23-21-13-8768.416859/page-4

I had madvr, gpu, and tv all set to FULL (0-255) and it was working great for 2D. As soon as I played 3D content I got the ghosting issue which on that screen I'd never seen before. I love that my TV gives me the option to choose. I thought Pure Direct may have messed with it, but, that's forced off for 3D content. I may have to do some more testing with the XB1 and PS4 and see if they exhibit the same issue with FULL (0-255) and the TV forced to FULL (0-255), as well. I really don't know.

As for the drivers, I just got a new insider build pushed to me yesterday so I'm guessing it's got the latest insider driver already. I don't want to mess with it as I tried to downgrade it manually and it failed. Yes, I can force the issue but I'm just not in the mood to mess with driver issues right now. That's a distinct possibility for the source of my problem, however.

[pirlouy]

What should disable? Or change?
Everything. :)
Asmodian's thread explains options (thank him for this initiative), it does not mean you have to enable them all.
Another thing Asmodian should be sorry (https://forum.doom9.org/showthread.php?p=1818077#post1818077) of ! xD

Soften is the opposite of sharpen so you don't want to enable both.
Some eyes prefer sharpen images, other eyes prefer soften images.

These settings can improve images in some videos, but do the opposite on others so I advise you to disable everything first.
Then, if you have a lot of time, you can try these settings ONE BY ONE. Maybe you'll like one of them. Careful though, they can be bad for some videos.
But sorry, no shortcut for you, you'll need time. The easiest path is obviously to enable nothing, it won't mean image will be bad.

Image post-processing (or calibration) is over-hyped IMO but that's because I noticed judder (the real enemy) more easily than a pixel 50;86;211 instead of 48;82;220. ;)
And thanks for the [IMG] effort. Appreciate that. :thanks:

[el Filou]

madvr: limited
gpu: full
tv: limited

I've read that this is an acceptable config so if someone wants to confirm or deny that for me I'd appreciate it. It seems to be working.Everything other than video playback will show crushed blacks and clipped whites but if you're only using that machine for madVR it's OK (even though less optimal than RGB Full).

[SamuriHL]

Everything other than video playback will show crushed blacks and clipped whites but if you're only using that machine for madVR it's OK (even though less optimal than RGB Full).

Yea, it's primarily used for video playback. I would like to properly solve the issue and allow FULL across the board. I did just check, and the new insider driver is installed. No idea if that's the issue or not. Hence why I want to check it on the PS4 or XB1 and see if I get the same ghosting issue with that particular title. I've never really had an issue with 3D like this before. The fact that 2D works fine and 3D doesn't worries me a little cause I know the Panasonic plasma is fast enough.

[steakhutzeee]

Everything. :)
Asmodian's thread explains options (thank him for this initiative), it does not mean you have to enable them all.
Another thing Asmodian should be sorry (https://forum.doom9.org/showthread.php?p=1818077#post1818077) of ! xD

Soften is the opposite of sharpen so you don't want to enable both.
Some eyes prefer sharpen images, other eyes prefer soften images.

These settings can improve images in some videos, but do the opposite on others so I advise you to disable everything first.
Then, if you have a lot of time, you can try these settings ONE BY ONE. Maybe you'll like one of them. Careful though, they can be bad for some videos.
But sorry, no shortcut for you, you'll need time. The easiest path is obviously to enable nothing, it won't mean image will be bad.

Image post-processing (or calibration) is over-hyped IMO but that's because I noticed judder (the real enemy) more easily than a pixel 50;86;211 instead of 48;82;220. ;)
And thanks for the [IMG] effort. Appreciate that. :thanks:

Everything in Upscaling Refinement? I disabled SuperRes in chroma because i'm using NGU.

And disabled 'soften edges' refinement.

Enabled are 'sharpen/crispen edges', 'enhance detail', 'LumaSharpen and A.Sharpen' and 'anti-ringing'.

Settings for chroma, i. downscaling/upscaling are good?

[Manni]

Anyone knows why 4K60p RGB 8bits Full would give a magenta tint when playing a video with MadVR, while 4K30p RGB 8bits Full or 4K30p RGB 12bits Full would give the correct colors? 4K60p YCC 4:2:2 12bits give the correct colors too (4:4:4 isn't possible due to bandwidth limitations).

As I set the nVidia panel to 12bits RGB in 30p, the bit depth goes blank when playing 60p (it does send 8bits automatically to fit into the 18Gb/s bandwidth limitation of HDMI 2.0), so I tried to force the output to 8bits at 60p (8bits showing instead of blank in the nVidia control panel) and I get the same results.

I checked and it's not a wrong colorspace selected in the projector (whether I select RGB or YCC instead of Auto the colors are wrong at 4K60p in RGB).

Anyone?

I forgot to say that of course if I select EVR-CP the issue goes away, so clearly a MadVR issue.

I've done more tests today and this issue seems to be only present with HDR content.

It only happens if HDR is set to "Let MadVR decide" or to HDR Passthrough. If I select one of the SDR conversion options, the picture is fine.

FSE/Windowed doesn't make any difference.

What's very weird is that even when MPC-BE is windowed (not full screen), the magenta tint is on the whole desktop, not only on the player's window.

Hopefully Madshi can reproduce and fix.

[Asmodian]

This sounds like your display having a bad HDR mode, if madVR sends it the HDR metadata it looks wrong?

My system passes HDR to my TV correctly using an almost identical GPU. :confused:

[Manni]

This sounds like your display having a bad HDR mode, if madVR sends it the HDR metadata it looks wrong?

My system passes HDR to my TV correctly using an almost identical GPU. :confused:

No, it has nothing to do with the display HDR mode, 4K60 RGB 8bits works fine from the UB900.

Also I select the HDR mode manually, so it has nothing to do with the metadata. I get the same magenta screen with HDR content if the display mode is HD/Rec709 or HDR/BT2020, it makes no difference.

It's just that in that mode, MadVR sets the whole desktop (not just the player's window) to black and magenta. It's not a subtle calibration issue, it's a completely wrong mode.

When you say it works with your TV, did you test specifically for the mode I reported, and with the HDR settings I mentioned?

HDR passthrough with MadVR works fine here, except in 4K60 RGB 8bits, and only when MadVR isn't doing a conversion to SDR.

[dvd1]

please see if there is any mistake
http://www.mediafire.com/file/c3tt98krd2899en/settings.rar

[Asmodian]

When you say it works with your TV, did you test specifically for the mode I reported, and with the HDR settings I mentioned?

HDR passthrough with MadVR works fine here, except in 4K60 RGB 8bits, and only when MadVR isn't doing a conversion to SDR.

Yes, this works fine for me.
screenshot (http://i1222.photobucket.com/albums/dd496/asmodian3/The_World_in_HDR_in_4K_HDR10.mkv_zps3idwgjzf.png)

[Johnzilver]

MadVR tends to crash when playing a HEVC video, using D3D11 (native / copy-back).
This does not happen using EVR.

Crash report: https://mega.nz/#!Ew8ymaqA!cq0nTDN6M5dkIWKVAyfHuXxNRADn5Fsy36k6ePHSaZM

PC specs:
Windows 10 CU X64
Intel Core i5-4210U / Intel HD 4400

MadVR 0.92.3
LavFilters 0.70.2.74

[Dreamland]

freeze videos (all formats) and player when this is in pause and after, move the seekbar when using D3D11.Works perfectly with native / copy-back

MadVR 0.92.3
LavFilters 0.70.2.74
MPC-BE x64 v 1.5.1 built 2939
Graphic Card R9380
Windows 10 CU X64

[Manni]

Yes, this works fine for me.
screenshot (http://i1222.photobucket.com/albums/dd496/asmodian3/The_World_in_HDR_in_4K_HDR10.mkv_zps3idwgjzf.png)

Is the display native bit depth set to 10 or more so that you display HDR10 properly at less than 50/60p?
Is MadVR HDR set to passthrough and sending metadata?

It might be display specific otherwise, but still it's only with MadVR.

Also if I launch Teamviewer from another PC, the HTPC output seems fine (no magenta), so the internal composition is not corrupted, it's the GPU output that is wrong at 4K60p RGB 8bits (only).

[huhn]

http://www.mediafire.com/file/c3tt98krd2899en/settings.rar

d3d11 is not enabled in the 1080p profile.

[Asmodian]

Is the display native bit depth set to 10 or more so that you display HDR10 properly at less than 50/60p?
Is MadVR HDR set to passthrough and sending metadata?

It might be display specific otherwise, but still it's only with MadVR.

Also if I launch Teamviewer from another PC, the HTPC output seems fine (no magenta), so the internal composition is not corrupted, it's the GPU output that is wrong at 4K60p RGB 8bits (only).

Yes, madVR is set to passthrough and sending metadata. My TV switches to HDR10 mode and everything looks correct. My GPU is outputting 4K60p 8-bit RGB full but the bit depth field is blank because I have 12-bit RGB enabled at lower refresh rates.

Your TV may be assuming a higher bit depth when in HDR mode but is only receiving 8-bit so looks really weird. I had a similar issue when I was able to force Mass Effect Andromeda to enable Dolby Vision while only outputting 8-bit RGB. My TV is fine with 8-bit input for HDR10 but not Dolby Vision.

In all your other working tests with 4K60p does your display ever enable its HDR mode?

[Manni]

Yes, madVR is set to passthrough and sending metadata. My TV switches to HDR10 mode and everything looks correct. My GPU is outputting 4K60p 8-bit RGB full but the bit depth field is blank because I have 12-bit RGB enabled at lower refresh rates.

Your TV may be assuming a higher bit depth when in HDR mode but is only receiving 8-bit so looks really weird. I had a similar issue when I was able to force Mass Effect Andromeda to enable Dolby Vision while only outputting 8-bit RGB. My TV is fine with 8-bit input for HDR10 but not Dolby Vision.

In all your other working tests with 4K60p does your display ever enable its HDR mode?


As I said, my projector displays 4K60p HDR 8bits fine with the UB900. There is nothing wrong with the projector. This problem only occurs with MadVR.

As I also said, I switch to HDR manually on the display (I disable the manufacturer's mode because it's poor and I apply my own BT2020/ST2084 calibration), so it's not "expecting" anything. As far as it's concerned, it's receiving SDR. And this works fine with everything except 4K60p 8bits from MadVR.

I have tried to force the GPU to 8bits as I also reported, so that the bit depth isn't blank, and that doesn't make any difference. It is definitely 8bits that comes out in both cases, and the display interprets it as 8bits.

The issue occurs when MadVR is passing through HDR, but the display doesn't know/care whether it's SDR or HDR. There is no metadata sent to the display anyway, so that it doesn't switch to HDR automatically and applies its buggy implementation.

So we can safely take the display's HDR out of the equation.

I think MadVR does something in that case that corrupts the picture. It's not an SDR/HDR, full/limited, RGB/YCC, or a wrong calibration issue. It's a completely corrupted picture over the whole desktop, not only the player's window (the two only colors are magenta and black).

[mzso]

I wish madVR wouldn't hang every program I use it with. But that's too much to wish for.

Both ProgDVB and Potplayer hang regularly.

[Manni]

I wish madVR wouldn't hang every program I use it with. But that's too much to wish for.

Both ProgDVB and Potplayer hang regularly.

Have you tried MPC-BE? I use the x64 version for LAV/MPC-BE/MadVR and it NEVER hangs.

[Siso]

Is it good to use anti-bloating filter (100%) on image downscaling?

http://imgbox.com/YKDfHkUw

[Manni]

Yes, madVR is set to passthrough and sending metadata. My TV switches to HDR10 mode and everything looks correct. My GPU is outputting 4K60p 8-bit RGB full but the bit depth field is blank because I have 12-bit RGB enabled at lower refresh rates.

Your TV may be assuming a higher bit depth when in HDR mode but is only receiving 8-bit so looks really weird. I had a similar issue when I was able to force Mass Effect Andromeda to enable Dolby Vision while only outputting 8-bit RGB. My TV is fine with 8-bit input for HDR10 but not Dolby Vision.

In all your other working tests with 4K60p does your display ever enable its HDR mode?

Again, it's not the display, HDR works fine in all modes at all refresh rates with the UB900, so it's not the display or the AVR or anything in between.

However it's not MadVR, I tried to switch HDR on manually in the Win10 display setting and I have the same issue.

So I guess it must be an nVidia driver issue. Which driver version are you using? I reverted to .28 as .41 had issues with 12bits in custom modes, maybe that's the difference. Also what's your OS?

[Manni]

Re above, I tried 385.69 released today, it doesn't make any difference re the 4K60p8bits issue and 12bits is still not selectable for custom modes, so I'm reverting back to 385.28

[dvd1]

d3d11 is not enabled in the 1080p profile.
I have enabled it, but when the movie starts at 1080p .D3D11 disables itself, why?

[nevcairiel]

Including "rendering -> general settings" in profiles is really not recommended, as it can result in odd behavior all around.

[huhn]

and it is not check in rendering for 1080p

[Asmodian]

So I guess it must be an nVidia driver issue. Which driver version are you using? I reverted to .28 as .41 had issues with 12bits in custom modes, maybe that's the difference. Also what's your OS?

I am using 385.41 and Windows 10 1703, 15063.608.

You are sure the UB900 can output 4k60 8-bit RGB with HDR signals? The manual talks about them separately all the time, e.g. "4K/60p (4:4:4) and HDR signals that meet Ultra HD Blu-ray standards". It would surprise me, I expected it to use >8-bit for HDR content (switching to 4:2:2 to enable 60p at >8-bit). It would be great news though, I was worried Dolby Vision on my TV wouldn't work correctly if given 8-bit 4K60p but if it is a GPU driver issue instead there is still hope. :)

[Klaus1189]

I'm trying to let madvr measure video playback. But it is still displaying "not measured yet" in this video mode. I followed the four steps. What am I doing wrong?

[Manni]

I am using 385.41 and Windows 10 1703, 15063.608.

You are sure the UB900 can output 4k60 8-bit RGB with HDR signals? The manual talks about them separately all the time, e.g. "4K/60p (4:4:4) and HDR signals that meet Ultra HD Blu-ray standards". It would surprise me, I expected it to use >8-bit for HDR content (switching to 4:2:2 to enable 60p at >8-bit). It would be great news though, I was worried Dolby Vision on my TV wouldn't work correctly if given 8-bit 4K60p but if it is a GPU driver issue instead there is still hope. :)

Thanks for the OS and driver version, we have the same Windows build.
I don't think .41 will be any different to .69 or .28 regarding this so I'm staying with .28.

I am 100% sure that the UB900 can display HDR signals in 4K60p RGB 8bits, I just double checked with Billy Lynn (all confirmed with the Vertex).

If you set the UB900 to RGB, it has to go to 8bits at 4K60p because it can't use 4:2:2 (RGB is always 4:4:4).

I normally use YCB 4:4:4 12bits because then the UB900 switches automatically to 4:2:2 and keeps 12bits at 60p, which is preferable (no banding).

So it's 100% an OS/GPU issue, it's not the display or the AVR or anything in between.

However as it's not a MadVR issue I'll stop posting about it so as not to clutter the thread, feel free to PM me if you'd like to discuss this further.

[AngelGraves13]

It would be great if madvr had a setting to "let madvr decide" for Chroma upscaling, if you happen to play a file and it begins dropping frames or losing sync, to lower the setting until it stops. Not very useful for me, but I can't use certain settings with 4K files like NGU Very High.

[dvd1]

https://s26.postimg.org/9ml1a2lvd/Catturaefe5.png (https://postimages.org/)
it is now active

https://s26.postimg.org/enx0p6ipl/Catturazdffgrr.png (https://postimages.org/)

starting a 1080p disables D3D11 and the 1080p always starts in D3D9

[Asmodian]

Re-create all your profiles without "general settings" in them.

[dvd1]

https://s26.postimg.org/a755xexx5/Catturaolj.png (https://postimages.org/)

done but now it all goes to D3D9
did I do something wrong?

[Asmodian]

No, that is fine. Maybe you need to reset to default settings first?

Very odd, sorry. :(

[steakhutzeee]

So, i've:

Chroma Upscaling -> NGU Sharp, medium. No SuperRes (MadVr stops me only if i use NGU and SuperRes from the upscaling refinement, but'll follow your suggestion).

Image Downscaling -> SSIM 1D 100%, No in linear light, Yes anti-ringing relaxed, and Yes anti-bloating 100%. What's difference with 2D? What i should use?

Image Upscaling -> NGU Sharp, High for luma doubling, all the others are let madVR decide.

Upscaling Refinement -> I've sharpen edges and enhance detail because as i can see, the first sharpens only the edges, the second sharpens the texture etc. I need them? I've enabled crispen edges, but it's another sharpener. So i need it? Disabled soften edges.
Enabled LumaSharpen 0.65, to avoid sharpen artifacts.
Enabled AdaptiveSharpen 0.5, to avoids sharpening near flat areas and very sharp edges. (Asmodian guide).
No SuperRes, and checked refine image after every 2x upscaling step.

Thanks in advance. :)

[Klaus1189]

I'm trying to let madvr measure video playback. But it is still displaying "not measured yet" in this video mode. I followed the four steps. What am I doing wrong?

So I don‘t get optimization data. What could prevent this?

[nussman]

What do you think? Did you test your settings? I dont think Lumasharpen and AdaptiveSharpen helps for most content but there is no "best" setting for videoprocessing. Test it and if you like it everything is fine ...

[Asmodian]

Image Downscaling -> SSIM 1D 100%, No in linear light, Yes anti-ringing relaxed, and Yes anti-bloating 100%. What's difference with 2D? What i should use?

2D is an even stronger version of SSIM (more detail preserved and/or sharper) but it is perhaps too strong and it takes A LOT more GPU power.

You do not need any Upscaling Refinement options. I only use them for particular sources that are unusually soft or have some other reason to want them. By default I have them all disabled.

AdaptiveSharpen works by sharpening that way, it does not affect the other sharpeners at all.

Enabling them all is a bad idea, I have never found them to be useful all at once. Some sources like sharpening with crispen edges while others look better with sharpen edges or adaptive sharpen, they all have their place and sometimes a few look good together but just using them all by default is not good.

So I don‘t get optimization data. What could prevent this?

Usually this is because your GPU driver is not actually switching to the correct custom mode. Try having madVR do the switch instead of using the control panel, or vice-versa if you are already having madVR do the switch. :p

[steakhutzeee]

2D is an even stronger version of SSIM (more detail preserved and/or sharper) but it is perhaps too strong and it takes A LOT more GPU power.

You do not need any Upscaling Refinement options. I only use them for particular sources that are unusually soft or have some other reason to want them. By default I have them all disabled.

AdaptiveSharpen works by sharpening that way, it does not affect the other sharpeners at all.

Enabling them all is a bad idea, I have never found them to be useful all at once. Some sources like sharpening with crispen edges while others look better with sharpen edges or adaptive sharpen, they all have their place and sometimes a few look good together but just using them all by default is not good.



Usually this is because your GPU driver is not actually switching to the correct custom mode. Try having madVR do the switch instead of using the control panel, or vice-versa if you are already having madVR do the switch. :pThanks :) So l've disabled all the upscaling refinement. Btw, I just seen a movie and with my previous settings it was looking great XD. Now, I know what the settings do thanks to your guide, but how I can go deeper, to know when a source need one of them?

Inviato dal mio ASUS_Z00LD utilizzando Tapatalk

[Asmodian]

Now, I know what the settings do thanks to your guide, but how I can go deeper, to know when a source need one of them?

Pure looking at the video with and without them. There are no correct answers, only what looks good to you. :)

[Fabulist]

Hello madshi and thank you for your amazing work.

I would like to ask your opinion regarding color spaces and depth on a matter that has haunted me for awhile now:

If all sources are 8-bit (rarely 10-bit) 1080p YCbCr 4:2:0 and I have madVR scaling chroma with NGU Sharp very high quality, would it be better to have the TV (also 1080p) set to (through NVIDIA's Control Panel):

a) 8-bit or 10-bit or 12-bit (Deep Color) YCbCr 4:2:2 (Pure Direct* greyed out / off)
b) 8-bit YCbCr 4:4:4 (Pure Direct* can be used)
c) 8-bit RGB (Pure Direct* can be used)

*I am confused as to what Pure Direct does exactly, it should in theory allow for a less altered signal assuming it is RGB or YCbCr 4:4:4. It is not allowed in YCbCr 4:2:2 at any bit-depth, although I doubt it makes any difference considering the source's quality and madVR functionality.

I am receiving consistently different answers from various sources including my own research - but I assumed that you would know what is best in combination with madVR.

Does it even matter assuming the conditions mentioned above? What do you think is correct?

[bcec]

I just got around playing around with new custom timings, but these timings are engaged only when D3D11 windowed mode (8-bit). When D3D11 full screen exclusive (10-bit) enabled, custom modes are not engaged. Any ideas?

EDIT: I disabled D3D11 FSE, and instead using D3D11 windowed mode (10-bit), and custom modes are engaged now.

[Asmodian]

a) 8-bit or 10-bit or 12-bit (Deep Color) YCbCr 4:2:2 (Pure Direct* greyed out / off)
b) 8-bit YCbCr 4:4:4 (Pure Direct* can be used)
c) 8-bit RGB (Pure Direct* can be used)


This has a well understood and non-controversial answer, at least in this thread. ;)

Given those options it is always c) 8-bit RGB, even with high bit depth sources.

a) YCbCr 4:2:2 is particularly bad; madVR outputs RGB and you don't want the GPU downscaling your chroma to half the horizontal resolution! That loses 1/3 of the video information and with good dithering the bit depth is significantly less important than spatial resolution. Chroma upscaling with NGU Sharp very high is rather pointless if you then downscale it again with bilinear. :p

b) YCbCr 4:4:4 would be better than 4:2:2, but there is no reason to have the GPU do an extra conversion. Video data must be RGB for humans to view it as a color image so this is always the final format, if madVR does the conversion, the display does, or something inbetween.

Where do you see "Pure Direct"? It sounds good, you don't want any extra processing.