Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
8th April 2018, 14:50 | #50141 | Link | |
Registered User
Join Date: May 2011
Posts: 164
|
Quote:
On my desktop though, no difference between the 2 in rendering times (i7 8700k/1080 ti). |
|
8th April 2018, 17:34 | #50142 | Link |
Registered User
Join Date: Oct 2017
Posts: 331
|
Hi madshi. Re: Banding and your 390.65 drivers.
NVidia introduced a pretty significant Windows audio bug starting with 390.65 through the present. I don't think any of these drivers retain a 12bit setting after a reboot either. All drivers prior to 390.65 have various dynamic HDR switching problems except 385.69 and 385.28. Those two and only those two are HDR switching and Audio switching correct. They also retain a 12bit setting after a reboot, not that it matters. Nvidia does not offer an RGB 10bit setting. Only 8 or 12. So, I always selected 12bit believing it would dither down to 10bit as needed. Then I discovered banding on the UHD HDR title Allied as one example. I presented the example quirk here. After testing by a few members it was determined some displays handle 12bit better than others because they are native 12bit. They get no banding using 12bit. This leads me to believe the banding is not built in to the title. My Samsung native 10bit for example handles it poorly and introduces banding. If NVidia provided a 10bit setting I could simply use that but they don't. So, I'm required to use 8bit. The banding is no longer present. Of course we'd all like to use 10bit for 10bit sources like UHD HDR on our 10bit displays with a perfect chain but we are limited to 8bit until NVidia introduces RGB 10bit. This I don't count on. Warner quizzed an AMD user about this banding quirk suggesting he set his driver to 10bit since AMD offers RGB at 10bit. He reported no banding using 10 or 12bit. Perhaps his display is 12bit native or he really isn't looking or admitting to banding proud of his new setup? Today a user here reports AMD banding with 12bit although again we don't know if this display is native 10bit causing the banding nor results at a 10bit setting. The point is, can madVR work around NVidia's fault for not supplying RGB 10bit which affects native 10bit (not 12bit) displays? I wouldn't ask if I thought NVidia would eventually step up but the fact is, they've NEVER offered it afaik. If we could get detailed positive confirmations from AMD users who have no banding using 10bit settings and displays, then the fix could be relatively simple; Dump NVidia and concentrate on AMD or use a 12bit display. Personally, given the price gouging going on, I will continue to use what I have at 8bit and replacing my display is out of the question at this point. I read the eye is not going to discern 8bit vs 10bit anyway but I have no way of concluding that for myself. I will trust that coming from you if indeed that is your opinion. I assume many more colors within the gamut would be visible especially blends which are now bands of ugliness. We all realize you are concentrating on other things and don't expect anything anytime soon if ever. Just some ammo to consider when and if you find any of this worthy of your powers. Thank you as always for providing what you have. If you never update madVR again, it's still a brilliant software just as it is.
__________________
HOW TO-Kodi 2D-3D-UHD (4k) HDR Guide Internal & External Players W11 Pro 24H2 GTX960-4GB RGB 4:4:4 @Matched Refresh Rates 8,10,12bit KODI 22 MPC-HC/BE 82" Q90R Denon S720W Last edited by brazen1; 8th April 2018 at 17:55. |
8th April 2018, 18:55 | #50144 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
The only way to understand the difference in bit depths is to find a grayscale test pattern. Set madVR to 8-bits and 10-bits. The gradient should get smoother at 10-bits, but it doesn't. In fact, the effect of dithering at 8-bits can make the gradient look smoother than 10-bits, but with a little more noise. And this noise is difficult to notice. That is all the bit depth does; it makes things smoother, not more colorful.
There are no 12-bit flat panels (maybe projectors), but there are displays which handle 12-bit inputs more gracefully. This would depend on whether dithering is used and the quality of that dithering.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
8th April 2018, 19:03 | #50145 | Link | |||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
------- Just found out that the Nvidia GPU drivers have a bug in Windows 10 which stop 10bit from working properly in fullscreen windowed mode, but only when using HDR passthrough. Works fine without HDR passthrough. Works fine in FSE mode. The next madVR build will force 8bit in HDR fullscreen windowed mode for Nvidia GPUs. For now, to workaround this issue, either use FSE mode, or manually switch the madVR monitor settings to 8bit. |
|||
8th April 2018, 19:37 | #50146 | Link | |
Registered User
Join Date: May 2011
Posts: 164
|
Quote:
On the files I tried (DVD and blu-ray rips I made) I got an extra ~10ms rendering time from enabling subtitles alone (and have to restart the playback to reset it, hiding the subtitles isn't enough). It's hard to measure CPU usage on this laptop though, CPU clock keeps going up and down etc. But without subs, I was at 15-20% CPU usage with very low clocks, enabling subs doesn't seem to increase it by that much, maybe 5-10%. Probably just a JRiver issue with some specific hardware though (Atom x7-Z8700 in my case). On my desktop enabling subs adds maybe 0.3ms to rendering times, if that... Last edited by kalston; 9th April 2018 at 00:34. |
|
8th April 2018, 20:43 | #50147 | Link | |
Registered User
Join Date: Mar 2002
Location: Sofia, Bulgaria
Posts: 661
|
Quote:
http://www.avsforum.com/forum/139-di...terns-set.html In the "04. Colors" folder there is a file called "01. Banding_Rotating-gradients_23.976.mp4" and with it I think I found an issue ... or it's technical limitation? ... in madVR's HDR to SDR conversion by using pixel shader math. It looks terrible in the blue a little bit better in the magenta and almost OK in the green and yellow. I know that this conversion/process is not lossless but this looks horrible and I simply can't believe that it's by design. madshi, a while ago there was a quite detailed/heated discussion how should we configure madVR in regards to the display calibration options. In the past when we had only SDR content it was widely accepted the the best choice would be to select BT.709 and "pure power curve" 2.20 ... or 2.40 depending on the display/viewing conditions ... and then correctly configure/calibrate the display to the same params and let madVR do the needed conversions in the rare cases of SMPTE C/PAL/etc. content. But with the introduction of HDR and wider color gamut displays (usually not wider than DCI-P3) I'm starting to doubt this rule. Especially having in mind that the TVs/displays usually switch their color mode for HDR content ... and I think that this is correct since we don't want to use the much wider color space but still send data in a subset of it ... and in 8bit ... which might introduce banding. So what is madVR doing when it's rendering HDR content in BT.2020 container with usually up to DCI-P3 data (99.99% of the HDR content) and I have my display set to "already calibrated" to BT.709/2.40? Is it trying to squeeze the content in the narrow BT.709 space or it presumes that if I want HDR content (in passthrough mode) than my display should accept and be calibrated correctly to BT.2020? Don't we need a second calibration config for HDR (wide color gamut) content? ... or have I totally lost it and talking nonsense now? P.S. Can someone ... or you madshi ... remind me why when accessing madVR's filter properties from the player there is a need to open this small window with madVR's version and the two buttons where the user has to click one more time (and one more to close it)? Isn't it possible to directly open the settings from madHcCtrl.exe as it happens when I press the "Edit Settings" button? If it's some kind of a DirectX requirement to have such a window isn't it possible to just briefly create the window, internally call madHcCtrl and then automatically close the small window?
__________________
Z370M Pro4 | i3-8100 | 16GB RAM | 256GB SSD + 40TB NAS NVIDIA GTX 1060 6GB (385.28) | LG OLED65B7V Win 10 64bit 1803 + Zoom Player v14 |
|
8th April 2018, 21:58 | #50148 | Link | |
Registered User
Join Date: Jul 2014
Posts: 942
|
Quote:
I have tested the "Allied" clip mentioned in HDR passthrough, there is zero banding here. As you know recent drivers seem to have borked levels (not sure when that happened), so I've reverted to 385.28 which is the last driver where everything works (12bits selectable in custom refresh mode, ASIO4All compatibility, and proper levels). The only bug (HTPC-wise) that I'm aware of with this version is in Dolby Atmos speaker config, the SBs and the SRs are inverted. I use 7.1 so I don't mind.
__________________
Win11 Pro x64 b23H2 Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33 madVR/LAV/jRiver/MyMovies/CMC Denon X8500HA>HD Fury VRRoom>TCL 55C805K Last edited by Manni; 8th April 2018 at 22:08. |
|
8th April 2018, 22:03 | #50149 | Link | |
Registered User
Join Date: Oct 2016
Posts: 896
|
Quote:
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40 |
|
8th April 2018, 22:33 | #50150 | Link | ||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
http://madshi.net/madVRhdrTest5.rar This build still shows some weirdness for the blue, but the other colors should be fine. I'm not completely sure why the problem with blue happens, will have to investigate. Quote:
HDR calibration is a mess. IMHO the best workaround is probably to let madVR convert HDR to SDR, and then you can just run the converted SDR video through a conventional SDR 3dlut. Quote:
Quote:
|
||||||
8th April 2018, 22:51 | #50151 | Link | |
Registered User
Join Date: Jul 2014
Posts: 942
|
Quote:
In the meantime please could you not force 8bits in HDR passthrough, unless/until the bug is confirmed with all driver versions and not just the latest 39x.xx? Maybe the banding in 10bits was introduced in the driver at the same time they borked the levels? Also does your display support HDR 12bits natively? Quite a few people with 10bits displays have been reporting issues using 12bits with nVidia, but this might simply be because the display doesn't support 12bits natively and the banding is introduced by the display itself when using HDR passthrough. When converted to SDR, the path might be different and the banding might not occur. Only trying to find reasons why it might not be a universal bug, even if you can reproduce 100% with your set-up/display.
__________________
Win11 Pro x64 b23H2 Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33 madVR/LAV/jRiver/MyMovies/CMC Denon X8500HA>HD Fury VRRoom>TCL 55C805K |
|
8th April 2018, 22:57 | #50152 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
I see banding in 10bit fullscreen windowed mode, but *not* in 10bit fullscreen exclusive mode, which means the display can't be at fault. |
|
8th April 2018, 23:03 | #50153 | Link |
Registered User
Join Date: Jul 2014
Posts: 942
|
Okay, do you have a preferred pattern/clip to test banding? I use many but I'd like to be sure the same test you use is passed/fails here.
__________________
Win11 Pro x64 b23H2 Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33 madVR/LAV/jRiver/MyMovies/CMC Denon X8500HA>HD Fury VRRoom>TCL 55C805K |
8th April 2018, 23:25 | #50154 | Link | ||||
Registered User
Join Date: Mar 2002
Location: Sofia, Bulgaria
Posts: 661
|
Quote:
Quote:
Quote:
Quote:
Yes, I know I can do this but in order to do it I have to exit fullscreen mode and then go back in which temporarily alters the scaling algorithms and resets the ques (drops frames, etc) and ... I think ... it's not convenient at all - that's why I asked if there is a real reason the have the small window in-between the player's filter menu and the actual target. I've lived with it so many years that I've got used to it but in the last few days I've been improving my HTPC cooling and I've been reconfiguring madVR alot and it was quite a nag.
__________________
Z370M Pro4 | i3-8100 | 16GB RAM | 256GB SSD + 40TB NAS NVIDIA GTX 1060 6GB (385.28) | LG OLED65B7V Win 10 64bit 1803 + Zoom Player v14 |
||||
9th April 2018, 01:30 | #50156 | Link | ||
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
Quote:
This means that, for me at least, LG's 2017 OLEDs can only do HDR in 4:2:2 and I have to go into the inputs menu and change the icon when using HDR. Input lag goes up a bunch too because only game mode, with its terrible white point, has low input lag if it isn't icon'ed "PC".
__________________
madVR options explained Last edited by Asmodian; 9th April 2018 at 02:02. |
||
9th April 2018, 01:40 | #50157 | Link | |
Registered User
Join Date: Mar 2002
Location: Sofia, Bulgaria
Posts: 661
|
Quote:
Using these I think I confirmed for myself that LG OLED's "PC Mode" when used with HDR content is total garbage. Yes we do get 4:4:4 chroma support but at the cost of washed out colors and lack of 10bit gradation. Again using these video files I think I can say that NVidia's conversion from madVR's 10bit output to 8bit display output in 2160p50/60 is not at all bad. The reason I say this is that as we all know the HDMI 2.0 spec doesn't support RGB 2160p at 50/60Hz 10/12bit and the drivers silently switch to 8bit behind madVR's back but nonetheless I do see some gradation and not clipping which might mean that they are doing some dithering ... or some other kind of "magic". If only I had a keyboard around I'm kidding ... kind of ... Thank you for reminding me about this shortcut (a bit generic but still working) but to be honest very often I control/re-configure my player and/or direct show filters only using the mouse (a one from Logitech that has horizontal scrolling and a couple of additional buttons) since that's more convenient and because the keyboard for the HTPC is usually hidden in some drawer.
__________________
Z370M Pro4 | i3-8100 | 16GB RAM | 256GB SSD + 40TB NAS NVIDIA GTX 1060 6GB (385.28) | LG OLED65B7V Win 10 64bit 1803 + Zoom Player v14 |
|
9th April 2018, 02:15 | #50158 | Link | |
Registered User
Join Date: Mar 2002
Location: Sofia, Bulgaria
Posts: 661
|
Quote:
Does anybody know if Intel (HD4000) can output 10bit 2160p? ... or is there a user with AMD and one of the 2017 LG OLEDs here that can test this for us?
__________________
Z370M Pro4 | i3-8100 | 16GB RAM | 256GB SSD + 40TB NAS NVIDIA GTX 1060 6GB (385.28) | LG OLED65B7V Win 10 64bit 1803 + Zoom Player v14 |
|
9th April 2018, 04:20 | #50159 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
I believe these TVs simply suck with >8bit input but I do get noticeably more banding in the situation I described above. As I move the mouse back and forth with paused video some banding appears and disappears. There is still some, more than in 8-bit mode, but that is due to the TV itself instead of this issue.
__________________
madVR options explained |
9th April 2018, 08:08 | #50160 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
We use the ISubRenderProvider interface
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|