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. |
24th September 2017, 13:01 | #45921 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,403
|
Quote:
Dolby Vision works properly with 12 bit RGB and the TV displays when it goes into Dolby Vision or HDR10.
__________________
madVR options explained |
|
24th September 2017, 13:40 | #45926 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Those screenshots are from complex profile setups. Does the same problem still occur with default settings without any profiles? Which media player are you using? E.g. Kodi's dsplayer may overwrite madVR settings, depending on how you've configured it.
The GPU is at the limit when the average rendering time gets near to the "frame" interval (e.g. 41.71ms for 23.976fps movies). |
24th September 2017, 14:52 | #45927 | Link | |
Registered User
Join Date: Aug 2017
Posts: 89
|
Quote:
Last edited by dvd1; 24th September 2017 at 14:55. |
|
24th September 2017, 14:53 | #45928 | Link | ||||
Registered User
Join Date: Jul 2014
Posts: 942
|
Quote:
Re 3, I always select the correct calibration manually given the poor HDR implementation in my display, so not an issue here, but I agree that with a display with a good HDR implementation that's another strong point for RGB. Quote:
I do use HDR passthrough, but the metadata stops with the Vertex so that the display doesn't switch automatically to its own poor HDR implementation. So the metadata is only used so the Vertex can decode and display it, then the Vertex "Disables HDR" i.e. doesn't send any metadata. For the display, it is receiving SDR, not HDR. But I apply my own BT2020/ST2084 implementation (using an ST2084 gamma curve made with Arve's tool and a BT2020 calibration) manually. I have tested this without anything in the way (direct connection from the GPU to the JVC) and I get exactly the same result, so it's not the AVR/Vertex. When I say Magenta, you have to understand that it's not a calibration issue. It's as if the only color available was magenta. So I get a black and magenta picture, as you wouyld get a black and white picture. The screen isn't fully magenta, I can still read what is displayed on the desktop or I can watch the video, it's just black&magenta. So not a calibration issue, or a wrong SDR/HDR mode issue. It's just a completely corrupted picture. It's not MadVR per se, when I send the desktop whith the OS HDR set to "off", all is fine. It just goes magenta if I set the OS HDR option to on, or if MadVR switches to HDR on the fly (as the OS HDR option is usually set to off). I think that my display is unable to accept that picture format, and when it's sent it goes in that magenta mode. What I don't understand is why it does that even when the Vertex kills the metadata, because in that case the display should think it's receiving SDR. But when in that mode, disabling HDR in the Vertex has no effect, the screen is magentified anyway. Quote:
Thanks, I'll add it to the list of displays accepting this. Quote:
I wouldn't expect Dolby Vision to work in 8bits, that's probably something that Dolby would forbid as it would cause too much banding for them.
__________________
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 |
||||
24th September 2017, 15:26 | #45929 | Link | ||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
The frame interval is shown in the Ctrl+J OSD. Look for "frame xxxx ms". Quote:
|
||
24th September 2017, 15:28 | #45930 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.92.4 released
http://madshi.net/madVR.zip Code:
* fixed: HDR metadata transport didn't always work with AMD GPUs * fixed: potential crash issue introduced in v0.92.0 * fixed: possible rendering slowdown issue introduced in v0.92.2 * fixed: custom mode warning windows sometimes appeared in background * added logging to help find why custom mode measurements aren't recorded * screenshotting now uses NGU High instead of Very High * screenshotting now has a 5 second timeout instead of 2 seconds * slightly modified user interface for Nvidia custom mode creation |
24th September 2017, 16:56 | #45931 | Link | |||||
Registered User
Join Date: Oct 2015
Posts: 29
|
Quote:
Quote:
The setting I am talking about is found under "Change resolution". The "Use default color settings" will provide the TV with RGB limited signal, where limited is "Limited" under "Output dynamic range". The "Use NVIDIA color settings" which lets you customize the output is the same as the default as long as I use RGB limited. Also, the black crushing x7007 is mentioning is exactly what is happening to me, it is like you reapply "Full" range, it is really weird. Quote:
Tested signal output from: 680 760 1080 Ti *With a fresh install on every single Windows 10 update. Have you tried a fresh install or DDU? If there are no mentions from others of this problem, maybe there is something else going on, I would try DDU (Display Driver Uninstaller) first and then a fresh install, I would never expect anything from NVIDIA's support, especially if it is not a widespread issue. Quote:
Quote:
Enhancements and video player tweaks are not activated anywhere on the control panel and all settings let the video player do its thing. Other such settings that exist on Intel's embedded GPUs I do not have since my processor does not have an embedded GPU, the only thing installed is the NVIDIA's graphic card. The utility you are mentioning is for forcing "Full" range but for the "Adjust video color settings" section right? I have set this to "With the video player settings" instead of custom. Wouldn't forcing another "Full" range make things even worse considering I have black crushing blacks like x7007 mentioned? |
|||||
24th September 2017, 17:02 | #45932 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,890
|
Quote:
GPU full means do nothing to the signal. GPU limited means take the full range signal and make limited out of it. the GPU always thinks the input is full range even with madVR at limited. |
|
24th September 2017, 17:06 | #45933 | Link | |
Registered User
Join Date: Jul 2014
Posts: 942
|
Quote:
As I said, it's not a metadata issue, the Vertex receives the metadata, decodes it, displays it on the OSD, then kills the metadata. The display never gets it. As far as the display is concerned, it's always receiving SDR, I am the one deciding which calibration should be applied (SDR REc-709 or HDR BT2020).
__________________
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 |
|
24th September 2017, 18:34 | #45935 | Link | |
Registered User
Join Date: May 2015
Posts: 225
|
Quote:
Filling your screen, you mean when you have no black bars? I don't understand if there is difference between standard black bars, and bars that is "part" of the movie... Btw, you mean xyVSfiler? Inviato dal mio ASUS_Z00LD utilizzando Tapatalk
__________________
Intel i5-4590 - MSI R9 270X 2GB - 8GB RAM |
|
24th September 2017, 20:15 | #45936 | Link | |
Registered User
Join Date: Jun 2007
Posts: 652
|
Quote:
As for the other question, for what concerns me the main problem with xyVSfilter is its unability to render subs at target resolution but rendering them at video resolution. This is a problem for SD sources. I use these rules: <subs videoaspect="1.33|1.66|1.78" filter="xysubfilter" /> <subs videoaspect="1.85|2.20|2.35|2.40" filter="directvobsub_(auto-loading_version)" /> This way I have xysubfilter in case where resolution might be low (1.33, 1.66) or where the screen is filled (1.78) and xyVSfilter (DirectVobSub) where I need to be sure subs are moved to the bottom of the screen and where I mostly (99%) have HD sources and so rendering at video resolution does not constitute a problem. I hope it's clear. If it isn't, PM me or write in the Kodi thread that's been opened recently. |
|
24th September 2017, 20:17 | #45937 | Link | |
Registered User
Join Date: May 2015
Posts: 225
|
Quote:
I'm going to look at it asap I use mpc be, you think it's the same? I'm on a 1920*1080 monitor, so filling the monitor videos are the ones with 16:9 aspect ratio? I'm not so good at it You think i've to edit something here for best use with my monitor? Talking about VSFilter, i installed it, and selected it in MPC BE, enabled at preferred DirectVobSub(auto loading) in External Filters, but when loading a file i don't see any icon an it's not in the list of active filters. What i'm doing wrong? I've all x64. EDIT: Selecting DirectVobSub instead of the auto-loading version, icon appears and filter is loaded fine. But i've the exact output i've with XySubfilter, subs are not in the black bars. Same result with the Internal Subtitle Renderer, subs are on the video, not below. Inviato dal mio ASUS_Z00LD utilizzando Tapatalk
__________________
Intel i5-4590 - MSI R9 270X 2GB - 8GB RAM Last edited by steakhutzeee; 24th September 2017 at 23:03. |
|
24th September 2017, 21:36 | #45938 | Link | |
Registered User
Join Date: Oct 2015
Posts: 29
|
Quote:
Having NVIDIA CP set to Full and madVR at Limited is what gives me as a final result "Full". If I change madVR or the TV to "Full" I will get blacks crushes further and further. You are suggesting otherwise and I cannot identify the source of the problem. |
|
24th September 2017, 21:37 | #45939 | Link | |
Registered User
Join Date: Jul 2014
Posts: 942
|
Quote:
This makes more sense (I understand why you were confused), what doesn't is that this metadata (which I do send usually so it can be decoded by the Vertex) isn't supposed to go past the Vertex, and most of it doesn't as my display doesn't switch to HDR automatically. If the metadata was sent, it would switch. I'm going to discuss this with HD Fury. Just to clarify, my normal MadVR config is HDR passthrough with Send HDR Metadata enabled (so the Vertex can read it and display it). It's good to know that if I disable the metadata in MadVR, I can get 4K60p GRB 8bits to display properly on the display, but I shouldn't have to do this with the Vertex. I'll keep you posted, thanks again for the suggestion. I've re-tested with the latest MadVR build but I have no reason to think that it's the new build that caused this difference in behaviour. One unrelated issue with MadVR: I have an NTSC DVD (Klute), ripped into DVD Folder, that doesn't render properly with MadVR. If I select EVR-CP, everything is fine (menus and film), but with MadVR the Warner Bros logo plays fine, then I only see the selecting line of the menu (not the menu options themselves), and no video at all (black screen) with audio when playing the film. I've tried other PAL and NTSC DVDs and I haven't found other titles behaving like this. I kown that earlier versions of MadVR used to work because I watched it a few months ago with MadVR and it worked fine. I couldn't say when it broke.
__________________
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 |
|
24th September 2017, 21:55 | #45940 | Link | |||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Anyway. I'm not 100% sure if the issue is with the Vertex. It could be. But it could also be a bug with the Nvidia GPU. In theory, when the Nvidia GPU is in HDR mode, all that should be different should be that the HDMI signal says "PQ" transfer function, and some SMPTE 2086 metadata. The actual pixels values and format should stay the same. But maybe the Nvidia GPU "secretly" also changes the pixel format? Maybe the GPU thinks that 60fps is too much for your HDMI connection and thus switches to YCbCr 4:2:0 or 4:2:2, but still reports RGB to the display? Or something weird like that. I don't really know, just some wild thoughts. Just wanted to let you know this, so you don't put the blame to 100% on the Vertex. It could be the Vertex, or it could be the Nvidia GPU/driver. FWIW, which "max pixel clock" does your EDID report? (See JVC identification tab in madVR.) Edit: You also have an AVR between HTPC and JVC, right? That one could also play a role. Quote:
It could be a bug in LAV or in madVR, it's hard to say for me. Can you upload a sample, so nevcairiel and I can both double check? |
|||||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|