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. |
19th July 2015, 16:10 | #31942 | Link | |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quote:
HQ adds a foggy smoke screen onto the picture, 1 is way too strong to be useful to anything(w/o HQ at least) and radius makes very weird artifacts when I mess with it. TBH this release has completely killed SuperRes for me, I'm kinda tired of whining in this thread to have SR reverted to how it was in .15(which would never happen anyway) so I might either call it a day and stick with it(3 passes at 0.65 is actually quite a bit too sharp, 0.42 looks less edgy) or I might just bite the bullet and give up on SR altogether as it would appear that a combination of sxbr+adaptive sharpen also gives very nice results(too bad the strength of sxbr doesn't come with a knob but AS does...for now at least). Usual story that all roads lead to Rome, hopefully you won't kill AS too by removing its strength knob and adding weird radius options or something And I wholeheartedly disagree that 2 passes at 1.0 look "pretty much" identical to 3@0.65 in .15 as the former looks way sharper and less detailed....like upscaling posterization and unchecking "refine after every 2X upscaling" makes matters even worse. Oh well. Last edited by leeperry; 19th July 2015 at 16:13. |
|
19th July 2015, 19:19 | #31946 | Link | |
Registered User
Join Date: Dec 2008
Posts: 496
|
Quote:
How do you expect madshi to react? Believe 20 other people that say A looks more satisfying and agree with madshi's findings or with 2-3 other people that don't agree, but they also don't show why they don't agree with e.x. samples or screenshots (including the settings they used). Especially when you write "tests for a few days now". Well, to be quite frank, IF I had so much time on my hands to do tests, I would not hesitate for even a second to provide a couple example shots to show it to everyone, so there actually is some discussion that will help everyone. Last edited by iSunrise; 19th July 2015 at 19:27. |
|
19th July 2015, 19:24 | #31947 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
|
|
19th July 2015, 20:45 | #31948 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Quote:
On top of that, output of interlaced material from a PC has all sorts of problems.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
19th July 2015, 22:51 | #31949 | Link | ||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I suppose the proper solution for this would be to remove the aliasing artifacts before upscaling the image. AviSynth has some filters for that, but they're pretty slow, IIRC. Maybe madVR will get such a filter at some time in the future, but probably not soon. Quote:
Quote:
Anyway, there may be room for further performance optimizations. For now we're trying to fine tune the algorithm, remove what's superfluous, set fixed values where it makes sense. Once the dust has settled, maybe some performance optimizations can be done. Quote:
Quote:
Quote:
Quote:
Leave LAV at default values. Don't use YCbCr unless after extensive testing you find it works best, due to technical limitations of your TV. Whether you should set the GPU, TV and madVR to PC or TV levels is a complicated question that can't be explained in one short sentence. Anybody has a link to a guide that explains this? Huh? This release re-introduced "HQ off" for you. I'm confused how that would kill SuperRes for you? Instead of saying "thank you" for adding a tweak *just for you*, you continue to whine, and you don't do screenshots, as I asked you to multiple times already. You're not very motivating atm. I've already told you that if that is your opinion, I want proof, in the form of screenshots. Put up or shut up!! |
||||||||||||
19th July 2015, 22:54 | #31950 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.88.20 released
http://madshi.net/madVR.zip Code:
* changed OSD rendering logic all over again * added SuperRes "radius" option (only for testing purposes) * removed SuperRes "use alternative color space" option * replaced SuperRes strength+passes option with a new strength option * added madTPG APIs "IsFseModeEnabled" and "En/DisableFseMode" Everyone who had *new* problems, introduced by v0.88.17, please test this new build and let me know if your problems are fixed. Everyone who has "old" problems (which affect builds older than v0.88.17, too), please hold your horses for now. Allow me to fix all the new issues first, otherwise I'll get bugfix overload. |
19th July 2015, 23:11 | #31951 | Link |
Registered User
Join Date: May 2012
Posts: 447
|
Sure, that's fine. I can just use the D3D11 path anyway.
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
19th July 2015, 23:47 | #31953 | Link |
Registered User
Join Date: Jul 2015
Location: Seattle, Washington
Posts: 53
|
New bug with the 88.20. Seems like the OSD is reporting incorrect render times. Render time is lower than what it was in previous updates with the exact same settings (I'm not using SuperRes). It reports even lower render times when I go from NNEDI3 16 -> 32 but the dropped frames and presentation glitches counter begin to rise.
|
19th July 2015, 23:58 | #31954 | Link | ||||
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quote:
I tried yesterday late at night on my usual 720p material and this afternoon again on different kinds of SD material just to be sure that my impressions didn't change and then I saw that post that pretty much synthesized exactly what I saw so I thought I would +1 it, nothing more. I also came to the conclusion this afternoon that sxbr+AS seem to look equally good(or even better?) than SR in .15 with 3@0.42 but I would need to finetune their strengths(sxbr75+AS 0.5 atm), madshi made clear that SR would take a route I'm not interested in so again I can either give up on SR altogether(as it's literalling been going downhill since .16 for me) or remain stuck in .15-land. I haven't really decided yet, yes it takes several test sessions on different kinds of material before making a decision. If I had access to the script as a text file or could fire up SR from PotPlayer as a PS script, this wouldn't be much of a hassle but I do realize that madshi's work on mVR is already a gift, he's not too keen on sharing his work with the competition, he primarly codes mVR for his own use and he's already extremely kind to share it with us...so I need to adapt my needs to what he's willing to offer(and PQ is stellar anyway ). Quote:
I wasn't able to use versions since .16 due to HQ SR being forced so I'm basically going from .15 to .19 and yes this new build is a total show stopper for me as far as SR is concerned, HQ or not. Screenshots? I'm sure you did a whole bunch of them when deciding that HQ=off looks horrible to you? Or did you toggle it while playing movie content? My point is that for all I know screenshots wouldn't prove anything and I would waste hours looking at microscopic pixels differences. It really only matters in motion IMHO and the differences I'm seeing are not content dependent to the least. At the end of the day what matters if that SR looks good to you and that I can also keep on being stunned by mVR, I seem willing to give up on SR as our views towards it would appear to drastically diverge. No worries. Quote:
Quote:
Last edited by leeperry; 20th July 2015 at 02:10. |
||||
20th July 2015, 01:23 | #31956 | Link |
Registered User
Join Date: May 2012
Posts: 447
|
madshi, I took debug logs for the 'repeated frames show very old frames' thing, comparing d3d9 and d3d11 windowed mode, though I don't know if they show anything. Just let me know when you have time to look at them.
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
20th July 2015, 01:23 | #31957 | Link | |
Registered User
Join Date: Apr 2011
Posts: 24
|
Quote:
original http://www84.zippyshare.com/v/CDsDqi9P/file.html hq strength 1 radius 0.70 http://abload.de/img/seventhhqjpjxy.png nohq strength 1 radius 0.70 http://abload.de/img/seventhnohqaejzk.png It's hard to compare because strength 1 for nohq is too strong. As I said radius does help. But HQ still has that almost softer than original look with slight ringing around numbers. White is spilled into black area, black is spilled into white area. NoHQ doesn't have that problem even on higher strengths. But as I said even strength 1 is too strong for my taste. |
|
20th July 2015, 01:42 | #31958 | Link | |
Registered User
Join Date: Jul 2012
Posts: 20
|
Quote:
Examples and dump below: OSD (SD MPEG-2) dump OSD (720p - presentation glitches when step forward/backward) dump Win 7 SP1 Pro x64 ASUS GTX770 2Gb ASUS VG278H 120 Hz MPC-HC x64 latest nightly build LAV x64 latest nightly build |
|
20th July 2015, 02:48 | #31960 | Link |
Registered User
Join Date: Jul 2015
Posts: 3
|
madVR / Potplayer / OBS broken since v0.88.17
I am reporting a bug that was introduced since v0.88.17.
In order for OBS (Open Broadcaster Software) to capture video in Potplayer with madVR, you have to use "Game Capture" source. I was told by someone on the OBS forum that this uses OpenGL to capture video. And it is the only method to capture video with madVR as the renderer. Since v0.88.17 video capture using OBS (both versions) and Potplayer causes unwatchable jittery/stuttering video. The video looks perfectly fine on screen. But the OBS capture window shows jittery video. v0.88.16 was the last release that worked fine. The bug can be reproduce on both of my PCs using the default madVR settings and default PotPlayer settings. However, if I use a different video player like MPC-HC x64 or bsplayer with madVR the video capture in OBS is fine. But when I adjust volume level the OSD causes stuttering video in the capture window. I don't expect this bug report to get a lot of attention since it's very specific but I still wanted to report it for documentation purposes. I hope other forums members can reproduce the bug and verify my claims. These were the changes introduced to madVR, perhaps one of these changes broke functionality between madVR, Potplayer, and OBS: v0.88.17 * madVR now renders in paused and stopped mode, too * added automatic OSD low latency logic * added SuperRes anti-ringing filter * fixed little SuperRes quality detoriation introduced in v0.88.16 * fixed: high GPU consumption in paused mode (PotPlayer, Kodi DSPlayer) * all (useful) IVideoWindow APIs now work even when no pins are connected My setup: madVR v0.88.17 thru v0.88.20 x64 bit Potplayer [1.6.55124] 2015/07/10 x64 OBS Multiplatform 0.11.1 x64 OBS Original 0.652b x64 Win 7 / Nvidia 8800 GTS Last edited by jewshawn2; 20th July 2015 at 11:42. |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|