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 October 2017, 12:15 | #46323 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
|
8th October 2017, 12:16 | #46324 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
I find AdaptiveSharpen plenty fast already. As far as improvements to it go if it even needs them that likely won't come till after 1.0
Doubt any changes to NGU are coming before 1.0 either, if you think RAVU does well in comparison to NGU AA, post some examples. |
8th October 2017, 14:16 | #46326 | Link | ||
Registered User
Join Date: Sep 2016
Posts: 89
|
Quote:
Quote:
Will the 1.0 version be available before 2020? |
||
8th October 2017, 16:02 | #46329 | Link | |
Registered User
Join Date: Sep 2012
Posts: 174
|
Quote:
just did some testing, created a custom mode in nvidia, 2160p24, only changed 24.000 Hz to 23.976Hz, left everything else. (So I basically only changed the pixel clock from 297.00mhz to 296.70mhz if I understand nvidias panel) So I tested standard modes 23 and 24 and my custom 24 mode by just running a 23.976fps video for about 10 minutes each time in FSE, every mode stabilized at the same Hz: 23.97894 Hz 1 frame repeat every 4.41 minutes in windowed or fullscreen windowed, I had different Hz every time: standard 23: 23.97894 Hz 1 frame repeat every 4.41 minutes standard 24: 23.99914 Hz 1 frame repeat every 41.71 seconds Custom 24: 23.97489 Hz 1 frame drop every 1.07 hours So the new custom mode does "something" different than the standard modes. Interesting thing to note is that according to the madVR custom modes tab, my custom 24 mode is not active, the 23Hz one is. This might be, because my custom 24 mode seems to have the exact same timing parameters as the standard 23 mode, even though I get different results in playback. I don't know if this is new information, or if this was obvious to you from the start, but there it is... Since I'm using windows 10, I should be getting 10bit in windowed fullscreen, correct? If so, 1 frame drop every 1.07 hours is good enough for me and I'm done for now. Though if bugs get fixed in the future, I'm happy to do more testing. On an unrelated note: the "display bitdepth - toggle" shortcut only goes through 9bit and 10bit the first go round... So if I have a 10bit display and use the shortcut, it'll go from 10 bit to 9, 8, 7, 6, then back to 8, 7, 6, 8, 7, 6 etc. Shouldn't it go back up to 10 bit? Last edited by Q-the-STORM; 8th October 2017 at 16:08. |
|
8th October 2017, 17:10 | #46333 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,926
|
or just look at this:
source: https://abload.de/img/title06.mkv_snapshot_j1ziv.png billinear: https://abload.de/img/bilinearwusqx.png spline: https://abload.de/img/splinewyszw.png ngu soft: https://abload.de/img/ngusoftveryhighhgsnw.png ngu standard: https://abload.de/img/ngustandardveryhighgeszx.png ngu sharp: https://abload.de/img/ngusharpveryhighxnssg.png the zipper and the hair is very different with the scalers and billinear is just bad. the source is pretty soft so the scaler are not doing much on the background because it is not in focus. |
8th October 2017, 17:27 | #46335 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,926
|
Quote:
ngu sharp: https://abload.de/img/ngusharpe1rem.png i don't even know where to start it is anywhere. if you can't see the major difference I suggest in a not offensive way to meet a optician to fix the problem. the difference is really really big al over the image except the sky. |
|
8th October 2017, 19:22 | #46337 | Link | |
Registered User
Join Date: Jan 2009
Posts: 625
|
Quote:
|
|
8th October 2017, 22:08 | #46338 | Link | |||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Is in v0.92.5. Maybe I'll look into that at some point, but it doesn't have a very high priority right now. With the anime image bjin has selected for his own image comparison NGU AA looks better to me than RAVU. So I'm not sure how much I can optimize there. Quote:
Quote:
Quote:
There is a strength setting, and unfortunately higher strengths can be quite destructive. Well, they most of all destroy block and mosquito artifacts, but eventually also some image detail. I'm not sure, maybe you can leave the lowest strength enabled at all times, you'll have to test if it costs too much detail or not. But I rather recommend having this algorithm disabled by default and only enable it if your eyes complain about compression artifacts during playback. |
|||||
8th October 2017, 22:18 | #46339 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.92.5 released
http://madshi.net/madVR.zip Code:
* added new algorithm "reduce compression artifacts" * added new algorithm "reduce random noise" * added file name tag and keyboard shortcut support for new algorithms * switched to igv's AdaptiveSharpen variant * custom mode optimization is now available for modes not created with madVR * fixed: mode optimization didn't work for Nvidia (introduced in v0.92.4) * fixed: ProgDVB: DXVA deinterlacing didn't activate after channel switch * fixed: potential freeze when freeing madVR instance * fixed: playback trouble after switching video files (introduced in v0.92) * fixed: screenshot memory leak 1) Please test the new algorithms and let me know what you think! 2) The block and mosquito noise reduction is actually *one* algorithm named "reduce compression artifacts", not two separate algorithms. The other new algorithm is "reduce random noise". 3) Currently the new algos are only available in one quality/speed variant. I might offer different quality/speed settings in the future. I'm not talking about the algorithm "strength", which is a totally different thing. I'm talking about the speed of the algorithm, and the resulting quality of the noise/artifact reduction. 4) Currently chroma noise/artifact reduction is very slow because I'm doing it in luma resolution. In a future version I'll do it on the original chroma data instead which should reduce the chroma processing hit to a quarter of the current cost for 4:2:0 content. 5) Random noise reduction is currently limited to max 5 strength. In a future version it will probably go up to 10. 6) The higher "reduce compression artifacts" strength settings will totally destroy your images, so DON'T use them. You've been warned! They're there only for videos which are borked beyond good and evil. My advice is to keep this algo disabled by default, or at lowest settings and only increase the strength if really necessary. You can use file name tags (e.g. "some video deblock=5.mkv") to force a specific deblock setting for a specific file. 7) Please compare the new AdaptiveSharpen version (it's igv's variant) to the original AdaptiveSharpen algorithm. On a quick check I liked igv's variant better, but I'd like your feedback on that. |
8th October 2017, 22:18 | #46340 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,926
|
Quote:
if it is faster and still in progress why not add it as long as it is a meaning full alternative. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|