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. |
![]() |
#34623 | Link |
Registered User
Join Date: Sep 2015
Posts: 59
|
How does the 4.4.4 test image work?
"If you want to test whether your display supports RGB in 4:2:0, 4:2:2 or 4:4:4, you can use this test image. Make sure you display it with 1:1 pixel mapping, otherwise it won't work." |
![]() |
![]() |
![]() |
#34625 | Link | |||||||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,137
|
Quote:
Quote:
Quote:
Quote:
Thanks! Quote:
Quote:
Quote:
Quote:
Quote:
It increases the contrast between brighter and darker pixels in image areas where there are no edges nearby. Doing so makes image detail stand out more, but it also makes noise, grain and artifacts more visible. So it's probably more useful for clean/good sources. Quote:
Quote:
Also make sure your GPU settings don't force anisotropic filtering or anti-aliasing. Doing that slows down your GPU without visual benefit in madVR. AFAIK generally yes, as long as you don't have CrossFire, but there's always the odd user who has problems, so there's no guarantee. Quote:
Quote:
Quote:
I'll revisit the whole settings dialog, and its user-friendliness (or lack of) before I reach v1, but atm it's not a priority for me. Quote:
BTW, in case you have a CIH/CIA/CIW setup, madVR can automate all that for you, including setting automatically activating lens memories for cinemascope movies etc... Quote:
Quote:
Quote:
Quote:
Quote:
In order to find the failure to enter FSE mode, I'll need another log with the debug OSD (Ctrl+J) active while recording the log, because having the debug OSD active adds some more information to the log that I need in this case. Quote:
Quote:
Quote:
Generally you should get better quality when letting madVR deinterlace. So it might make sense to try that again and post a screenshot of Ctrl+J with that setup, too. |
|||||||||||||||||||||||
![]() |
![]() |
![]() |
#34626 | Link | |||||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,137
|
Quote:
Quote:
I might add NLS in some far away future version, but it's very low priority because I consider NLS to be bad. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
It's impossible for me to know for sure whether a source is progressive or not. For all I know, the video stream can claim it's progressive but it would still be telecined. Because of that, if forced film mode is activated, IVTC is always performed, even if the source appears to be progressive. But as mentioned above, due to the very high reliability of the madVR IVTC algorithm it's not a problem if you activate it accidently - other than raising CPU load a bit. Quote:
Quote:
Or are you saying that every time the old version reported a repeated frame, you got a visual stutter? That would be something completely different, of course! Quote:
1) Do you have a 3dlut active? If so, some old GPUs may run into problems if certain areas of the 3dlut are accessed. I've had that reported by one user some years ago. But it was a *really* old GPU. 2) Maybe it's some sort of deinterlacing issue? Are you using forced film mode? Film credits are sometimes video mode and require proper deinterlacing. I suppose with EVR this problem does not occur? Can you post a screenshot of the Ctrl+J debug menu in the moment when those frame drops occur? Quote:
Quote:
Or are you asking whether I'd be willing to help mpv future development? If that's your question then my answer is a simple no. I don't have the time to help other projects. Furthermore madVR is supported by a lot of different media players. I can't help one of them but not the others. That wouldn't go down well with the other media player devs/companies. Quote:
Quote:
Quote:
Quote:
Quote:
It's not a limitation of the Jinc algorithm itself, it's just that I haven't implemented Jinc downscaling in madVR (yet?). No. |
|||||||||||||||||||||
![]() |
![]() |
![]() |
#34627 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,137
|
madVR v0.89.18 released
http://madshi.net/madVR.zip Code:
* added tone mapping support for HDR content * added gamut mapping support for HDR BT.2020/DCI-P3 content * added support for SMPTE 2084 transfer function decoding * added support for receiving HDR metadata from LAV Video Decoder * added "maximum display luminance" option to display properties page * added "HDR" profile variable * SuperRes now supports being run after every ~2x upscaling step (again) * improved JVC projector ip control connection reliability 1) First of all, this madVR build does *not* aim to send HDR content untouched to the display, to let a "HDR compatible" display do all the processing. Doing that might be supported by some future version (as an option). But for now what madVR does is convert the HDR content in such a way that it looks well on *any* display (new and old), regardless of whether the display officially supports HDR or not. 2) The key idea of HDR is to increase the peak white luminance, so that we can get brighter highlights, and more texture detail in bright image areas. HDR content uses 10bit (or more) instead of the usual 8bit, and it also uses an improved transfer (gamma) function, which means we also get better shadow detail at the same time. 3) HDR content is encoded using a totally different transfer ("gamma") curve. So playing HDR content with a media player and display which don't understand the new transfer function won't look good/correct. It will look totally washed out. 4) The new transfer function directly maps each pixel to a specific desired luminance value (in "nits" or cd/mē). Possible values are 0 nits up to 10,000 nits. However, videos don't have to use the full 0 - 10,000 range, they often top out at either 4,000 nits or 1,200 nits (from what I've seen). 5) UHD Blu-Ray will usually be encoded in BT.2020 color space, which is extremely wide. However, videos don't have to use the full BT.2020 space, they usually only use DCI-P3, inside of the encoded BT.2020 container. 6) Today's displays (even the best of the best) cannot really properly reproduce HDR content. E.g. many display's don't reach full DCI-P3 colors yet (let alone BT.2020), and no available display today comes even close to be able to output 10,000 nits! Which means that someone somewhere has to convert the HDR content down to something the display can handle. The consumer electronics world plans that the display will do this conversion (only new models, obviously) - and every TV manufacturer will write their own conversion algorithms because there's no standard for that! From what I've been told those conversion algorithms (at least for the first few HDR display generations) are probably not going to be very high quality. 7) madVR is able to compress both the luminance and the colors down to what your display can handle. It uses reasonably high quality algorithms for that. I might find even better algorithms in the future, but for now these algorithms should be a good starting point. 8) UHD Blu-Rays will come with an updated copy protection. So madVR will not be able to play them - unless the copy protection gets broken at some point. If you want to test HDR playback, please update to a new LAV nightly build because only the latest LAV nightlies are able to pass some HDR metadata information to madVR! (P.S: There's also a new "madTestPatternSource" version available with some HDR test patterns. Link see first post in this thread.) |
![]() |
![]() |
![]() |
#34628 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,042
|
Are there any smart ideas how to properly configure a display for HDR? I could set it to its maximum brightness and measure this, and tell madVR about it.
However, the maximum brightness is far above what I find "pleasing" for SDR movies, or even the desktop/player UI, so its really not "good" to configure it to that. Of course I could tell madVR about the brightness of my average setup, but then there is nothing to gain from HDR at all.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
![]() |
![]() |
![]() |
#34629 | Link |
Registered User
Join Date: Apr 2009
Posts: 76
|
So, there is no way to prevent the crashes without disabling Crossfire globally? I'm not trying to accelerate madVR's computation with crossfire, mind you, but rather, I am trying to find out why the crashes happen even though crossfire is not enabled for MPC-HC/madVR and is only enabled for applications that specifically have a profile.
|
![]() |
![]() |
![]() |
#34630 | Link | |
Registered User
Join Date: May 2015
Posts: 78
|
Quote:
Note that this only seems to happen when fps is almost the same as the display rate. It took me some time to remember that the interlaced NTSC DVDs (actual video, not film) will have there frames doubled by DXVA deinterlacing, therefore running 59 fps at 60 Hz. This seems to be hard for FRC. (No way around starting to use ReClock, it seems?) madVR never did report such repeated frames, at least not for me. When viewing a 24 fps movie at 60 Hz with FRC on I never got even one repeated frame reported in any version. Or do you want to say, this was by accident, because each and every frame was unique or blended, so that there never was any actual repeated frame? |
|
![]() |
![]() |
![]() |
#34632 | Link | |||
Registered Developer
Join Date: Sep 2006
Posts: 9,137
|
Quote:
Another option would be to use different presets in the TV, but only some TVs support that, and the lack of auto switching could be quickly become annoying. Edit: My idea above would only work for video playback, obviously, it would not do anything for desktop or player GUI. If you need a solution for that, too, maybe one option would be to misuse the GPU gamma ramps to make everything darker? That should work for desktop and media player GUI. However, GPU gamma ramps don't use dithering, I think, so it would not be a good solution for image quality. Quote:
Quote:
What fill state do the queues have when that stuttering occurs? How many frames are you presenting in advance? Or did you disable the "present several frames in advance" option? FWIW, it's recommended to use that option because it increases presentation reliability. Last edited by madshi; 14th December 2015 at 17:01. |
|||
![]() |
![]() |
![]() |
#34633 | Link | |
Registered User
Join Date: Oct 2012
Posts: 6,847
|
Quote:
switching the HDMI output on a TV doesn't sound too terrible. and DP 1.3 to HDMI 2.0 should work with an passive adapter. you are simply way ahead of time with that feature. but i don't think leaving the TV at a high brightness for SDR content is a good idea. none OLED screens will lose a lot of CR this way. and local dimming has a enough of problems already without this high brightness. |
|
![]() |
![]() |
![]() |
#34634 | Link |
Registered User
Join Date: Sep 2006
Posts: 2,181
|
So does this mean even when using madVR for watching an UHD Blu-ray on my current plasma TV (VT60) that it will look bad/not right?
__________________
Laptop Lenovo Legion 5 17IMH05: i5-10300H, 16 GB Ram, NVIDIA GTX 1650 Ti (+ Intel UHD 630), Windows 10 x64, madVR (x64), MPC-HC (x64), LAV Filter (x64), XySubfilter (x64) (K-lite codec pack) |
![]() |
![]() |
![]() |
#34635 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,042
|
Quote:
Note however that not all UHD Blu-rays will use HDR, in fact most will not. There may even be two releases of movies, one in HDR and one SDR.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
![]() |
![]() |
![]() |
#34636 | Link |
Registered User
Join Date: Sep 2010
Posts: 321
|
Thanks for new version Madshi, I have a quick question though. How do we know what to set the display peak luminance to? I have an older 1080p 32" EX400 Sony LCD and a 1080p 55" VT60 Panasonic Plasma. Both by default are set to 600 nits. Not sure how or where to find the correct setting. I know one thing is for certain, the plasma is a much higher end display which may affect this setting?
__________________
MPC-HC/MPC-BE, Lav Filters, MadVR CPU: AMD Ryzen 5 1600, Video: AMD Radeon RX Vega 56 -> TCL S405 55", Audio: Audio-Technica M50S |
![]() |
![]() |
![]() |
#34637 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,042
|
Quote:
Note that documented peak luminance will always refer to 100% backlight setting, which you may not find good for general watching purposes, like myself.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
![]() |
![]() |
![]() |
#34638 | Link | |
Registered User
Join Date: Sep 2013
Posts: 919
|
Quote:
Questions: How can you really know in what range the studio mastered their movie? Seen where? Judging by what I see with madTestPattern, how did you know what region is more important to compress and what to clip? With 1200nit mastered content (presumably), the whole range is compressed. With 4000nit, again practically the whole range is compressed. Doesn't that mean that the movie will be too dark overall just so that we will be able to see the super bright parts?
__________________
System: i7 3770K, GTX660, Win7 64bit, Panasonic ST60, Dell U2410. |
|
![]() |
![]() |
![]() |
#34639 | Link | |
Registered User
Join Date: May 2010
Posts: 236
|
Quote:
Here's the log with the debug OSD: https://yadi.sk/d/QDP2CRqHmDvVi Maybe you can tell why it doesn't go into FSE? I've downloaded several test videos and tried the new HDR feature. I am currently using a professional NEC P241W monitor which is true 10 bit through DisplayPort cable and is capable of >Adobe RGB coverage and has a preset for DCI color space. I've set the maximum brightness which is 350 cd/m2 for this display and set the white point to 6500K. I used 400 cd/m2 in madVR settings. Well, it works. ![]() Also, you said that we may choose the maximum luminance between 0-10000 cd/m2, but the lowest I can choose now is 400 cd/m2. Is it intentional? Can we choose luminance in increments other than 100-200? Last edited by TheElix; 14th December 2015 at 19:31. |
|
![]() |
![]() |
![]() |
#34640 | Link |
Registered User
Join Date: Sep 2013
Posts: 919
|
I think the new "display peak luminance" feature only works if your display has a static and unchangable minimum light level (MLL) of the display.
Meaning, it only truly works if you have a FALD (full-array local dimming) display. If your display can do 4,000nits but keeps the contrast ratio at 1000:1 it simply does not differ from any other SDR TV. OR, I might be very wrong! ..and madVR actually compress the HDR content to 1000:1 and you should turn your SDR display brightness to max (400nit) to utilize the new feature...? I need some HDR demo clips, anyone?
__________________
System: i7 3770K, GTX660, Win7 64bit, Panasonic ST60, Dell U2410. Last edited by James Freeman; 14th December 2015 at 19:32. |
![]() |
![]() |
![]() |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|