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 March 2014, 22:17 | #24321 | Link |
Registered User
Join Date: Nov 2013
Location: Wales
Posts: 37
|
Buggy on current NV drivers, ah I see. Thank you both.
Downgrade to driver 327.23, ah that's not so easy when your main computer is your games rig as well as your video-hdmi player. I'll have to wait for a fix then. Has Nvidia acknowledged the problem yet and given a time frame for fixing NNEDI3. |
5th March 2014, 22:19 | #24322 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Acknowledged yes, but you will never get a time frame out of big companies like that.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
5th March 2014, 22:32 | #24324 | Link |
Registered User
Join Date: Mar 2013
Posts: 101
|
Thanks - I had been using 1.3.10 (also have 1.3.12 but it is flawed and crashes MPC-HC) 1.4.1 works just fine - I have it enabled as a "post resize shader". BTW: Anyone expecting obvious razor sharp results need to look elsewhere - this shader is very subtle using the defaults when applied to good quality 720P being upsized to 1080P.
|
6th March 2014, 00:15 | #24327 | Link | |
Registered User
Join Date: Mar 2013
Posts: 101
|
Quote:
Under "Color & Gamma" I don't "enable gamma processing" because I hadn't selected "disable the GPU gamma ramps" under "Calibration". It seems to me that with both selected you may well be working one against the other..no? |
|
6th March 2014, 00:16 | #24328 | Link | |
Broadband Junkie
Join Date: Oct 2005
Posts: 1,859
|
Quote:
Here I've uploaded a modified nv_disp.inf (English) & nv_dispi.inf (International) x64 which adds support for GTX 780 Ti to 327.23. Overwrite the inf file in C:\NVIDIA\DisplayDriver\327.23\Win8_WinVista_Win7_64\[International|English]\Display.Driver\ and install as normal using the Setup.exe one directory up. Inf mods such as this strip WHQL certification, so standard rules apply for installing non-WHQL drivers on 64-bit Windows. Last edited by cyberbeing; 6th March 2014 at 00:23. |
|
6th March 2014, 00:19 | #24329 | Link | |
Registered User
Join Date: Jan 2007
Posts: 33
|
Quote:
Regardless, thanks Madshi for all that you do for us, and how well you manage all the various opinions and personalities that participate in this thread. I'm constantly amazed at your calmness and rationality!! Keep up the good work! |
|
6th March 2014, 00:29 | #24330 | Link | ||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I only meant to say you should *not* get a 6xxx generation AMD GPU or older. Get a 7xxx generation GPU or newer. Quote:
Quote:
Yes, most. But not all. Take any interlaced source, after deinterlacing it becomes 60p, after scaling to 4K it becomes 4kp60 which is very GPU power consuming. Quote:
Quote:
Quote:
Thanks! |
||||||||||||
6th March 2014, 00:54 | #24331 | Link | |
Registered User
Join Date: Apr 2009
Posts: 1,019
|
Quote:
|
|
6th March 2014, 01:17 | #24332 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
As far as I understand what they saw in 8-bit was not flickering, but a higher noise floor. The higher noise floor is independent of whether the movie framerate matches the display refreshrate or not. I can see the higher noise floor even if framerate and refreshrate match. The flickering only occurs if there's a framerate/refreshrate mismatch. So these 2 things have different causes. Which means that changing the dither pattern for every VSync refresh at 8-bit would neither help reduce flickering (because flickering doesn't exist at 8-bit in the first place) nor would it reduce the noise floor. So it would serve no purpose.
|
6th March 2014, 01:32 | #24333 | Link |
Registered User
Join Date: Dec 2013
Posts: 753
|
Oh, so the dither pattern didn't actually change every frame when smooth motion was enabled? Well, that solves the mystery of why enabling smooth motion didn't actually help to prevent 'blinking'. Anyway I agree that this 'flickering' probably doesn't occur with 8-bits, and if it does then I can't say for certain whether changing the dither pattern every vsync will actually help. Although it would make all frames equally wrong.
|
6th March 2014, 01:37 | #24334 | Link |
Registered User
Join Date: Feb 2014
Posts: 162
|
Here's the result of R9 290X
This is the result of upscaling to 1440 with a H.265 encoded video, rendering time is 10-30% longer with bluray, ouch! If you are upscaling to 4k expect the time to be even longer. I also tried to "maxed out" MadVR with 256 neurons in both luma and chroma doubling, as you can see, it answered my question of why madshi decided to stop at 256 and not go higher. :P If graphics card performance doubles every two years, then in 5-6 years you can upscale to 1440 with 256 neurons without frame dropping, for 4k maybe in 7-9 years? Maybe in eight years the high end will be 8k instead of 4k, who knows? Last edited by seiyafan; 6th March 2014 at 02:01. |
6th March 2014, 03:16 | #24338 | Link | |
Troubleshooter
Join Date: Feb 2014
Posts: 339
|
Quote:
As has been mentioned before on this board using LAV hardware acceleration can lead to faster ms rendering times. Do you like, or use Smooth Motion with madVR? During my testing of using different LAV video hardware decoder options I found that I'd get dropped frames somewhere along the way (in some cases not until 6 or 7 minutes of video played) if I had Smooth Motion enabled in madVR and any of the hardware decoding options selected in LAV. I've concluded that my video playback is smooth enough without Smooth Motion enabled on my system, and that I'm not a fan of the blur effect that smooth motion adds to some moving objects when its enabled. If you like using Smooth Motion then you should probably set the LAV hardware decoder to none. Next thing to consider is the power of your CPU and GPU. The more powerful your GPU the more benefit you may see from selecting a hardware decoder. If you have a strong GPU and weak CPU then using hardware acceleration may be the better choice. On the other end of that if you have a strong CPU, but a weak GPU then you may be better with none selected as software will be used, and thus more of the load will be passed to the CPU. Some Nvidia users seem to prefer to go with one of the DXVA2 options over NVIDIA CUVID because they say CUVID turns the GPU on for 100% of the time CUVID is being used while DXVA2 can fluctuate the GPU usage. If your using a laptop/notebook and viewing your videos while running on the notebooks battery then you'll probably want to run it with one of the DXVAs (or None) instead of CUVID. If you have a noisy fan or cooling system then likewise you may want to choose DXVA2 or None. If you're watching your videos while plugged into an electrical outlet, and you have a quite fan/cooling system then why not let the GPU kick up to full power. I found in my testing of watching one video with CUVID set to do LAV Video hardware decoding that I had a consistent 5.51ms rendering and 1.51ms present while viewing. While running with the DXVA2 and none options I saw it steadily creep up from 5.56ms to an ever increasing number as video playback continued (22+ms 2 and a half minutes into viewing with DXVA2, and 16+ms at the same point with None selected ... a bug in the readings perhaps...). If you're using a system that is using an AMD or Intel then you don't even need to consider CUVID. Like most people on this board you'll probably want to experiment and see what gives you good speed while also providing stability and freedom from glitches during video playback. What works best on one system may not be the best settings on others.
__________________
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. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|