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. |
4th January 2016, 19:55 | #34981 | Link | |
Registered User
Join Date: Jun 2009
Location: Stockholm
Posts: 28
|
Quote:
Changing to 10-bit for the monitor in madVR didn't help either. EDIT: Changing to DX11 is now rendering the video in FS as well. EDIT2: !!! Enabling "Activate SuperRes Filter" is what is yielding the sepia image. !!!
__________________
HTPC: Samsung 65JS9505, Yamaha A2070, Sonus Faber, RX580 |
|
4th January 2016, 21:30 | #34982 | Link |
Registered User
Join Date: Oct 2015
Posts: 99
|
Which would be more preferable and why (SD -> 1080p upscale):
- Double luma at NNEDI3 256 (no quadrupling) or - Use luma quadrupling at NNEDI3 32 and doubling at however high you can go with NNEDI3 (which would be significantly less than the 256 above, of course) Assuming in both cases the resulting resource expenditure is about equal, that is, near the absolute max available. Last edited by Uoppi; 4th January 2016 at 21:33. |
4th January 2016, 21:55 | #34983 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
Quadrupling doesn't make much sense in this situation since 576p or 480p doubled is already more than 1080p or almost as much.
Instead of using that many neurons, I'd suggest SuperRes. NNEDI3 is mostly very artifact free, but it can look a bit artificial. SuperRes can help a lot against this. e.g. try NNEDI3 64 doubling with SuperRes strength 2 or 3. You can also put a little of sharpen edges, enhance detail or Adpative Sharpen on top of that. |
5th January 2016, 01:37 | #34984 | Link | |
Registered User
Join Date: Oct 2015
Posts: 99
|
Quote:
So for SD -> 1080p upscale the "correct" way is to use doubling with the setting "only when scaling factor is 1.5 or more"? I think for 720p I've got it set at "always when needed". I use SuperRes (at 1 or 2) with NNEDI3 (32 and more) for all upscales. And I don't usually want any further sharpening (even the sharpness setting on my tv is at 0). Last edited by Uoppi; 5th January 2016 at 01:43. |
|
5th January 2016, 02:10 | #34985 | Link | |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
Quote:
I'd use super-xbr for quadrupling after NNEDI3 doubling in such situations then. Someone claimed here that it would look pixelated compared to pure NNEDI3 quadrupling, but I'm not aware of any proof for that. With my tests, I could hardly distinguish NNEDI3 64 doubling + super-xbr 75 quadrupling vs. NNEDI3 64 doubling + NNEDI3 64 quadrupling. SuperRes also reduces the remaining differences. |
|
5th January 2016, 02:30 | #34986 | Link |
Registered User
Join Date: Jun 2006
Posts: 350
|
I get dropped frames playing NTSC SD video (http://mir.cr/0JGNT9O8) on 30 Hz and no dropped frames playing it on 60 Hz. Also, I get dropped frames playing PAL SD video (http://mir.cr/0TO7HKQ7) on 24 Hz (with ReClock) and no dropped frames playing it on 50 Hz (and no such issue when playing NTSC HD video on 24 Hz).
HD5770 + Catalyst 14.4, WinXP SP3, MPC-HC 1.7.10.40, madVR 0.89.19
__________________
Windows 8.1 x64 Magically yours Raistlin |
5th January 2016, 18:08 | #34988 | Link |
Registered User
Join Date: Jan 2008
Posts: 589
|
Not entirely related to madVR, but wanted to share that the "UHD Premium" announcement might end up bringing order into the chaos that HDR currently is. Hopefully.
|
5th January 2016, 18:55 | #34989 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Quote:
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
5th January 2016, 20:10 | #34990 | Link | |
Registered User
Join Date: Oct 2015
Posts: 99
|
Quote:
So from what I can gather, it would indeed be a good strategy to use a moderate NNEDI3 count for doubling + Super-XBR for quadrupling (to kick in for higher upscales) INSTEAD of allocating all available resources towards maxing NNEDI3 doubling? I mean, I'm having a hard time spotting differences between 64 vs. 256 neurons anyway unless zooming up close. |
|
5th January 2016, 21:15 | #34991 | Link |
Registered User
Join Date: Sep 2006
Posts: 2,197
|
a question regarding range conversion. what is the recommendation here for a TV, set the graphic card to 0-255 and then let madVR do the conversion to 16-235? someone I know who has a Panasonic plasma TV says that when he does so, forcing the nvidia driver to output 0-255, and then setting 16-235 in madVR will leave whiter than whites (236-255) pass through and make 235, which is supposed to be white, darker. According to him the only way to get proper output with nvidia is to set the gpu to 16-235 and madvr to 0-255.
he made some pictures using the AVSHD calibration disc: madvr 16-235, GPU 0-255: http://someimage.com/TIY4nz2 madvr 0-255, GPU 16-235: http://someimage.com/uy1kWWj
__________________
Laptop Lenovo Legion 5 17IMH05: i5-10300H, 16 GB Ram, NVIDIA GTX 1650 Ti (+ Intel UHD 630), Windows 10 x64, madVR (x64), MPC-HC (x64), LAV Filter (x64), XySubfilter (x64) (K-lite codec pack) Last edited by Thunderbolt8; 5th January 2016 at 21:19. |
5th January 2016, 21:30 | #34992 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,903
|
depends on the screen setting.
madvr 16-235, GPU 0-255 and madvr 0-255, GPU 16-235 should result in the same output type (limited) which should look the same. so either the TV settings are changed or the screen act strange with a full range signal which doesn't make a lot of sense. or in "short" this should count: Quote:
|
|
5th January 2016, 21:31 | #34993 | Link |
Registered User
Join Date: Mar 2006
Posts: 567
|
Nvidia GPUs and drivers are able to properly output a full range [0-255] signal, it's Panasonic plasmas that used to not accept full range signals. I know this first hand, I had a Panasonic plasma myself. More recent models might no longer have this issue though.
So what your friend does is the right thing to do for him. He has to set his output to [16-235] in the GPU because his TV set would ignore the [0-16] and [235-255] range of values were he to send a full range signal [0-255]. This is option (2) in the quote from huhn's post. I do not agree that option (3) in huhn's quoted post is preferable to (2) for two reasons: one is that we don't use TVs to see movies only, but we also want the desktop, images, games and everything else to be displayed properly - and this is not what happens with option (3); and second, because from my experience the [0-255] signal is not properly interpreted by a TV which only expects [16-235] - the gamma or something else is not right, the image in movies does not look quite the same as when you use option (2). If you have a TV that accepts a full range signal, the best thing to do is to output full range from the GPU [0-255] and configure madVR to do the conversion from 16-235 to [0-255] as intended - that's exactly option (1) from the post quoted above. You need to look into the controls of your TV set to enable it to accept a full range signal though. How to do this varies from brand to brand and model to model. It may involve setting the input as a PC input, or activating some mode (like "Game"), or toggling some "black level" option. On my Sony TV, everything is properly working out of the box with its auto setting, the TV properly recognizes when the GPU sends limited range or full range signals. But if I were to force full range for an input, what I would have to do would be to set Display -> Video Input Settings -> HDMI Dynamic Range to "Full" for that HDMI port. In the past some TVs were not being able to accept a full range signal at all. Last edited by KoD; 5th January 2016 at 22:05. Reason: made the link between what I said and the quote in huhn's post |
5th January 2016, 22:10 | #34994 | Link |
Registered User
Join Date: Jul 2014
Posts: 942
|
This is just the press release, signatories of the UHD Alliance have access to the full specs.
__________________
Win11 Pro x64 b23H2 Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33 madVR/LAV/jRiver/MyMovies/CMC Denon X8500HA>HD Fury VRRoom>TCL 55C805K |
5th January 2016, 22:12 | #34995 | Link |
Registered User
Join Date: Sep 2006
Posts: 2,197
|
but they arent as you can see in the pictures. his TV only accepts 16-235 via HMDI.
__________________
Laptop Lenovo Legion 5 17IMH05: i5-10300H, 16 GB Ram, NVIDIA GTX 1650 Ti (+ Intel UHD 630), Windows 10 x64, madVR (x64), MPC-HC (x64), LAV Filter (x64), XySubfilter (x64) (K-lite codec pack) |
5th January 2016, 22:52 | #34996 | Link | |
Registered User
Join Date: May 2007
Posts: 454
|
Quote:
I have tv set to accept full RGB, NVidia driver to send full range RGB and madVR to send limited range (16-235)... In this setup whiter than white is sent (236-255) but blacker than black is not (0-16). If you however change madVR color range to custom and then select the range (16-255) madVR will then loose the whiter than white and the color range will be correct between 16-235 with the avshd tests. Its not logical but it works. Raz |
|
5th January 2016, 23:18 | #34997 | Link | |
Registered User
Join Date: Feb 2014
Posts: 16
|
Quote:
|
|
6th January 2016, 00:42 | #34998 | Link |
Registered User
Join Date: Jan 2014
Posts: 123
|
Using latest versions of madVR 89.19 and Emby for WMC (Windows 7 Professional). With MPC-HC 1.7.10 after refresh rate switching by madVR (windowed overlay mode) then video hangs and does not play. Video will play after closing then re-starting MPC.
Refresh rate switching when using MPC-HC 1.7.9 works with video playing fine after refresh rate switching. Has anyone else seen this, better still have a solution for it? I have also posted this in the MPC-HC forum as I suspect it is more of an issue with the latest version of MPC-HC than madVR. |
6th January 2016, 01:47 | #34999 | Link | |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Quote:
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
|
6th January 2016, 03:58 | #35000 | Link |
Registered User
Join Date: Sep 2006
Posts: 2,197
|
same RGB range question for my old AMD laptop. in the video settings under colour there is the setting dynamic range. the options here are full, limited or leave this option unticked. unticked appears to be the same as full though. not sure if theres really a difference here. I unticked all video & quality options in the AMD settings just to be sure drivers dont mess with the content. so should I leave the dynamic range option as well unticked or set it to full?
madvr: is currently set to display expects PC levels (default). with my panasonic plasma (VT60) I can choose HDMI range normal (default setting) or full. when I set it to full though then black becomes gray. but according to "(1) Display wants 0-255. GPU and madVR are consequently also both set to 0-255." setting it to full range should be right, shouldnt it? another thing: with my TV theres also an option called HDMI content type from which I can choose Auto (default), graphics, foto or off. which is the recommended setting here when watching movies? auto, graphic and foto look all the same, that setting is a little bit brighter than off. edit: I need to double check if I really read the RGB level values for my TV in madVR or my laptop screen, not sure any more. will do tomorrow.
__________________
Laptop Lenovo Legion 5 17IMH05: i5-10300H, 16 GB Ram, NVIDIA GTX 1650 Ti (+ Intel UHD 630), Windows 10 x64, madVR (x64), MPC-HC (x64), LAV Filter (x64), XySubfilter (x64) (K-lite codec pack) Last edited by Thunderbolt8; 6th January 2016 at 04:01. |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|