madVR 10-bit Display Support Test

[chros]

1. Could you explain what you mean by "panel string"?
2. Panasonic PR65VT60.
I was curious whether it has a 10bit panel (or 8+FRC) but it seems it has. The last idea: is "DeepColorHDMIDisable" is "0" in registry? (as it should by default) (You can check the valid path to this reg entry with the help of madleveltweaker.exe, after you drag it to the proper display.)

[rivera]

is "DeepColorHDMIDisable" is "0" in registry? (as it should by default)
Yes, it is 0

[huhn]

I was curious whether it has a 10bit panel (or 8+FRC) but it seems it has. The last idea: is "DeepColorHDMIDisable" is "0" in registry? (as it should by default) (You can check the valid path to this reg entry with the help of madleveltweaker.exe, after you drag it to the proper display.)

it's a plasma is doesn't have a real bit deep...

[chros]

Yes, it is 0

it's a plasma is doesn't have a real bit deep...

Then I'm out of ideas :(

[rivera]

Then I'm out of ideas :(
May be it works, I do not know for sure:1. When I open .png file in MPC-HC there is a text in madVR OSD "fullscreen exclusive (10 bit)".
From 2.5 m from the TV screen I can see vertical stripes (about 3..5 mm width).
Same stripes I can see if "automatic exclusive fullscreen mode (FSE)-> off".
Seems there is no difference?

[chros]

May be it works, I do not know for sure:
You could easily tell the difference so probably it means it doesn't work.
But this 10bit output is negligible compared to be able to get full 4:4:4 chroma output (which I can't get at all :( ).

[rivera]

You could easily tell the difference so probably it means it doesn't workMay be Intel Graphics 530 doesn't support 10 bit output?
Actually, there is no any info (positive or negative) for this on intel.com

[chros]

May be Intel Graphics 530 doesn't support 10 bit output?
Actually, there is no any info (positive or negative) for this on intel.com
I'm pretty sure it does unless something is broken in the driver. As we mentioned it's (>=10bit output) called Deep Color (it's available since HDMI v1.3) and there was also a registry entry for it in your reg.
https://en.wikipedia.org/wiki/Color_depth#Deep_color_.2830.2F36.2F48-bit.29

[James Freeman]

Just wanted to say that dithered 8bit looks like 12bit to the i1 Display Pro colorimeter.
If you don't see the pixels then it should looks like 12bit to your eye too.

Professional video editing software like Adobe After Effects dithers automatically the 32bit Floating workflow to 8bit at export if you choose 8bit.
The 16bit PNG test pattern looks smooth as silk when exported from AE in 8bit just like in madVR, although AE uses your typical Random Dithering like the similar setting in madVR.

[James Freeman]

BTW I can set my Dell 2410 to 10bit in Nvidia CPL, when I use display port, and indeed there is no banding when dithering is Off with the OP test.
But is the GTX series actually sending 10bit to the panel or it dithers to 8bit? Anyone actually found out?

EDIT:
After some testing, I found that the GTX dithers down to 8bit no matter what.

[James Freeman]

Panasonic ST60 summery:
MadVR: No Dithering, PC Levels, 16bit Grey Ramp PNG.
DX11, Exclusive, 8bit or 10bit.

Banding = How the TV processes the image.
Steps = How the 16bit PNG looks without dithering in madVR (it should look like steps in 8bit w/o dithering, and smooth in 10bit w/o dithering).

YCbCr 4:4:4 8bit (always limited):
8bit = No Banding, Steps.
10bit = No Banding, Smooth (nvidia dithering).

YCbCr 4:4:4 12bit (always limited):
8bit = Banding, Steps.
10bit = Banding, Steps (nvidia quantizes it to 8bit).

RGB 8bit (Full):
8bit = Banding, Steps.
10bit = Banding, Smooth.

RGB 8bit (Limited):
8bit = Slight Banding, Steps.
10bit = Slight Banding, Smooth.

RGB 12bit (Full):
8bit = Banding, Steps.
10bit = Banding, Steps (nvidia quantizes it to 8bit).

RGB 12bit (Limited):
8bit = Banding, Steps.
10bit = Banding, Steps (nvidia quantizes it to 8bit).

Clear Winner: YCbCr 4:4:4 8bit NV-CPL, 8bit + Dithering in madVR.
TVs are made for YCbCr and it's where the best processing will probably be.

As you can see, only in YCbCr 4:4:4 8bit the ST60 doesn't generate banding.
You have a choice to get smooth steps, 10bit in madVR but nvidia will dither down to 8bit (unknown method of dithering), OR, 8bit in madVR + Dithering where Nvidia will not dither.
In a word, 10bit from madVR = Nivida dithering down to 8bit.
If nvidia dithers in 60fps then it will be better than madVR, if it is static, worse than madVR; but I have no means to verify that.

Only in 8bit (NV CPL) the 10bit in madVR is Smooth, so nvidia MUST be dithering from 10bit to 8bit when you set 8bit in CPL.
When in 12bit (NV CPL), 10bit in madVR is truncated/quantized to 8bit for some reason and it is always has steps.

[huhn]

BTW I can set my Dell 2410 to 10bit in Nvidia CPL, when I use display port, and indeed there is no banding when dithering is Off with the OP test.
But is the GTX series actually sending 10bit to the panel or it dithers to 8bit? Anyone actually found out?

EDIT:
After some testing, I found that the GTX dithers down to 8bit no matter what.

with amd i made 100 % sure the screen gets 10 bit.

thanks to the disable dither option.

i don't see a reason nvidia should dither down to 8 bit and still send a 12 bit signal.

in the past nvidia was sending 12 bit no matter what option was used in the CP as long as 10 bit was outputted to the driver. but i did this test nearly a year ago.

some screens can confirm what type of signal they get. so sending 12 bit but only using 8 is very unlikely.

to me it sounds like the Panasonic ST60 has broken/bad processing with high bit deep signals and that's it. the fact it shows banding with RGB 8 bit full range is a very clear indicator.

after a RGB -> YCbCr you have to dither too. YCbCr is always limited and even without that you have to dither.

[nevcairiel]

Panasonic ST60 summery:

Plasma TVs are not a very good reference for bitdepth measurements, as they are practically low bitdepth screens with temporal dithering.

[James Freeman]

I don't see a reason nvidia should dither down to 8 bit and still send a 12 bit signal.
To me it sounds like the Panasonic ST60 has broken/bad processing with high bit deep signals and that's it. the fact it shows banding with RGB 8 bit full range is a very clear indicator.
After a RGB -> YCbCr you have to dither too. YCbCr is always limited and even without that you have to dither.
Indeed, the ST60 has terrible processing in 12bit, and not the best in RGB.
The question remains whether nvidia dithers down to 8bit (as set in NV CPL) when a higher bitdepth signal is received like 10bit from madVR.
Still, nvidia's dithering is not bad at all, looks smooth, dithered 8bit can look as good as 12bit as I mentioned in the last post.
The process of RGB Full -> YCbCr 4:4:4 Limited has to be dithered alright, but it is in imperceptible.
As for 12bit NV-CPL and 10bit madVR = steps, only Jen-Hsun Huang knows what is going on in there....maybe.

Plasma TVs are not a very good reference for bitdepth measurements, as they are practically low bitdepth screens with temporal dithering.
Right, but the 8bit steps are still visible even on the plasma, so I can at least see if the input signal is smooth whether it is dithered or true high bitdepth.

[huhn]

Indeed, the ST60 has terrible processing in 12bit, and not the best in RGB.
The question remains whether nvidia dithers down to 8bit (as set in NV CPL) when a higher bitdepth signal is received like 10bit from madVR.
Still, nvidia's dithering is not bad at all, looks smooth, dithered 8bit can look as good as 12bit as I mentioned in the last post.

my old screen and my current screen don't show banding with 12 bit output.

the fact that your screen is showing banding with it and mine not is a indicator that nvidia isn't dithering down.

i tested my old screen with an AMD card with disabled dithering in the reg and with 10 bit output it wasn't showing banding so the screen was properly dithering down to 8 bit.

i'm kind of missing this totally flawless processing of my old very cheap Philips. it is so much better at this than my new screen...

so i say nvidia can send 10 bit worth of data to a screen.

[James Freeman]

You understand my difference between Banding and Steps right?
Banding = How the TV processes the image no matter how smooth it is (can look very smooth yet have banding).
Steps (gradations) = How the 16bit PNG looks without dithering in madVR (it should look like steps in 8bit w/o dithering, and smooth in 10bit w/o dithering).

The Banding on the ST60 is not like Steps, it is much more subtle, like slight color shifts in the smooth geryscale.
Here is a smooth madVR 8bit+Dither greyscale on the ST60 in YCbCr 4:4:4 8/12 bit HDMI.

The ST60 has worse banding in 12bit and in Full range.
RGB 8bit Limited has slightly worse banding than YCbCr 8bit, but not as bad as any mode in 12bit.
The ST60 prefers Limited to Full, 8bit to 12bit, YCbCr to RGB.
So YCbCr 8bit for the smoothest image on the ST60.

Have fun.

http://www.mediafire.com/convkey/8a18/9jlgclfe8rredmbzg.jpg
http://www.mediafire.com/convkey/ede1/b288i8wntw24si9zg.jpg

[huhn]

both screen show banding to me. (could be the camera i mean it is super noisy)

the second one is just terrible.

if you want to difference them fine by me.
i don't difference between both they are both banding to me.

[James Freeman]

Yes, camera is shit, TVs blacks are very dark.
The first one has no banding in real REALITY.
This information is for Panasonic plasma owners anyway.

[James Freeman]

Something really fishy going on with nvidia in higher bit depths.

This time with my trusty old Dell2410 10bit (8+FRC) monitor, I can select 8 or 10 bit in NV-CPL.
I disabled dithering in madVR, Video Frame (Double) and brightness to -100 in MPC-HC, and zoomed (numpad 6) and moved to the farthest left (Ctrl+Numpad 6), to clearly see the 10bit gradations (4 times as narrower).
I also had to turn the backlight to max on the monitor to see anything.
Screenshots were taken with 8 second exposure, ISO 64 for lowest noise, with my crap camera, in a completely dark room.

When nvidia control panel set to higher bit depth like 10bit (DP) or 12bit (HDMI), and madVR sends 10bit picture in exclusive mode, the result is terrible banding.

EDIT:
It might be the proof that nvidia does NOT dither when a higher bit depth is selected in NV-CPL, but simply maps it in 8bit no matter the settings in NV-CPL.
This is the worst thing that can be done when going from higher to lower bitdepth.

If set MPC-HC Brightness back to 0, the un-even gradations in "10bit NV-CPL, 10bit madVR", become even because the steps are equally divided to 4.
But if I set NV-CPL to 8bit they are always even, no matter if the brightness is manipulated and dithering is disabled in madVR, because nvidia dithers to 8bit when a higher bitdepth signal is received.

My guess is:
MadVR outputs true 10bit (no dithering) and relies on the next in chain to properly map the 10bit signal.
Nvidia receives this true 10bit signal and Dithers it to 8 bit, if 8bit is selected in NV-CPL.

But when Nvidia is set to higher bit depth (10 or 12) it just maps the received 10bit signal to 8bit without dithering therefor banding.
OR (second theory), the 10bit values madVR sends (DirectX 11 actually) mismatch the values nvidia expects, therefor maps 10bit to 10bit with slight mathematical error.

8bit NV-CPL, 8bit madVR:
http://www.mediafire.com/convkey/5d24/575leva3587o8clzg.jpg

8bit NV-CPL, 10bit madVR:
All OK as it should be, each 8bit step is now 4 steps.
Even gradations, I assume nvidia dithers down to 8bit.
http://www.mediafire.com/convkey/1c2c/w7fcqywahuzjn5kzg.jpg

10bit NV-CPL, 8bit madVR:
Same as 8bit NV-CPL, 8bit madVR.
http://www.mediafire.com/convkey/dab7/yjfg1liivbbvlqczg.jpg

10bit NV-CPL, 10bit madVR:
What is this? The gradations are not equal.
http://www.mediafire.com/convkey/a5e0/fedwr5om3ldxueuzg.jpg

[huhn]

i can test my cx700 again but the last time i did it it was smooth with 10 bit input.

if this is your screen it is just 8 bit. it has 10 bit processing. i didn't find a word about FRC.

http://www.tftcentral.co.uk/reviews/dell_u2410.htm

and i mean which LCD TV doesn't do 8 bit plus FRC these days?

[James Freeman]

Yes practically all displays have high bitdepth internal processing, but do not accept higher than 8bit input.
The Dell U2410 can actually accept 10bit input and show it. It's a wide gamut 10bit input monitor for color grading.
It's all dependent on the capability of the video card. The monitor can support 10bit colour via A-FRC dithering. If you get a graphics card capable of 10bit colour output and use the DisplayPort input on the U2410, the U2410 is capable of supporting and rendering (via dithering) 10bit colour values.

That is not the point.

The gradations I speak of have nothing to do with the display, but with Nvidia high bit depth output processing.
Apparently there is some mathematical error that causes banding if higher bit depths are selected in NV-CPL.

Please do test with your CX700 exactly as I explained.

[nevcairiel]

FRC is temporal dithering, so taking a single photo of something that changes over time may not do it justice. Its definitely more than 8-bit, but not quite the full 10-bit either way.
Your testing jumps to conclusions based on assumptions way to quickly.

[James Freeman]

8 seconds of exposure time is enough to eliminate all 1/60[s] changes don't you think?
I don't need the camera either, it's what I see with my own eyes.

Understand that it's nvidia that sends the 10bit signal to the display.
If the internal processing of nvidia has an error then that's what the display will show.
Besides, the gradients are HUGE in this test so the display is out of the question, it's something in the video card processing or driver.

I would be happy if someone could repeat my experiment with 10 or 12 bit settings in NV-CPL.

[huhn]

could be as simple as this:

the screen is doing processing in 10 bit. with some gamma correction is is already adding a lot of error in the image but the frame buffer is just 10 bit so some of the steps are gone even with dithering to 8 bit now.

with other words how can you show 10 steps with just 10 bit processing?

[James Freeman]

You might be right huhn.

[nevcairiel]

I just did, as I have a U2410 myself, using similar zoom setting as you (same zoom, slightly different position as it didnt want to move anymore).
I don't have any camera other than my phone, and thats not worth taking any image with.

At -100 brightness, in most areas of the screen I can see the small bars (1/4 of the 8-bit bars), in some others its pretty hard to make out all the bars as some "melt" together, which could just be the screen not being perfectly uniform, or the FRC dithering.
Of course this is all irrelevant when I turn on dithering in madVR, since the input is 16-bit, and even at 10-bit output it becomes perfectly smooth then. NVIDIA or the screen definitely do not introduce any new banding even when fed with 10-bit from madVR. So not sure what we're actually trying to proof now.

[James Freeman]

I tried to figure 2 things:

1. Whether nvidia dither in high bit depths, which clearly shows it does not if a lower or equal bitdepth is sent.
2. Whether the gradations I see with my Dell U2410 in 10bit NV and 10bit madVR, are from the Monitor or from Nvidia.

MadVR will output a perfectly smooth 10bit gradations with any processing applied on the 16bit pattern like -100 brightness with dithering disabled.
I think huhn is right and the old U2410 has only 10bit internal processing therefor has variable thickness banding even in 8bit.

I may jumped too early to conclusions, shoving nvidias head in the dirt... :D

[huhn]

8bit NV-CPL, 10bit madVR:
All OK as it should be, each 8bit step is now 4 steps.
Even gradations, I assume nvidia dithers down to 8bit.

if you ask me this looks like a perfect job from "nvidia".

nvidia doesn't need to use high bit deepo here if it doesn't touch the image with anything else than dither.

it is just doing 10 to 8 there is no need for high bit deep processing.

[James Freeman]

if you ask me this looks like a perfect job from "nvidia".
nvidia doesn't need to use high bit deepo here if it doesn't touch the image with anything else than dither.
it is just doing 10 to 8 there is no need for high bit deep processing.

Actually they DO dither down to 8bit, they are not that lazy.
I just tested it with my camera and they have 3 more shades of black between 0 and 1 out of 255 in 10bit.
And it's not switching my monitor to 10bit because it respects the NV-CPL setting of 8bit.
Furthermore, dithered 10bit to 8bit (by nvidia) looks much better on the U2410 than true 10bit to 10bit because the U2410 maps 10bit un-evenly.

So when a higher bit depth input like 10 bit from madVR (undithered) and 8bit in NV-CPL output, the result is similar to true 10bit because nvidia has nice down dithering.
But nvidia will not dither if the same bit depth is at the input as at the output, or lower input obviously.

I also learned today from huhn that the internal processing bitdepth of the display HAS to be higher than the highest input bitdepth the display supports, for the gradients to be smooth and equal.
The U2410 has 12bit processing (HERE (http://www.dell.com/ed/business/p/dell-u2410/pd)), bus still generates banding in 10bit input.

[BluesFanUK]

Is there even much of a difference between 8 bit and 10 bit? I've just bought the Dell Ultrasharp U2515H (True 8 bit) and have a 980ti. MadVR for some reason allows you to select 10 bit in the control panel then it shows as 10 bit on screen. Surely it should be detected from the GPU direct?

Is there a difference between 8 bit and 10 bit (8 bit + dithering)? Sorry if i'm being dense, but I couldn't notice a difference on my old Acer 4K S277HK (8 bit + dithering).

[chros]

Is there even much of a difference between 8 bit and 10 bit? I've just bought the Dell Ultrasharp U2515H (True 8 bit) and have a 980ti. MadVR for some reason allows you to select 10 bit in the control panel then it shows as 10 bit on screen. Surely it should be detected from the GPU direct?
How? :) There's no reliable way to do that. That's why you have to experiment yourself.
Is there a difference between 8 bit and 10 bit (8 bit + dithering)? Sorry if i'm being dense, but I couldn't notice a difference on my old Acer 4K S277HK (8 bit + dithering).
Visual quality wise: good question. If you don't see then it doesn't matter :) (I can't really see it either but I'm using it.)
Performance wise: definitely! 10 bit needs more bandwidth (especially when frame rate rises) than 8 bit. So this can be another reason to use 8 bit if your display doesn't support it!

[kolak]

Difference is quite small. If you use good dithering than it's hard to see.
I've done tests on pro equipment (Sony OLED reference monitors) and you really need to be looking for it (and have real 10bit next to it) to see the difference. It all depends on the footage, but on the real world sample with home viewing conditions it's not so obvious.

[rivera]

Regarding RGB48 checkbox in MPC-HC settings.
Shall I leave only this checkbox checked and rest of other ones - unchecked?

[aufkrawall]

You should enable all checkboxes to let madVR do the RGB conversion instead of LAV Filters.

[rivera]

You should enable all checkboxes to let madVR do the RGB conversion instead of LAV Filters.
Sorry, I can't see a logic.
How these checkboxes in LAV filter's settings are connected to madVR ?

[Asmodian]

Sorry, I can't see a logic.
How these checkboxes in LAV filter's settings are connected to madVR ?

Those control what LAV is allowed to send to madVR.

[rivera]

Those control what LAV is allowed to send to madVR.
So, if I select only RGB48 then doesn't that mean that only 16bit color will be used?

I have Nvidia GTX960 card.
In Nvidia Control Panel "12bit" color output is selected.
TV is Panasonic PR65VT60 plasma (10bit panel).

So, just in case I decided to permit only RGB48 output in MPC-HC.
In case of 1080p videos everything runs smooth.
But in case of 2160p videos (some test clips) no drops too, but it runs very slow (0..2 frames in a queue).
If not only RGB48 is selected (i.e RGB24, RGB32 are selected too) then 2160p videos run smooth.
So I wonder why these stuttering occurred.

[CruNcher]

Did anyone here looked deeper into the G-sync Module apart from the Variable V blank but more in the matter of the Scaling unit and FRC and into the possibility that they maybe temporarily interpolate frames on the fly gathered from the Sync Data with a G-sync Panel ?

and maybe even interpolate from a cheap 60 FPS Panel 120 and 144 HZ Signal results that their customers then sell as "real" 120 and 144 HZ Gamer Displays ?

[Asmodian]

Did anyone here looked deeper into the G-sync Module apart from the Variable V blank but more in the matter of the Scaling unit and FRC and into the possibility that they maybe temporarily interpolate frames on the fly gathered from the Sync Data with a G-sync Panel ?

and maybe even interpolate from a cheap 60 FPS Panel 120 and 144 HZ Signal results that their customers then sell as "real" 120 and 144 HZ Gamer Displays ?

FRC? The G-sync module doesn't do frame rate conversations, except for doubling frames when needed. You think it might be blending 144 Hz signals into a 60 Hz one to drive the panel? That seems far fetched. They also do not have a scaling unit.

It really does not seem like that is happening and TFTCentral's testing with high speed chase cams would surely show it.

There is a problem with frame "blending" but it is due to slow response times. On VA panels real response times can easily be 10ms or even higher so the panel is never fully caught up, the new frame comes before the pixels have fully set for the last one.

Why in the 10-bit thread? Even the newest G-sync modules will only accept 8-bit input, won't they?

[CruNcher]

I doubt they will stay at 8 bit with HDR incoming but yeah most probably to far fetched though i wondered if the Size of the FPGA Framebuffer could be enough if Nvidias DCC would be running on it additionally
Also seeing that Sony is doing the same in their driver box for the PSVR taking the 60 Hz input and FRC a 120 result and for VR it needs to be absolutely stable there you would be realizing motion misspredicitions pretty much instantly faster then you ever would on a Desktop Display.

[iSeries]

Hi,

For some reason I can't see 10bit in nvidia driver control panel (GTX950), only 8bit and 12bit. What happens if I set the driver to 12bit and have Madvr output 10bit? Does the driver just pad the signal with zeroes to 12bit, or does it do something undesirable? Also would anyone have an idea why I can't see 10bit in the driver? I could on my previous AMD card, with the same TV.

[huhn]

nvidia doesn't expose a 10 bit option if 12 bit is possible.

just hope it is padding no one knows this for sure what nvidia is doing.

[Spc.]

Hi everyone.
I have Dell U2410 monitor which supports 10bpc input, it has 8bit+FRC panel and i wanted to test 10bit input if it makes a difference in picture quality using method this thread mentions.

My Hardware:
Dell U2410
AMD RADEON PowerColor TurboDuo R9 280X 3GB GDDR5 OC (Tahiti)
16GB RAM
Core i7-3930k @ 4.4GHz
Windows Server 2016 Datacenter (MSDN)

Here's a test i made:

R9 280X (Tahiti) 6bpc > DisplayPort > U2410 (262144 Colors) (18 bits):
http://www.netsky.org/10bpc/6bpcamdeng.png

R9 280X (Tahiti) 8bpc > DisplayPort > U2410 (16777216 Colors) (24bits):
http://www.netsky.org/10bpc/8bpcamdeng.png

R9 280X (Tahiti) 10bpc > DisplayPort > U2410 (1073741824 Colors) (30bits):
http://www.netsky.org/10bpc/10bpcamdeng.png

I used Canon EOS 7D Mark II with EF 24-105mm L IS USM Lens (48bit RAW Files) to test image quality tests on my monitor.
As you can see image quality between 8bit and 8bit+FRC is huge.

** If you're viewing pictures in FireFox let me tell you that FireFox has a problem rendering 48bit png files, because it assumes all pictures on the web are sRGB so FireFox does read embeded ICC Color profile so you will see upper blue line as purple line, use google chrome to get exact colors, i hope FireFox fixes this bug soon. :(


I also wanted to test HDMI port on my Radeon, it does the same thing, 10bpc output on HDMI port gives me the same 10bpc quality.

On nvidia cards only Display Port connection works with higher than 8bpc settings.

While with AMD cards you can choose 10bpc on HDMI and DisplayPort, nvidia cards can only output 10bpc on DisplayPort.
If you select HDMI connection to Dell U2410 nvidia does not let you choose higher than 8bpc.

Here's a picture of R9 280X using a HDMI or Display Port:
http://www.netsky.org/10bpc/DELL+Tahiti.png

Here's a picture of GTX 960 using a Display Port:
http://www.netsky.org/10bpc/MaxwellGTX960DisplayPortU2410.png

If i choose HDMI connection, 10 bpc option disappears and I only get 8bpc option (nvidia).


My conclusion:
1. 8bit+FRC does look very good when using 10bit input and difference is very big in 8/10 input.
2. AMD Cards can use HDMI (EDID 1.3) or DisplayPort (EDID 1.4) to output 10bit per channel to monitor.
3. Nvidia Cards only work with Display Port (EDID 1.4) to output 10bpc, HDMI (EDID 1.3) does not work higher than 8bpc on DELL U2410.

[huhn]

did you disable the dithering in the GPU or why is 6 bit not dithered?

[Spc.]

did you disable the dithering in the GPU or why is 6 bit not dithered?
Yes i did disable dithering in registry (AMD).

[huhn]

for a more fair comparison set the madVR bit deep to the same value as the output bit deep in the CCC (RIP BTW.).

[aufkrawall]

Do you guys already know this test video?
https://github.com/jursonovicst/gradient
Very helpful. Windows 10 video app clearly shows banding here for the 10 bit content, which is not the case with MPC HC EVR.

Handbrake automatically seems to apply dither when converting to 8 bit, so the 10 bit gradients are also banding-free then. At least when rendered by madVR and mpv (mpv however doesn't activate dithering by default), EVR struggles with the dithered 8 bit. I expect MPDN to be banding-free as well.

[Manni]

Do you guys already know this test video?
https://github.com/jursonovicst/gradient

Thanks, I didn't have this file. I had the greyscale gradient one, but this one is even better.

[copenhagenstreaming]

Now switch FSE On and go fullscreen again, now the GPU actually sends 10bit image to the display, and if your display supports 10bit input, you should now see 1024 gradients from black to white.
These gradients are 4 times narrower compared to 8bit and are practically indiscernible (to me).
In other words, you should NOT see any gradients.

After following your guide, I see no difference between 8 and 10 bit. The gradients are exactly the same. The lower bit modes are clearly distinguishable. In the nVidia control panel I have selected 12 bit, as 8 and 12 bit are the only options.

What can be the issue?

Now switch FSE

Can you outline exactly how this is done in MPC-HC?

My setup is a laptop with Geforce 1060 GTX > HDMI 2m > Denon AVR-X2600H > HDMI 7m > Epson Home Cinema 5050UB (4:4:4 up to 8-bit, 4:2:2 up to 12-bit)

Thanks a bunch!

[huhn]

you don't need FSE anymore more on windows 10.
it'S not an option in mpc-hc.