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. |
13th December 2015, 03:51 | #34601 | Link | |
Registered User
Join Date: May 2011
Posts: 51
|
Quote:
I was using Smooth motions since it was introduced (before it I had issues on my 60Hz only monitor). Never noticed anything bad about it. |
|
13th December 2015, 04:47 | #34602 | Link |
Registered User
Join Date: Apr 2009
Posts: 76
|
So, after more testing, it seems crossfire does not actually work in MPC and does not help accelerating madVR's computations even if it is forcibly enabled using profiles but for some reason, even when crossfire is forcibly disabled for MPC/madVR, during video playback, the second GPU sometimes randomly switches to 3D clocks (but doesn't stay at that clock all the time, even if I am using 256 Neurons in which case my first GPU cannot keep up and heavily drops frames) and the crash I am experiencing can definitely be resolved by disabling crossfire.
Disabling ULPS does not help either (I thought maybe the second GPU goes to sleep when I pause and when I unpause, crashes madVR when trying to wake up again). At this point in time it seems the only solution is to disable crossfire globally and enable it only when I want to play games. Fortunately this can be done without having to restart the OS. Unfortunately, with crossfire disabled, the second GPU never sleeps and stays at idle clocks which results in ~25 watts of extra power usage (yes, it matters for a student living in a foreign country). I might give MPC 32-bit + madVR 32-bit a try later. |
13th December 2015, 05:04 | #34603 | Link | ||
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
|
Quote:
Thanks. Quote:
__________________
madVR options explained Last edited by Asmodian; 13th December 2015 at 05:06. |
||
13th December 2015, 06:46 | #34605 | Link |
Registered User
Join Date: Dec 2011
Posts: 180
|
If anyone is interested, here is my experience for 1080 60i content double to 4k using nnedi on the r9 290/290x and gtx980
win 10 stock drivers there are 2 types of 1080i content, encoded broadcast and bluray(BR) broadcast tend to have some period that require "burst" performance, where BR is rather constant. setting is to use nnedi 16 + super res or nnedi32 while toning down non essentials (bicubic chroma, 3dlut on, banding on low/mid, order dithering, uncheck all trade performance) struggle = drop fame/low queue/broader-line rendering time r9 290 stock(16 +sr) struggle with either type r9 290 overclock 11xx(16 +sr) good enough for BR, struggle at some scene for broadcast, at 1200, it start overcome those scene, but not all card can get there HOT HOT HOT r9 290x mild overclock (16+sr) this was some time ago, but I remember both type run fine, with some real buggy scene in broadcast require higher overlock GTX 980 mild overclock (16+sr) playback BR fine, struggle at some scene, overall is close to 290 experience, cannot overcome those buggy scene even at 1500 GTX 980 mild overclock (32) seem to be enough for either type. I did not really test just 32 on the 290, will have a check now and put it up. edit: 290 mild overlock will handle either type fine on just nnedi32. Last edited by baii; 13th December 2015 at 18:52. |
13th December 2015, 07:54 | #34606 | Link |
Registered User
Join Date: Feb 2014
Posts: 139
|
I have a question about the OSD/madvr scaling behavior:
Whenever you set up an image upscale that results in a final step of upscale in one dimension but downscale simultaneously in another dimension, lanczos 3 is used for the upscale. Is this because Jinc cannot be used for 1 dimensional upscaling? http://imgur.com/UtXU4gM |
13th December 2015, 18:15 | #34611 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
crossfire and sli should already work but they don't.
crossfire and SLI need both the same data in each GPU. the data madVR is using is gigantic so copying the data from one GPU to the other will cost a lot at UHD and this will not change with DX12. |
14th December 2015, 01:07 | #34612 | Link | ||
Registered User
Join Date: Mar 2002
Posts: 2,323
|
Quote:
If you use these resolutions then turn off smooth motion. Quote:
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config |
||
14th December 2015, 13:01 | #34615 | Link |
Registered User
Join Date: Sep 2015
Posts: 60
|
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." |
14th December 2015, 15:23 | #34617 | Link | |||||||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
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. |
|||||||||||||||||||||||
14th December 2015, 15:24 | #34618 | Link | |||||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
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. |
|||||||||||||||||||||
14th December 2015, 15:57 | #34619 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
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.) |
14th December 2015, 16:25 | #34620 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,342
|
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 |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|