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. |
1st January 2018, 20:05 | #48002 | Link |
Registered User
Join Date: Dec 2016
Posts: 212
|
Sorry if this has been covered before but the thread is huuge, the search found nothing.
I'm using HDR->SDR conversion via MadVR to a measured 180 nit monitor with cca 2.2 gamma...I have measured the post-MadVR gamma curve for it with a colorimeter, with "compress highlights" turned on...comparing it to the BT2084 curve, I find that the rolloff starts way too early, as low as 30% (10 nits) input while it should start at around 50% (or around 100 nits) since that's what color grading aims at as diffuse white. I know 200 nits peak brightness of an average monitor is not exactly HDR, but what I propose, there would still be 100 nits to do the rolloff and achieve more of the HDR effect...just a note: changing current options except turning off "compress highlights" made no difference... I'd like to encourage the Great Madshi to look into this and hopefully adapt the behaviour of the conversion. Thanks. Last edited by mytbyte; 2nd January 2018 at 10:52. |
1st January 2018, 22:23 | #48003 | Link | |
Registered User
Join Date: Nov 2013
Posts: 577
|
Quote:
"use Direct3D 11 for presentation..." is enabled or when "automatic fullscreen exclusive mode" is enabled in case of any source I have but "frame-packed" 3D sources. and of course frame-packed 3D rendering is only working as it expected when: "use Direct3D 11 for presentation..."is enabled and when "automatic fullscreen exclusive mode" is enabled, too. So for a stable workflow I need to create separate profile for 3D sources and everything else currently. I have to give up with 10-bit processing as well due to lack of feature Direct3D 11. Does anyone have some solution? Going back to a previous Nvidia driver would help? Or should I wait for a win10 repair/new driver from Nvidia? |
|
1st January 2018, 23:55 | #48004 | Link |
Registered User
Join Date: Dec 2010
Posts: 255
|
madshi, there's a few UHD titles that madvr doesn't correctly recognize the HDR properties. One such title is Planet Earth II UHD Blu-ray. It says "HDR, unknown properties." Another title I encountered this with is Terminator 2: Judgment Day. Maybe it's just a cosmetic thing, but it does correctly measure the peak values.
|
2nd January 2018, 00:43 | #48005 | Link | |
Registered User
Join Date: Jul 2014
Posts: 942
|
Quote:
Same for Life of Pi and the UK version of Dunkirk.
__________________
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 Last edited by Manni; 2nd January 2018 at 11:26. |
|
2nd January 2018, 07:13 | #48007 | Link | |
Registered User
Join Date: Aug 2005
Posts: 54
|
Quote:
You may need to check MadVRs screenshot options to make sure it's outputting the expected results (I believe there are options to use pre/post resize for example). |
|
2nd January 2018, 14:26 | #48008 | Link |
Registered User
Join Date: Nov 2013
Posts: 577
|
In case of "frame-packed" 3D source, is it the correct behaviour of madVR not to double the source to 4K, even though the display is 4K with the refresh rates and resolution and a "3D" profile's doubling algorithm set properly? I expected 2 pcs of 4K image being sent to the display.
Any help would be appreciated. |
3rd January 2018, 11:32 | #48011 | Link |
Registered User
Join Date: Jul 2017
Posts: 30
|
HDR10 conundrum
A happy New Year to everyone here and a conundrum regarding HDR10 for the new year…:
My setup: Windows 10 Enterprise 1709 64bit Zoom Player 14 madVR v0.92.10 -> set to 10bit and 0-255 and HDR metadata passthrough Nvidia GTX 980 385.69 -> set to 12bit and RGB Full Sony XD9305 TV (HDR ready) Test scenario A: Playing HDR10 demos (Exodus trailer and LG Colors of Journey demo) through madVR -> TV switches to HDR mode -> ok Playing HDR10 demos (Exodus trailer and LG Colors of Journey demo) through TV built-in video app -> TV switches to HDR mode -> ok CTRL+J shows the following information for both files:Test scenario B: Playing HDR10 movies (HDR10 according to their file names) through madVR -> TV doesn’t switch to HDR mode -> not ok Playing HDR10 movies (HDR10 according to their file names) through TV built-in video app -> TV switches to HDR mode -> ok CTRL+J shows the following information for both files:The movies first look washed out when playing through madVR. But when switching the TV manually to HDR, the colours seem to be fine (they look the same as when playing throug the built-in video app). Now to the conundrum (I hope you are still with me…):
Could it be that madVR somehow misinterprets the movies’ video data? Is there any other explanation for this behaviour? How can I tell whether the movie files are really HDR 10bit? |
3rd January 2018, 11:48 | #48012 | Link |
Registered User
Join Date: Dec 2016
Posts: 212
|
@Goeggel: you could post here the report generated from running your trouble files through Mediainfo software...we need to see what metadata are there in the file in order to help...just please omit the title of the movie from the report
Last edited by mytbyte; 3rd January 2018 at 11:58. |
3rd January 2018, 12:43 | #48013 | Link |
Registered User
Join Date: Jul 2017
Posts: 30
|
@mytbyte:
Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5.1@High Codec ID : V_MPEGH/ISO/HEVC Duration : 1 h 48 min Bit rate : 45.0 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 (Type 2) Bit depth : 10 bits Bits/(Pixel*Frame) : 0.226 Stream size : 34.0 GiB (76%) Writing library : ATEME Titan KFE 3.7.3 (4.7.3.1003) Default : Yes Forced : No Color range : Limited Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : BT.2020 non-constant Mastering display color primaries : Display P3 Mastering display luminance : min: 0.0000 cd/m2, max: 1000 cd/m2 Last edited by Goeggel; 3rd January 2018 at 15:57. |
3rd January 2018, 17:47 | #48015 | Link |
Registered User
Join Date: Jul 2017
Posts: 30
|
@mytbyte: As the metadata seems ok, why does madVR show "Matrix/Primaries BT.709 / YV12 8bit 4:2:0" for this movie and seemingly not passthrough the HDR info to the TV? Does madVR do SDR conversion in this case?
The Sony TV video app seems to be able to read the metadata correctly as it automatically switches to HDR. Thanks for the quick replies by the way! |
3rd January 2018, 19:13 | #48017 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Dolby Vision requires A LOT more than a "passthrough". Please, try keep these reminders down to once every half a year, at most.
__________________
madVR options explained |
3rd January 2018, 20:17 | #48019 | Link | |
Registered User
Join Date: Dec 2016
Posts: 212
|
Quote:
|
|
3rd January 2018, 20:25 | #48020 | Link |
Registered User
Join Date: Mar 2016
Location: Switzerland
Posts: 140
|
Stop this Dolby Vision spam bullshit in this thread FFS
Every single post : https://forum.doom9.org/search.php?searchid=8039934 STOP Last edited by Neo-XP; 3rd January 2018 at 20:48. |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|