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. |
5th July 2015, 14:19 | #31521 | Link | |
Registered User
Join Date: Apr 2009
Posts: 1,019
|
Quote:
Last edited by 6233638; 5th July 2015 at 14:22. |
|
5th July 2015, 14:33 | #31522 | Link |
Troubleshooter
Join Date: Feb 2014
Posts: 339
|
Some extremely old (poorly coded) videos can show pixelation with hardware acceleration on, but usually those are rare to come across these days. To a degree some of the madVR error correction features may lessen or eliminate some of the pixelation, but its hard to say for sure. Try with it enabled, and if you see pixelation in your videos then you can set it to none instead. Native should be the fastest given that it doesn't copy data back out to the system/cpu. Depending on the speed of your non-gpu components (memory/cpu) you may see/notice a difference between copyback and native, or you may not. Bottom line is in most cases native should be faster. This is more of a LAV than madVR topic. There are quite a bit of articles/posts about native vs copyback you can find with a search engine, and if those don't address the issue to your liking you can post in the LAV forum.
__________________
System specs: Sager NP9150 SE with i7-3630QM 2.40GHz, 16 GB RAM, 64-bit Windows 10 Pro, NVidia GTX 680M/Intel 4000 HD optimus dual GPU system. Video viewed on LG notebook screen and LG 3D passive TV. Last edited by Anime Viewer; 5th July 2015 at 14:36. |
5th July 2015, 16:20 | #31524 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
They got deleted because the latest LAV build has faster copyback routines than madVR ever had. If you want to use DXVA decoding with the best quality, use the LAV copyback functionality. If you want DXVA decoding with the fastest speed, use DXVA native, but then you'll get ever so slightly lower chroma quality with some GPUs (Intel, NVidia). |
|
5th July 2015, 17:37 | #31527 | Link | ||
Registered User
Join Date: Nov 2011
Posts: 187
|
Quote:
Feedback on SuperRes: Quote:
2) The default values look good to me. I tried other values but could not decide whether it’s getting better or worse. 3) I prefer HQ downscaling to be enabled. 4) 2 passes look fine. However, I set the number of passes to 3. There is not much difference though. |
||
5th July 2015, 17:58 | #31528 | Link | ||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
|
||
5th July 2015, 19:03 | #31529 | Link | |
Registered User
Join Date: Jan 2010
Posts: 169
|
Quote:
|
|
5th July 2015, 19:19 | #31531 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.88.15 released
http://madshi.net/madVR.zip Code:
* super-xbr image doubling AR optimization: 20% performance boost * super-xbr chroma upscaling now supports higher quality AR algo -> 6% slower * super-xbr chroma "AR" option now switches between low/high AR quality * modified Bilateral chroma upscaling algorithm parameters For super-xbr chroma upscaling, v0.88.14 either supported "no AR" or the original super-xbr strict AR. Now v0.88.15 doesn't support "no AR", anymore. Instead the "activate anti-ringing filter" option now activates the slower high-quality madVR AR algorithm. With the "activate anti-ringing filter" option disabled, the strict AR algorithm is used instead. I know, this is slightly confusing, but I think it's more useful to offer these two different AR algos instead of offering no AR at all, considering that the strict AR is so fast that it barely makes a performance difference. I've thought about which AR algo to use when the AR option in madVR is activated. But my thinking was that users usually expect higher quality and slower performance when that option is enabled, so that's how I decided that with the option activated, the slower high-quality madVR AR algo is used, and with the option deactivated, the strict AR algo is used instead. FWIW, at this point I think the stream of super-xbr tweaks from the previous weeks is at an end. No dramatic super-xbr changes planned for the near future, anymore. Would still love to get more feedback about the new SuperRes algo. |
5th July 2015, 19:52 | #31532 | Link |
MPC-HC Developer
Join Date: May 2010
Location: Poland
Posts: 586
|
Thanks for new release.
For some reason madshi.net domain is on Malvertising filter list by Disconnect (apparently uBlock addon uses this list). You might want to contact them to clear this up. |
5th July 2015, 20:05 | #31533 | Link |
Registered User
Join Date: May 2012
Posts: 447
|
Thanks for the new release! What AR algorithm is used for super-xbr image doubling? Or does AR not make sense for that?
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
5th July 2015, 20:09 | #31534 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Image doubling uses the high quality madVR AR algorithm. |
|
5th July 2015, 20:16 | #31535 | Link |
Registered User
Join Date: May 2012
Posts: 447
|
Thanks! That makes sense.
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
5th July 2015, 20:39 | #31536 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
The new AR filter for super-xbr is better than the original one, colors get better seperated with it instead of worse.
However, I still find the ringing more obvious than with Jinc AR, unless I set sharpness to 50. But this causes less clear color contrast again. So I personally will stick to Jinc for chroma with its aspect of "positive ringing". Have the values for SuperRes for chroma changed? I can't remember it worsening ringing with default values, but "now" it does. NNEDI3 luma, eternal love.. Regarding SupeRes for image doubling: I'm still sticking to passes 1, strength 0.3, softness 0 and HQ downscaling. Seems like a no brainer for me to use it at least this way since I never could see it making anything look worse. Bilateral chroma upscaling is still terrible. |
5th July 2015, 21:41 | #31537 | Link | |
Registered User
Join Date: Jul 2013
Posts: 76
|
Quote:
Went from windowed (1s) -> fullscreen (1s) -> windowed (1s) -> fullscreen (~10s) -> alt + f4 to close player in fullscreen. Queues not filling occurred, as well as playback appearing to stutter but not showing dropped frames. https://www.dropbox.com/s/hi8yiom7xc...20log.txt?dl=0 Not sure if it would make much of a difference, but here is another debug where I waited for queues to completely fill before switching modes. The bug occurred in both attempts and is easily repeatable by just toggling between windowed and fullscreen exclusive mode twice. Windowed (3s) -> fullscreen (3s) -> windowed (3s) -> fullscreen (~10s) -> alt + f4. https://www.dropbox.com/s/cqo5yif5vy...0log2.txt?dl=0 Again as a reminder, this only seems to occur with D3D11 10bit. D3D9 10bit and D3D11 8bit both seem to be fine. In a completely unrelated situation, it seems unchecking fullscreen exclusive mode to use the windowed fullscreen path crashes the nvidia display driver immediately when attempting to go fullscreen. Not sure if it is a problem with Windows 10 build 10164, GeForce 353.38, or madVR - but have been experiencing this for a few months. I primarily use fullscreen exclusive for the 10bit output so it isn't a big concern for me, just thought I'd let you know about it. |
|
5th July 2015, 21:50 | #31538 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
what would you get from powerdvd you can't get from anydvd hd if you want to use madVR? |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|