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. |
13th February 2014, 16:00 | #23061 | Link | |
*****
Join Date: Feb 2005
Posts: 5,647
|
Quote:
madVR should of course still respect the size requested by the player. Doing padding instead of resizing could be beneficial for quality (and performance). It could be a "Trade quality for performance" option to do padding when size difference is <16 pixels in both dimensions.
__________________
MPC-HC 2.2.1 |
|
13th February 2014, 16:06 | #23062 | Link | |
Registered User
Join Date: Oct 2011
Posts: 204
|
Quote:
|
|
13th February 2014, 16:11 | #23063 | Link | |||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Would still like to hear your feedback. If you don't have time to test all the builds, at least I'd love to hear your opinion about how nl1 and nl6 compare, because those are the 2 builds mentioned most often by other users. |
|||
13th February 2014, 16:20 | #23064 | Link | ||
*****
Join Date: Feb 2005
Posts: 5,647
|
Quote:
Quote:
__________________
MPC-HC 2.2.1 |
||
13th February 2014, 16:48 | #23065 | Link | |
Registered User
Join Date: Sep 2012
Posts: 47
|
Quote:
Maybe setting 7 bits is a good compromise? In any case, it might be worth a try as well for those on 6 bits + AFRC displays. At least, try all the options. edit: I tried it and setting 6 bits and 7 bits looks worse at least on the display I used. There's just too much difference between the pixels. Maybe the more appropriate solution would be dithering with even higher noise, allowing values like 10.4 -> 12 sometimes? I don't know if that's of much interest in general. Last edited by trip_let; 13th February 2014 at 17:13. |
|
13th February 2014, 17:28 | #23066 | Link | |
Registered User
Join Date: Dec 2013
Posts: 753
|
Quote:
Edit: After thinking about it you may need to divide by a value slightly larger than 2 or 4 to completely prevent 'out of range' values like 128 or 64 but it should still be quite easy to do error diffusion for 6 and 7 bits. Last edited by Shiandow; 13th February 2014 at 18:59. |
|
13th February 2014, 19:09 | #23067 | Link | |
Registered User
Join Date: Mar 2013
Posts: 101
|
Quote:
All AVIsynth off. MadVR at default settings except Chrome Upscaling=Jinc 3 tap, Image Upscaling=Jinc 3 tap. Play video full screen (with NL1 and NL6) and navigate to frame 1420 of each. Full screen capture (Alt+Printscreen). Open in editor, 200% zoom and cropped the upper left corners (1920-1440, 0-405). Performed this twice to insure conformity of process. What I discovered was that NL6 is noticeably sharper while NL1 provides 'smoother' dithering. See attachments (hopefully). edit: Darn..second capture runs 225KB. Using smaller crop. nl1a-frame1420 nl6a-frame1420 Last edited by MistahBonzai; 13th February 2014 at 19:51. Reason: external image links |
|
13th February 2014, 19:35 | #23069 | Link | ||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
|
||
13th February 2014, 20:25 | #23071 | Link | ||||
Registered User
Join Date: Feb 2014
Posts: 19
|
As always, all input is appreciated.
Quote:
(I certainly understand that it is a kludge based on what giant corporations have decided they are willing to do.) Between the monitor, the GPU, the GPU driver, GPU software package, other Windows drivers & APIs, media player, video filters, audio filters, video renderer, you really need a pre-existing "scorecard" to know what asks for what (and that is without extra complications like Reclock). Quote:
It turns out that Jriver has a bug whereby it displays a checkmark next to "100%" when "Fit Window" is also checked, so a casual glance indicates that the former is in effect, when it is actually the latter. But, actually, I don't want to manually set it to "100%" only for these corner cases, so it is a moot point. (In fact, manually checking each file with MediaInfo before playing, and then manually changing settings during playback, is contrary to the whole point of profiles - and software in general - which is to automate complex tasks.) Quote:
Quote:
|
||||
13th February 2014, 20:53 | #23072 | Link |
Registered User
Join Date: Oct 2013
Location: Sweden
Posts: 128
|
I used the 16-bit "gradient-perceptual.mkv" at the specific frame of "59, 29.970" and clipped the histogram at 4.
A random dither and a non dither version is included as comparison. nl? testbuilds The blurred version is blurred by paint.net, gaussian blur, radius 2. nl? testbuilds blurred I vote for NL6. |
13th February 2014, 20:56 | #23073 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,926
|
Quote:
just take things as they are or you have to read a lot... |
|
13th February 2014, 21:19 | #23074 | Link | |
Registered User
Join Date: Dec 2013
Posts: 753
|
Quote:
I think it's worth a try to see if dividing all values by 4, performing error dithering, and then multiplying all values by 4, improves the image for people with 6-bit panels. |
|
13th February 2014, 21:22 | #23075 | Link | |
Registered User
Join Date: Oct 2011
Posts: 204
|
Quote:
P.S. Just to clarify: Before, I would also have chosen NL6, I just wasn't too certain if it was objective enough. |
|
13th February 2014, 21:55 | #23077 | Link | |
Registered User
Join Date: Dec 2013
Posts: 753
|
By the way I was wondering, in the random number generator:
Quote:
The random number generator I wrote has the same 'bug' by the way, I divided by 2147450880.0f (0x7fff8000) which should be 2147483648.0f (0x80000000). |
|
13th February 2014, 21:55 | #23078 | Link | |
Registered User
Join Date: Jan 2014
Posts: 51
|
Quote:
|
|
13th February 2014, 22:24 | #23079 | Link | |
Registered User
Join Date: Feb 2014
Posts: 19
|
Quote:
Thanks ! |
|
13th February 2014, 22:45 | #23080 | Link | |
Registered User
Join Date: Mar 2013
Posts: 101
|
Quote:
The odd thing was that I performed the tests twice - once cropping a 480*405 of each of the 2 and again with 282*405 and both exhibited the same size and sharpness differences. What appears to have happened is that avisynth in ffdshow raw was activated. but I can't believe it did so 2x during the tests. After performing the retest I discovered that avisynth was active..so I suspect all the retest was done with avisynth active. However I see the file sizes (and appearances) are a far better match than the 1st 2 images (NL1a and NL6a). Once again my sincere apologize. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|