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. |
29th September 2018, 09:16 | #52821 | Link |
Registered User
Join Date: Dec 2016
Posts: 212
|
@huhn: I think I understand now what you want to say but default values are for people who don't know their gamma, white and black levels and that (must be) ok. But HDR levels are absolute and those values won't be converted to absolute brightness levels unless you specify actual SDR gamma you calibrated your tv to if you have the possibility to do that. I know, you'll say that top brightness differs from Tv to Tv (even HDR models) anyway so why stick to absolute levels but for my way of thinking, HDR-SDR conversion is also designed to simulate, on an SDR TV with high brightness, as close as possible how it would look on a HDR display, not just losely convert to SDR, if you calibrated your SDR tv and know it's characteristics. Of course, it means multiple processing, quality depends on TV's gamma precission and lut bitdepth and thus banding is a risk.
Sent from my GM 5 Plus d using Tapatalk Last edited by mytbyte; 29th September 2018 at 09:21. |
29th September 2018, 10:37 | #52822 | Link | |
Registered User
Join Date: Feb 2015
Location: Bavaria
Posts: 1,666
|
Quote:
Why is 399.xx working fine for HDR? Because the 399.xx driver is fine. You get another installer for Win 8.1 which is also smaller: Version: 411.70 WHQL Freigabedatum: 2018.9.27 Betriebssystem: Windows 7 64-bit, Windows 8.1 64-bit, Windows 8 64-bit Dateigröße: 469.19 MB -------------------------------------------------------------------------------------------- Version: 411.70 WHQL Freigabedatum: 2018.9.27 Betriebssystem: Windows 10 64-bit Dateigröße: 520.35 MB But I have the same opinion that Win 8.1 is better suited for HTPC use, but since I am using Win10 for over 3 years now, I think Nvidia should be able to deliver a working driver and not brk things repeatedly. I stay with Win 10 for the next time. |
|
29th September 2018, 11:59 | #52823 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.92.17 released
http://madshi.net/madVR.zip Code:
* modified/simplified HDR tone mapping settings page * small HDR tone mapping saturation improvement * OSD now also shows the measured luminance of the current frame (in addition to the average) * fixed: render & present queues didn't always fill in Windows 10 build 1803 * fixed: using XySubFilter sometimes resulted in black screen / freeze * fixed: using HDR "processing" resulted in dark and red-ish image * fixed: using BT.601/709 gamma curve with HDR tone mapping produced gray-ish image * fixed: settings dialog sometimes crashed on display mode / custom mode tab |
29th September 2018, 13:05 | #52825 | Link |
Registered User
Join Date: Mar 2018
Posts: 22
|
madVR display device
I get all sort of display devices in madvr, for the moment i have Yamaha RX2070, Intel Vertex twice and Visio M50-E1
and for the moment only the Visio M50 are active but I don't own a Visio M50, so what is happening with my devices and how do i get rid of an active device I don' own? |
29th September 2018, 13:30 | #52826 | Link | |
Registered User
Join Date: Jun 2007
Posts: 652
|
Quote:
First: I've never doubted that madVR could do a better tone mapping job than what internally LG OLEDs achieve. The internal SoC is most likely no match for a powerful enough GPU. *And* I have better faith in your algorithms than LG's. You might be right that LG's algorithm isn't smart enough to take into account ABL. But that's no reason for madVR not to do it, correct? Assuming RTings values are correct (and they do provide them for many TVs out there), it would be a great option to have to provide even better tone mapping, wouldn't it? Having peak nits values according to "screen space" occupied by high nits content. Maybe it's too hard to do that calculation in real time, I don't know. Or maybe it's useless, I don't know. Although, if it's impossibile to disable tonemapping on the TV, from what you state I conclude that it would be better to turn off the option in madVR anyway, am I right? Lastly, although I know the above was not directed to me, I have pretty clear in mind the fact that all OLEDs tone map HDR content. There's 1000 nits mastered content and 4000 nits mastered content. Peak nits highlights in OLEDs don't even reach 900, so tone mapping is a must. |
|
29th September 2018, 13:55 | #52827 | Link |
Registered User
Join Date: May 2012
Posts: 447
|
Just tested and I can confirm that my problems are gone! Thanks for the great work
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
29th September 2018, 14:52 | #52828 | Link | |
Registered User
Join Date: Sep 2016
Posts: 70
|
Quote:
|
|
29th September 2018, 15:11 | #52829 | Link | |||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
> I doubt that madVR can provide a better tone mapping > results than the internal system in an OLED screen Quote:
If I don't know the *exact* way the ABL works, then trying to adjust to the ABL may make things worse than better. RTings might measure some thing, but they don't measure everything. E.g. does the ABL react to the brightest subpixel? Or to the combined brightness of all subpixels? What happens if there's very bright green, but blue and red are off? Which number of pixels exactly have to surpass a specific threshold to activate ABL? And is it a fixed threshold, or a "fuzzy" logic? I would basically need access to the exact formulas used by the ABL, for this to make any sense. Quote:
Quote:
Quote:
Quote:
Quote:
|
|||||||
29th September 2018, 16:16 | #52830 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
i even can turn the whole thing on the top. what about bt 1886 or a 3D LUT so we just do nothing in this case? or why is gamma 2.4 used in the first place over 2.2 by user in a dark room? ambient light sources and so much more gamma related things. nothing of this changes even if the source is HDR. even the brightness in an SDR file is absolute if someone would follow would follow it exactly and even that doesn't change that a gamma of 2.1 and lower can be quite handy depending on other factor. and how does any of this help user that don't know there gamma? that the calibration tab not something to guess about. |
|
29th September 2018, 16:32 | #52831 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
The only thing the user should know is that this setting will not impact SDR content. Most of that content today is 2.40 based on the calibration of the most popular mastering monitors out there. You have to guess at what your calibrated gamma might be for HDR -> SDR because there is no way for madVR to measure this. Even then, you may get the best result with a gamma other than 2.20. For some people (me included), 2.20 crushes black when PQ is converted to pure power gamma. Not everyone would understand they can experiment with this setting without upsetting SDR content.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
29th September 2018, 16:48 | #52832 | Link | |
Registered User
Join Date: Mar 2018
Posts: 22
|
Quote:
|
|
29th September 2018, 16:49 | #52833 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
would be nice if gamma would be such a simple topic than bt 1886 wouldn't be the "new" thing.
gamma 2.4 is a "bat cave" gamma and that's not a good idea in a daylight filled room and one of the reason is not generally correct and why there is no correct answer. getting the same gamma as a mastering screen is not always getting you proper result on a screen. |
29th September 2018, 17:36 | #52834 | Link |
Registered User
Join Date: Feb 2014
Posts: 39
|
On the topic of gamma, my SDR mode has always been calibrated to BT.1886 (which is power 2.40 on an OLED), and has been the perfect option from a pitch dark to a dim/low light room. As long as there wasn't direct sunlight or glare, details were properly visible. However, HDR mode is forced into power 2.2 on my OLED, without the option to change it. I took this to imply that all HDR content is mastered in 2.2, and the picture is perfect under this gamma. How do the HDR to SDR or just HDR pixel processed modes take this into account? Does SDR have to be calibrated for 2.2 or does madVR process it correctly into BT.1886? How does madVR know the TV gamma if you disable calibration controls (or what is the default)?
|
29th September 2018, 20:04 | #52835 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
HDR mode is always absolute PQ and not 2.20. HDR -> SDR is up to user preference and should match your known calibrated SDR gamma, but you could choose anything you want.
SDR content is mastered to a specific gamma as set by the mastering display, so madVR doesn't have to convert anything. As mentioned previously, the most commonly used mastering monitors today are a perfectly flat 2.40.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
29th September 2018, 20:05 | #52836 | Link | |
Registered User
Join Date: Dec 2016
Posts: 212
|
Quote:
You calibrate to PQ or ideally, to BT.2390 curve that defines the tone mapping for TV's that can't reach required brightness. MadVR doesn't know the gamma of your TV but is doesn't need to if your TV is HDR and you feed it HDR signal. |
|
29th September 2018, 20:38 | #52837 | Link | |
Registered User
Join Date: Jun 2007
Posts: 652
|
Quote:
In my defense I meant it in the contest of being unable to take ABL into account (which is something I hope the TV internally does, I don't know for sure though) while I was asking if that could somehow be implemented in madVR. In any case, I'll stop here. I don't have an OLED screen yet (still plasma for me, last model Kuro), so I'm just discussing to stay "up to date" of where everything is going. |
|
30th September 2018, 03:04 | #52839 | Link | |
Registered User
Join Date: Sep 2018
Posts: 22
|
I don't think the driver size matters as long as it works as expected, and it does work well on Windows 8.1. Just think why Madshi keeps recommending 8.1 for HTPC, that is for a reason. You can see most users here and other forums are having issues with Windows 10.Anyway, all I can say is 8.1 resolved all the issues that I was having on windows 10.
Quote:
|
|
30th September 2018, 03:53 | #52840 | Link |
Registered User
Join Date: Apr 2011
Posts: 121
|
I played several movies just now with MadVR v0.92.17.The visual effects between the HDR mode and the non-HDR mode(I can't regard it as HDR->SDR mode any more,LOL,because of modified name) look undifferentiated when I set peak nits to 1099,899,699,499,299,200 separately.I guess the non-HDR mode should be devoted to the oled TV set with lower brightness.Unfortunatedly,Running the highlights recovery algorithm will consume pc resources tremendously so that the playback of HDR movies gets stammering and stuttering very much.I'm expecting the algorithm will improve dramatically soon later.
Thanks to super master Madshi for your diligent work. |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|