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. |
30th May 2017, 00:06 | #43941 | Link |
*****
Join Date: Feb 2005
Posts: 5,643
|
There is also the option to use an older pre-WDDM 2.2 driver, like 378.xx.
And the custom resolution trick: http://forum.doom9.org/showthread.php?t=173571 |
30th May 2017, 00:35 | #43942 | Link |
Registered User
Join Date: Jul 2002
Location: Maryland
Posts: 52
|
HDR Playback, need some help
Can someone provide simple instructions on Window Settings and MadVR settings to get HDR to work.
I have a GTX 1080 TI, Windows 1703 and and HDR TV (samsung KS8500), 1. I can get Windows to display HDR if I select the silder to HDR, but then it is aloways in HDR mode no matter what I do, and everything looks like trash. 2. I can disable HDR in Windows, and then use mdavr, using DX11 Playback. I have passthrough HDR Content to the Display selected. 2a. Nvidia's private API 2b. Windows 10 API In both cases playing back of an HDR video such as "LG_Chess_HDR.mp4" or "Sony_4K_HDR_Camp.mp4", does not switch to HDR mode, according to the TV. The splitter is LAV and the decoder is LAV, so I do not see why madvr is not sending HDR10 data. I also have an HD Intergral inline so I can monitor what is happing and the Intergal in both cases shows I'm not passing any HDR10 data, so the TV seems correct. What am I doing wrong? ERIC |
30th May 2017, 08:27 | #43943 | Link |
Registered User
Join Date: Jan 2002
Posts: 1,264
|
I am having so much fun with HDR. It keeps getting stuck in that mode even though I turned it off in Win10. So SDR gets incorrectly tone mapped. If I switch from 10bit to 8bit in MadVR settings I can get it back. Either that are rebooting fixes it. But then I have to mess about getting HDR working again as it does not like switching to HDR without clicking on MadVR's system track icon, leaving it for a few seconds then clicking away. I hope this is fixable and not something Win10 or the driver is doing.
|
30th May 2017, 10:36 | #43944 | Link |
Registered User
Join Date: Apr 2013
Posts: 315
|
Using newest madvr 0.91.10 causing Potplayer to close really slow and start really slow, I can't click on movie instantly after closing potplayer, I can see potplayer going from 100+ mb of ram to 35mb and then close which takes about 4-5 sec, within this time it doesn't open another movie or the same movie cause I limited it to 1 instance of player. without using Madvr , just any other renderer , potplayer closes fast and opens fast. 0.91.9 worked properly without an issue.
EDIT : Nvm , it still happens with 0.91.9 , I figure it's the new update, he changed something for people who have crashes , might kind of timeout which doesn't close it instant. with version 1.7.1916 it works like it should. Still for some unkonwn reason, potplayer opens when the internet is disabled ! , can anyone figure out why !? it opens the movie instant without internet ( network adapter disabled ) compare to with internet takes like 2-3 sec saying it's opening ... Last edited by x7007; 30th May 2017 at 10:50. |
30th May 2017, 23:17 | #43950 | Link | |
Registered User
Join Date: Jun 2007
Posts: 652
|
Quote:
Depending on your screen, you might be better off implementing a custom resolution for 23.976Hz, because the screen might already be working "behind scenes" to multiply it in order to reduce flicker. |
|
31st May 2017, 00:07 | #43951 | Link | |
Guest
Posts: n/a
|
Quote:
1. Stock Win10 x64 RS1 + run Windows Update + NO TWEAKS + install latest NVidia drivers + install latest MPC-HC x86, LAV, madVR, ReClock = no issues with playback 2. Stock Win10 x64 RS2 + the same as above = severe frame-droppping with exactly the same settings. I did this comparison several times and you're wrong to say I am the only one. Windows 10 RS2 does bring significant changes to the way it treats video drivers, refresh rates, adds overlays and "Optimizations" to FSE. There is no way to get rid of it. Its integrated into the OS, most likely hard-coded into DWM.EXE. Just because you aren't getting the same problem does not mean it is not there. As I mentioned, I do not have this RS2 frame-dropping problem on all of my displays, just one of them, and the other 2 work the same way with either edition. It just happens that the one display that has issues with RS2 is my TV! |
|
31st May 2017, 03:16 | #43952 | Link | |
Registered User
Join Date: Jul 2016
Posts: 130
|
Quote:
|
|
31st May 2017, 08:25 | #43954 | Link | |
Soul Seeker
Join Date: Sep 2013
Posts: 711
|
Quote:
|
|
1st June 2017, 00:03 | #43960 | Link | ||
Registered User
Join Date: Jul 2011
Posts: 33
|
Returning to the issue of oversaturated colors of some videos on wide-gamut displays:
For the sample video, I made the following test: in the video player that was using madVR, switched to interpreting video as full range (via madVR shortcut) and made a screenshot in PNG. Then opened it in Photoshop and analyzed the values in the areas of these artifacts. Red areas were indeed oversaturated in R channel (highest R was 255), but G and B were less than 252 (and even less that 235 in green area), although R values were 0 (or close to zero) there. So, most of the visible problems are in areas with R not in range 16-235 (or even 1-254). Here is the captured frame: Photoshop_-_Color_Lookup_Table.mkv_-_00000.png Quote:
Anyway, does it really has any sense to have values 0 and 255 pass to 3D LUT then? |
||
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|