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. |
![]() |
#31881 | Link |
Registered User
Join Date: May 2012
Posts: 445
|
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
![]() |
![]() |
![]() |
#31883 | Link |
Registered User
Join Date: Nov 2009
Posts: 1,009
|
okey okey, looks like my appreciations are not welcome here (for some unexplained reasons -right KhR0N1K?, right Ver Greeneyes?, right madshi?-) nonetheless it's my ONTOPIC opinion, so please, everyone, stay ontopic.
|
![]() |
![]() |
![]() |
#31884 | Link |
Registered User
Join Date: May 2012
Posts: 445
|
If you don't think your post sounded condescending, you should learn some language comprehension. But sure, I'll stop feeding the troll.
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
![]() |
![]() |
![]() |
#31885 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,716
|
What a pure trolling. I suggest to completely ignore him.
Well, hopefully a more constructive opinion: In image doubling, maybe it should be named "double luma axis resolution" etc.? E.g. in games rendering, you usually refer to the total amount of pixels when having a multiplicator. Of course you can define doubling the one way or the other, but giving a hint that it's meant for each axis sounds like a compromise to me that should make fans of both types content. Maybe it would reduce confusion, as image doubling options are probably not easy to understand when you are new to madVR. |
![]() |
![]() |
![]() |
#31886 | Link |
Registered User
Join Date: Jul 2015
Location: Seattle, Washington
Posts: 53
|
Hi everyone,
This is my first time posting on the forums but I've been following this thread and reading threads on the forum for a few months. First off, thank you so much for all of your work madashi. You and the other developers on this forum helped awaken my interest in film and home theater playback. With that out of the way, I have a few questions regarding madVR:
Sorry for the laundry list of questions but I'm really appreciative of everything on this forum. |
![]() |
![]() |
![]() |
#31887 | Link | |
Registered User
Join Date: Dec 2011
Posts: 180
|
Quote:
2. edit: nvm thought you said SVP, that wont make a difference. 3. people are working on it 4. does not matter ~~ most of the stuff go back to "judge with your own eye". |
|
![]() |
![]() |
![]() |
#31888 | Link | |
Registered User
Join Date: May 2012
Posts: 445
|
Quote:
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
|
![]() |
![]() |
![]() |
#31889 | Link | ||
Registered User
Join Date: Jul 2015
Location: Seattle, Washington
Posts: 53
|
Quote:
2. So I can keep reclock set to original speed? 4. Considering the render times are noticeably different, I would think that it does matter. My question was more about why they would be slightly different though rather than should I set d3d11 on or off. Judging things for myself is good advice but I always go mad whenever I see people write about how they can notice huge differences in various options while I can't see any. Gives off the feeling that my eyes are broken. Quote:
On the note of GPU paths: This might have to do with an optimus issue but plugging in my laptop to my TV results in extremely high render times unless I restart my system. Despite render times being higher than the frame interval though, there are no visible dropped frames nor does madVR report dropped frames or presentation glitches. Last edited by Akeno; 17th July 2015 at 20:06. |
||
![]() |
![]() |
![]() |
#31890 | Link |
Registered User
Join Date: Feb 2014
Posts: 139
|
These are mostly my opinions, but I think the gist is mirrored by many others in this thread:
1. A good number of IPS displays are not true 8 bit and use static dither built into the logic of the display to "upscale" from 6 bit to 8 bit. Sometimes it'll look better if you set the display bitdepth for dithering to the true (6 bit, if applicable) depth of your monitor, sometimes it looks better at 8, and this depends entirely on your own configuration. You may need to test this empirically on your end. Usually you want to feed a monitor 8 bit info (even if it's 6 bit) because the dither levels decided by madvr may be different from your monitor, which can cause way more noise than necessary. Unless you know for sure your monitor supports 10 bit color or higher (almost nothing does in a laptop), don't go higher than 8 bit. Chroma quality differences in live-action film are going to be very hard to distinguish on any monitor unless you are trained well in what to look for. The best way to visualize differences is to try to find pure colors (red is best) on pure black background. Credit rolls and opening logo scenes are best for this. Otherwise, you can set chroma to nearest neighbor and look for the heavily aliased areas to identify places in the image where a chroma upscaler makes a lot of difference. As a sort of related tidbit, since it's hard to tell the difference between chroma upscalers, many people like to get some performance back by setting the upscaling to bicubic 75 AR. 2. Smooth motion should works just fine with 23.976->60. At least, it does for me. However, if you're able to test with reclock on and off already, it won't hurt to try and see what you like better. IIRC, reclock does cost a noticeable chunk of computation time, so it may be worth it to skip it and use some more obviously visible madvr features if you're bottlenecked by your laptop hardware. 3. I have no idea how the math of the current SuperRes algorithm works, and it's still very much in testing. IIRC madshi said that he'll be replacing those numerical entries with presets at some point in the future. 4. D3D9 and D3D11 are the same as the DX9 and DX11 that you see for games. They can enable new features, but by themselves shouldn't cause any differences in an image result. D3D11 needs a newer GPU (which you probably have if you have an IPS screen laptop) and enables 10 bit output. Otherwise, it really doesn't matter if you use D3D9 or D3D11. Go with whichever one runs faster unless you need 10 bit output for a 10bit or higher screen. Edit: RE: your TV plugging issue: Probably some sort of OSD bug, where madvr gets confused about the stats when dealing with switchable graphics. If you don't see frame stuttering or weird jumping, it really shouldn't matter what the stats say. TBH, madvr support for laptops and switchable graphics isn't quite perfect (intel + AMD in laptops has been reported to not work with openCL or nnedi3) so just report whatever bugs you see and move on. Last edited by har3inger; 17th July 2015 at 20:12. |
![]() |
![]() |
![]() |
#31891 | Link |
Registered User
Join Date: Jul 2015
Location: Seattle, Washington
Posts: 53
|
Thanks for the information, har3inger. I didn't know about the display bitdepth. Is it true even though the iGPU settings state that the monitor is 32bit?
For chroma upscaling, is this true even for CG or anime material? I personally can't see any difference even with extremely colorful and simple anime material unless I push it up to something like 4x zoom. Regarding smooth motion: a personal preference, but I prefer to use smooth motion with a 60hz display rather than switching the refresh rate to 24hz. The judder is just too obvious at 24hz and smooth motion alleviates it slightly. I suppose an alternative would be to use SVP but I don't know how resource intensive it would be. |
![]() |
![]() |
![]() |
#31892 | Link |
Registered User
Join Date: Sep 2013
Posts: 919
|
D3D9:
![]() D3D11: ![]() *Sorry for the huge pics. Shouldn't they shrink like on some other forums? As you can see, I have a 30% faster rendering time with d3d11, if d3d9 is the base. Or a 44% slow down with d3d9, if d3d11 is the base. This is in P8 state (GTX660, 324MHz both gpu and memory clocks). D3D11 definitely got faster in the last few releases. When the GPU is in P2 state or full clock speeds, the rendering times are less than 4ms on both. d3d9= 3.7ms d3d11= 3.4ms
__________________
System: i7 3770K, GTX660, Win7 64bit, Panasonic ST60, Dell U2410. Last edited by James Freeman; 17th July 2015 at 20:33. |
![]() |
![]() |
![]() |
#31893 | Link |
Registered User
Join Date: May 2012
Posts: 445
|
Interesting! Well, I'm certainly not going to complain.
__________________
Test patterns: Grayscale yuv444p16le perceptually spaced gradient v2.1 (8-bit version), Multicolor yuv444p16le perceptually spaced gradient v2.1 (8-bit version) |
![]() |
![]() |
![]() |
#31895 | Link | |
Registered User
Join Date: Feb 2014
Posts: 139
|
Quote:
The chroma differences are more obvious with crisp edges in anime or CG works, but again, hard to discern unless you know exactly where in an image to be looking. A lot of chroma information is well obscured by the luma channel, as it's supposed to be. Better scaling generally shouldn't give you more vivid colors, but more accurate edges between colors and more accurate saturation in thin or small bits of color. Go with a recommended algorithm like jinc3, bicubic75AR or super-xbr 100 if you're in doubt. ![]() 24 hz material (or 23.976, difference should be unnoticeable) on a proper 24 hz display should be perfect and theoretically better than 60fps and smooth motion. If you're seeing judder, something is not working like you're expecting in your setup. May as well just stick with smooth motion because it's so amazing. The only artifact smooth motion introduces is very slightly increased ghosting from motion in a scene/camera pans. You'll find a lot of the answers to questions here basically come down to "I dunno, play around with the settings and pick something you like best. After all, you're the only one you're deciding settings for" ![]() Force GPU clocks to max for mpchc through CCC if you can. You might need to rename the mpchc executable to something else for this to work (I had to--ATI is stupid and locks certain applications to lower power states or iGPU and takes away user control). You can also try turning off hardware decoding (DXVA) in LAV filters. This tends to lock clocks for AMD gpus to lower clocks as well. In general, GPU power states are entirely controlled by your OS and GPU driver settings and how they handle your video player (NOT madVR, which runs inside the vid player). There's likely nothing madVR can do to force certain GPU power states, so unfortunately, don't expect support here if troubleshooting doesn't work. Last edited by har3inger; 18th July 2015 at 00:04. |
|
![]() |
![]() |
![]() |
#31897 | Link | |
Registered User
Join Date: Jul 2015
Location: Seattle, Washington
Posts: 53
|
Quote:
Unfortunately, my TV doesn't support any interpolation settings when connected to a computer. I'd like to try out the cineflow options on it like what another user has posted but oh well. On a side note: What's the bilateral option? I remember madashi saying it works well on some content but horrible on others. |
|
![]() |
![]() |
![]() |
#31898 | Link | |
Registered User
Join Date: Jan 2014
Posts: 94
|
Quote:
However, it is still a madVR issue. I highly doubt madVR is at fault here, however, there clearly is a compatibility issue with my setup: madVR needs performance, desperately, but fails to reserve just that... Bottom line: How do I fix this? |
|
![]() |
![]() |
![]() |
#31899 | Link |
Registered User
Join Date: Oct 2012
Posts: 5,979
|
reinstall the driver and delete everything that can change or control the clock of your GPU there are so many possibilities.
after that try to rename your mpc-hc exe. BTW. your screen shows a huge issue with the buggy and most likely windows 7 desktop composition. |
![]() |
![]() |
![]() |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|