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. |
23rd November 2012, 04:39 | #15681 | Link | |
Registered User
Join Date: Oct 2012
Posts: 27
|
Quote:
To be sure that it doesn't keep any Catalyst control center settings, you have to uninstall the video card driver too. That way it wipes the registry entries for your video card in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video. When the operating system automatically reinstalls the video drivers when your restart your PC, it would give you a clean slate without any Catalyst settings. Before, with Catalyst control panel installed - left side is the unaltered video, right side is with all the Catalyst video color and quality settings on: After, with Catalyst control panel uninstalled, video card drivers uninstalled from device manager and registry settings wiped: |
|
23rd November 2012, 04:49 | #15682 | Link |
Registered User
Join Date: Aug 2010
Posts: 576
|
with amd drivers, even with the color settings set to use player's preference, the advanced video color still defaults to having a bunch of crap on.
and, with amd, I have crashes on seeking, using lav splitter, dxva2 with bilinear chroma, in fullscreen mode. |
23rd November 2012, 04:52 | #15683 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
Quote:
tested with quicksync, dxva2 native, dxva2 cp and lav software decoder |
|
23rd November 2012, 05:05 | #15684 | Link | |
Registered User
Join Date: Sep 2011
Posts: 14
|
Quote:
Sorry I'm an analogue guy. |
|
23rd November 2012, 05:11 | #15685 | Link | |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
Quote:
The only conclusion is that the GT 440 DDR5 (16-19ms rendering times) and lesser GPUs in full-power state, not having enough muscle for 1920x1080p60 Catmull-Rom linear light + AR downscaling. As for 1920x1080i30->60p downscaling, I'd assume it would need at least a GT 650 or GT 650 TI in full-power state, considering rendering times were 21-31ms + 3ms on the GT 440. It came to a point that I'd rather have reliable playback on all types of content, rather than needing to deal with switching of settings around all the time, else be greeted by unexpected dropped frames. As madshi stated a few times in the past, downscaling is more GPU intensive than the same algorithm used for upscaling. Last edited by cyberbeing; 23rd November 2012 at 05:21. |
|
23rd November 2012, 07:44 | #15686 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
I noticed enabling DXVA upscaling on my Intel HD4000 changes the color output, some colors are darkened some are lightened, everything under the media tab is set to application settings or is unticked. There's a slight pixel shift as well *shrug*
DVXA upscaling vs Jinc 3 AR. http://screenshotcomparison.com/comparison/159646 |
23rd November 2012, 09:26 | #15687 | Link | |
Registered User
Join Date: Dec 2010
Posts: 62
|
Quote:
|
|
23rd November 2012, 10:20 | #15688 | Link | |||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Anyway, DXVA decoding on XP is problematic, anyway. It's always been very unstable (blue screens etc) on my XP PC. And there's a fundamental problem when resizing the window, too. Resizing the window results in madVR trying to reset the D3D9 device, but in XP that is only possible if all GPU resources are destroyed first. That makes things very very complicated when using external DXVA decoders, because they hold some GPU resources, as well. In Vista (and win7 and win8) resetting the D3D9 device is possible without having to destroy all GPU resources first. So that's a much more friendly environment for DXVA decoding. As a result I have no intentions to support DXVA1/2 decoding on XP at all. Even if suddenly documentation for writing a DXVA1 renderer showed up, I'd probably not support it for XP because of the D3D9 device reset problem. FWIW, I fully support DXVA2 deinterlacing and scaling on XP and it works very stable for me. But right now chances for getting DXVA1/2 decoding support for XP are extremely low for madVR users. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
(1) Use software decoding and e.g. Bilinear scaling. (2) Use native DXVA2 decoding and e.g. Bilinear scaling. (3) Use software decoding and DXVA2 scaling. (4) Use native DXVA2 decoding and DXVA2 scaling. The reference is (1) for colors, brightness, contrast and gamma. This is how the image must look. Please check which of (2), (3) and (4) are different from the reference and which are identical. Also please check if maybe (4) is even more different than (2) and (3) are. (I don't need screenshots.) Please also list your GPU, your drivers, and your OS. Thank you!!! The scaling algorithm itself (e.g. Jinc vs. Bilinear) does not have any effect on color/contrast. I'm just saying that to clarify that the DXVA2 scaling algorithm itself isn't better than Jinc. It just happens that the colors look different when using DXVA2 for some reason. This could be a bug in madVR, or a misbehaviour of the GPU drivers. In any case, the DXVA2 colors are very very likely to be incorrect. It's just a happy accident that they might look pleasing in this specific case. |
|||||||||||||||
23rd November 2012, 11:26 | #15692 | Link | |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Quote:
-EVR CP in PotP -VMR9 in an old build from Casimir666 released in 2007 -EVR CP in the recent 6240 MPC build, whatever in regular or float mode = they all give identical colors with the nightvision script on my rec709 video test pattern! so if BTB/WTW are trimmed, it all remains a big mystery to me as to why the AVS PS script outputs the exact same colors as ddcc(): untouched: AVS PS script: ddcc: there are some slight R/G/B differences in the <16 and >235 regions but these might account for different gamma curves or slightly different coeffs...nothing appears to be "cut" Last edited by leeperry; 23rd November 2012 at 11:29. |
|
23rd November 2012, 11:47 | #15694 | Link | ||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Anyway, could you please give this finally a rest? I've told you many times, this topic is still under discussion between the devs. I will not do anything about this until the discussion has finished. Posting any more about this really doesn't make any sense right now. Quote:
So, suggestions for madVR default scaling settings, anyone? I'd like to aim low. Maybe I should be brutal and set everything to bilinear to achieve smooth results on any GPU for first time users? But that would be too extreme, I guess... |
||
23rd November 2012, 11:52 | #15695 | Link |
MPC-HC Developer
Join Date: May 2010
Location: Poland
Posts: 586
|
@crotecun:
Using old Microsoft drivers is just wrong :< And you don't need to uninstall CCC in order to disable video enhance features. Just disable everything and turn off demo mode, and that's all. Last edited by kasper93; 23rd November 2012 at 11:54. |
23rd November 2012, 11:56 | #15696 | Link |
Kid for Today
Join Date: Aug 2004
Posts: 3,477
|
Well, I was feeding full range 0-255 RGB32 to this PS script so if <16 and >235 were harmed, this would show...and it does not, that's my point. It's virtually identical to the 0-255 RGB32 test pattern that was fed to ddcc().
Last edited by leeperry; 23rd November 2012 at 12:56. |
23rd November 2012, 12:09 | #15698 | Link | |
Registered User
Join Date: Jan 2004
Posts: 567
|
Quote:
__________________
Bye |
|
23rd November 2012, 12:22 | #15699 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
Quote:
Once again falling into final stage fine-tuning but having MadVR perform a benchmark and auto selecting a preset would be quite cool. Last edited by ryrynz; 23rd November 2012 at 12:26. |
|
23rd November 2012, 12:34 | #15700 | Link | |||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
If you want to really test whether BTB and WTW are cut with EVR with default settings, just apply the following 2 scripts after each other, with no other scripts: (1) "16-235 -> 0-255", (2) "0-255 -> 16-235". Then feed RGB with a gray scale. If BTB and WTW are cut, the darkest gray you should get is 16,16,16. If BTB and WTW are not cut, you should get 0,0,0. And this is exactly what happens with EVR on my PC. EVR produces 16,16,16. madVR maintains the full range down to 0,0,0. Anyway, as I said about a dozen times now, and as I have already said right in the very v0.85.0 release notes, the levels custom shaders run in are still under discussion. So it really doesn't make much sense to discuss it here in the forum now. Quote:
Quote:
- ISpecifyPropertyPages - IVideoWindow - IBasicVideo - IBasicVideo2 - IKsPropertySet - IVMRMixerControl9 - IQualProp - IMFGetService -> IDirect3DDeviceManager9, IDirectXVideoMemoryConfiguration There might be some more supported by the Microsoft base classes madVR is building on, but I don't think so. If media player devs need more MS interfaces than those listed above, I'm willing to put that on my to do list. |
|||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|