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. |
15th September 2012, 22:25 | #13864 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
That's why I don't have the 7970 anymore (I even had three different ones and all were more or less defect by hardware too *wtf*. )
Yup, madVR definitely gives rock solid playback performance now in FSE. With highered presented frames in advance, I can watch any kind of video without any dropped or delayed frame nor presentation glitch. |
15th September 2012, 23:25 | #13865 | Link |
Registered User
Join Date: Dec 2007
Posts: 652
|
What make/models look good?.... I'm no GPU expert but these seems to be similar in processing to a 550ti but with way less power consumption/heat output. I'd prefer those silent(ish) fan designs that dumps the heat out the back of the card.
|
15th September 2012, 23:25 | #13866 | Link |
Registered User
Join Date: May 2011
Posts: 94
|
Guys, I was just following your comments regarding Nvidia vs. ATI. I have always used ATI and currently I run a 7770. Playback has always been pretty solid I usually get about 15 drops frames when I start a movie but then I can watch the entire movie without any noticeable glitches. The only issue I have from time to time is with music playback, I get small drop outs (some time). I use MC17, LAV and madVR in FSE. I watch 1080p/720p exclusively and mostly rip Blurays 1:1 (no compression).
So, I was just wondering why many of you favour Nvidia over ATI? I don't think PQ will be different, is there something I am missing? |
16th September 2012, 02:29 | #13867 | Link |
Registered User
Join Date: Nov 2010
Posts: 80
|
EDIT: I apologize, I did not read far enough back, it looks like you definitely do know about this.
Has anyone else noticed that the new NVidia driver 306.23 contains the following? : "Media Player Classic Home Cinema displays a black screen during playback when using the MadVR video renderer. [960463]" Does anyone know what this means? (I obviously have not seen any issue so serious.) LOL and congrats on Madvr being under the radar of NVidia itself. EDIT: If the issue is involved with 0-255 colorspace/BTB/WTW issues, I have been pushing 0-255 to my Pioneer Kuro without any registry fixes with my NVidia graphics card. I thought I had the issues resolved a couple years ago or so and I was displaying the correct colorspace without any "black crush." Am I incorrect? For instance, do I need to run the new "tweaker" Madshi posted a few posts back? Last edited by Mikey2; 16th September 2012 at 02:42. |
16th September 2012, 02:39 | #13868 | Link | |
Registered User
Join Date: Nov 2010
Posts: 80
|
Quote:
http://us.download.nvidia.com/Window...ease-notes.pdf |
|
16th September 2012, 19:53 | #13871 | Link | |
Registered User
Join Date: Apr 2011
Posts: 141
|
Quote:
can madvr compensate for nvidas defualt tv-leveles setting? |
|
16th September 2012, 20:00 | #13872 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
If your TV expects the video in limited range, then you obviously don't need this tweak.
You can however still use it, and afterwards set madVR to TV levels. GPU in Limited Range/TV Mode: - Desktop still renders at full range, GPU compresses to limited range on output - madVR set for PC levels outputs 0-255 -> GPU compresses to 16-235 on output. GPU in Full Range/PC Mode: - Desktop renders at full range, GPU outputs as-is - madVR set to PC levels leaves the GPU as PC levels - madVR set to TV Levels, leaves the GPU as TV levels (the signal is 0-255, but madVR makes all video only use 16-235) In case your TV needs Limited Range/TV Levels, the second option may have slightly better accuracy in the colors, at the expense of your desktop being black and white crushed.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 16th September 2012 at 20:04. |
16th September 2012, 21:45 | #13873 | Link | |
Registered User
Join Date: Apr 2011
Posts: 141
|
Quote:
i think i figured out my tv has a hdmi black levels setting. so i can adjust what my tv epectrs i think. the question then is whats best? set gpu fullrange with the tweak and tv to exspecy that or go with limited? |
|
16th September 2012, 22:00 | #13874 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Go fullrange if your TV supports it. It results in less conversions being performed, so better image quality for all desktop, games and videos. Of course if your TVs HDMI black level setting is not implemented well, things could get screwed up again. So in the end you'll have to try both solutions and trust your eyes which looks better. Try the madTestPatternSource test patterns to check if you can see a difference.
|
16th September 2012, 22:19 | #13875 | Link |
Registered User
Join Date: Apr 2011
Posts: 141
|
kk thx.
yes the tv's blacklevel for fullrange is called normal. I guess sugetsting that the "lov" setting does some converting. anyway with the tweak enabled and black level set to normal the image looks the about the same as with no tweak and a setting of "low". the image was pretty darn good before but i guess i cant see much of a difference. it so annoying that tv manufatcures insist on using settings names like "contrast+", "motion plus" and "black level" with a normal and low settings. such names say nothing of what the settings actually do. dint know i had the abillity to choose full or limeted untill just now becouse of this. ah well. |
17th September 2012, 06:11 | #13876 | Link |
Registered User
Join Date: Nov 2010
Posts: 80
|
I just tried running the "Tweak" utility. I was on my 0-255 plasma and it went entirely blank. I had to do a hard-reset of my computer. It now displays properly; however, I notice no difference than before. (I have madVR set to 0-255 and my TV set to the same. Blacks are grey when madVR is set to 16-235.) Furthermore, when opening up the Tweaker, the "force PC levels" is still not checked.
Does this mean that the "tweak" did not take? As I mentioned before, I am not sure I needed it in the first place, but I guess it was a dumb question since no one responded. Well, I'll try again: am I ok as it stands right now? Boy I hate colorspace issues; they have been dogging me since I first built my HTPC! Thanks in advance for any help, MikeY EDIT: In conjunction with some research on this thread, is the "tweak" simply adding/setting the " SetDefaultFullRGBRangeOnHDMI " key (in My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B0823740-41FA-45D1-8D11-E547D5CED249}\0001 ) to 1? If so, mine is there and set to 1. EDIT2: My Mistake, that value is missing for my Plasma. (I know you said the Tweaker was based on the current monitor; I have three monitors and it was sensing the wrong set of registry keys. I do NOT have this value on my plasma, which is the only one I care about. Should I add it? Once I had this pointing to the correct key, the tweak did in fact work and the checkbox is now on (i.e. I can undo it.) I am still curious on its necessity though... Oh and I found this link: http://forums.guru3d.com/showthread....43#post4278943 I assume that the first post is the custom resolution that should not be necessary with this tweak? (And the linked post is what your tweaker tool does? I apologize that this post is pretty scattered; it is getting late and I keep finding out more as I go along. Last edited by Mikey2; 17th September 2012 at 07:46. |
17th September 2012, 08:26 | #13877 | Link |
Registered User
Join Date: Aug 2008
Location: the Netherlands
Posts: 851
|
Why not just change the .inf file (adding lines HKR,,SetDefaultFullRGBRangeOnHDMI,%REG_DWORD%,1?).
This is a one time procedure and no worries after that anymore. @Madshi: can we expect a totally new madVR version soon now that NVIDIA fixed the most important thing? Zou wel zwaar relaxt zijn! Last edited by THX-UltraII; 17th September 2012 at 11:03. |
17th September 2012, 11:45 | #13878 | Link | |
Registered User
Join Date: Sep 2006
Posts: 212
|
Quote:
So before you decide to remove that option please don't as us Optimus users seem still need that "Use a seperate device for presentation" option.... Cheers Last edited by andybkma; 17th September 2012 at 11:50. |
|
17th September 2012, 12:37 | #13879 | Link | |||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Ok, 6 months worth of replies, part I:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Nothing. If it looks better to you, you can use it. If your display is not perfectly calibrated, trying different gamma curves/values could help improving the image. If your display is perfectly calibrated, then using the power curves might be the more mathematically correct option. But it's still a matter of taste. The BT.709/601 curve simply has a different look to it. Quote:
Quote:
Quote:
Quote:
Quote:
IQ should be the same. Using NVIDIA CUVID or DXVA moves decoding from CPU to GPU. Whether that makes sense depends on which of those 2 is the bottleneck on your PC. Personally, I prefer software decoding, because it's been more stable and reliable in my experience. But then, if your CPU is a bit slow, or if you want to do e.g. AviSynth processing, moving the decoding to the GPU might make sense. I'd say just try both and use what works better for you. If both your CPU and GPU are equally fast, you'll probably not notice a difference either way. |
|||||||||||||
17th September 2012, 12:39 | #13880 | Link | ||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
The problem can occur if there's a cadence break and there's not enough motion in the middle of the screen for madVR to find the new cadence. When watching the full screen, of course there's more information to look at. Quote:
Quote:
Depends on whether you watch in the same lighting conditions all the time or not. If you watch in sunlight or with room lights on, using e.g. a pure power curve of 2.20 might make sense. And that's probably what you calibrated your display to? However, if you watch at night with all lights turned off, going to a gamma curve of maybe 2.35 might make sense. So if you want to switch between different gamma values to adjust for different lighting situations, turn gamma processing on. Otherwise turn it off. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Probably at some time in the future, but not soon. Quote:
Quote:
Makes sense. Maybe I should use the setting to the devices section, so you can set it per monitor? But then, probably nobody is going to look for that setting there! Hmmmm... Difficult... |
||||||||||||||||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|