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. |
23rd April 2017, 20:21 | #43461 | Link | |||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
1) Maybe your HDMI cable is bad. Try a newer/better one. 2) Maybe your GPU's HDMI output is broken. Try a different output port. 3) Maybe all your GPU's output ports are broken, you could try a different GPU. 4) Maybe your TV is broken. This problem does not seem to be madVR's fault, from what I can see. Quote:
FWIW, chip/memory frequency probably rise for a short time when switching window size or entering full-screen because madVR has to re-render the internal queue, and it does so as fast as possible. I don't consider this behaviour a problem. It works as intended. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I don't think it's a madVR issue. |
|||||||||
23rd April 2017, 20:28 | #43462 | Link | ||
Registered User
Join Date: Mar 2016
Location: Switzerland
Posts: 140
|
Quote:
Quote:
If the new target produces this change, it should at least be possible to add an option to disable it (scale in gamma light ?). Last edited by Neo-XP; 23rd April 2017 at 21:02. |
||
23rd April 2017, 20:30 | #43463 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR v0.91.9 released
http://madshi.net/madVR.zip Code:
* added support for sending HDR metadata via Nvidia's private API * added support for sending HDR metadata via win10 (not tested yet) * fixed: processing (not converting) HDR was not handling gamut correctly 1) It works in all OSs starting with Windows 7 (I think). 2) It works with both D3D9 and D3D11. 3) It's true "passthrough", the GPU driver doesn't modify the HDR pixels. BUT: It only works for Nvidia GPUs and requires a fairly recent GPU driver version. AMD/Intel users will have to use the new Windows 10 HDR APIs. I've implemented support for these, too, but couldn't fully test them yet, so they may work, or maybe not. Let me know. These APIs will probably behave differently compared to the Nvidia API. I'm not sure if they're true "passthrough". If they are, then probably only in fullscreen mode. These Windows 10 HDR APIs require the Creator's Update to be installed, and you need to activate "use D3D11 for presentation". |
23rd April 2017, 20:40 | #43465 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
You need a GPU which supports HDR output, in both hardware and drivers. That should be Pascal, Polaris and Kaby Lake. If you have an older GPU, you can still tell madVR to passthrough, but then you have to manually switch your TV into HDR mode.
|
23rd April 2017, 20:53 | #43466 | Link | |
Registered User
Join Date: Dec 2007
Posts: 128
|
Quote:
I hope you can look into this soon... |
|
23rd April 2017, 20:59 | #43467 | Link | |
Registered User
Join Date: Sep 2012
Posts: 174
|
Quote:
Do both nvidia and win10 metadata transfer the entire metadata from the file (so correct levels of White Point, min/max luminance, maxfall, maxcll etc)? Just triggering win10's HDR mode from display settings obviously couldn't set the correct metadata of the file you are playing (since win10 wouldn't be able to know it), but I assume you can set the correct values via API? Last edited by Q-the-STORM; 23rd April 2017 at 21:12. |
|
23rd April 2017, 21:02 | #43468 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Both APIs support the full set. maxfall and maxcll are not in the SMPTE 2086 metadata set, though, IIRC, but somewhere in the video bitstream. I'm not setting those two, but the others are set correctly by madVR, of course.
All that said, many TVs seem to totally ignore the metadata atm (other than HDR on vs off). |
23rd April 2017, 21:13 | #43469 | Link |
Registered User
Join Date: Sep 2012
Posts: 174
|
When the x265 encoding settings haven't been stripped, you can see maxCLL and maxFALL there, e.g. in mediainfo:
max-cll=1529,380 1529 is maxcll, 380 is maxfall it's between master-display and min-luma Maybe LAV could read those values and feed them to madVR? Also, is there any way to display the HDR infoframe for a file, so people can set it in HDFury's integral or Linker (so people with old GPUs can set the correct infoframe)? I have not found any program that can just display the infoframe for a file, you'd always have to calculate it. Since madVR is processing the values anyways, maybe you can display them somewhere? Last edited by Q-the-STORM; 23rd April 2017 at 21:37. |
23rd April 2017, 21:54 | #43470 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
madVR shows the HDR metadata in the OSD (Ctrl+J). I'm not sure if that's what you mean with "HDR infoframe"? Or do you mean the raw data? I'm not even getting that myself, it's read by ffmpeg, then transported to LAV, then transported to madVR, and probably converted several times in between.
I'm not sure if maxcll and maxfall are really needed to be sent to the display, but the APIs do support it. @nevcairiel, what do you think? Worth implementing? |
23rd April 2017, 22:53 | #43471 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
I can add it to the data set, but I'm not sure how many samples actually set it. FFmpeg already got patches to read it recently, so not very complex to do that.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 23rd April 2017 at 23:02. |
23rd April 2017, 22:53 | #43472 | Link |
Registered User
Join Date: Sep 2012
Posts: 174
|
We obviously don't know what exactly each display does with maxfall and maxcll.
When a frame is bright enough to trigger ABL on a display, the display will dim the image, now it would make sense that if maxFALL is high, a display that can't get that bright will use the metadata to simply be a bit dimmer at all times, so that the brightness will not suddenly have a big drop when average brightness of the frame is a lot higher than what the display can display. If the display compensates from the start, the image will be a bit darker over the whole movie, but in return, bright scenes can actually be brighter than dark scenes, because the display compensates from the beginning. And maxCLL could be used to determine how to roll highlights, so if the display can only do 700nits highlights and maxCLL is 800. it needs to roll highlights a bit so that everything over 700nits is not "just" blown out, but blown out with a curve... if maxCLL is 1500, this curve would obviously be different, since the display can roll the highlights a bit differently, to retain some more detail there. So maxCLL and maxFALL can be very important... "can"... but that's just theory on my part, they might not do anything with it yet, or they do something entirely different... though I would really be surprised if "UltraHD Premium" certified TVs don't use maxCLL and maxFALL in some way... so if it's not too hard to implement, I would definitely recommend it... the HDR infoframe is basically all the values in hex send to the display, it's what triggers HDR mode and how the metadata is transfered.... it looks like this: Code:
87:01:1A:A4:02:00:C2:33:C4:86:4C:1D:B8:0B:D0:84:80:3E:13:3D:42:40:E8:03:32:00:E8:03:90:01 so if you put this string in the integral/linker, it'll inject that in the HDMI stream and the display will get the metadata to process. Last edited by Q-the-STORM; 23rd April 2017 at 23:00. |
23rd April 2017, 23:02 | #43474 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,348
|
Quote:
https://github.com/Nevcairiel/LAVFil...f86d26217e12a3 Some of the test clips I have do even set it, and those claim to be UHD BD compatible encodes, so that sounds good, I guess.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 23rd April 2017 at 23:24. |
|
24th April 2017, 02:05 | #43476 | Link |
Registered User
Join Date: Apr 2012
Posts: 23
|
I dont believe this is a madvr problem but its something that happened. can i know what this means? It showed up in every video, im guessing its because its reading from a bad drive but not sure:
Only audio played and display was black. My worry is that even though the source of the problem is a bad drive, it did cause madvr to behave strangely for subsequent videos. Its working now again but for a time, this is the error i had. Last edited by dioxholster; 24th April 2017 at 02:08. |
24th April 2017, 02:18 | #43477 | Link | |
Registered User
Join Date: Sep 2012
Posts: 174
|
Quote:
|
|
24th April 2017, 03:02 | #43478 | Link | |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
Quote:
Sent from my Nexus 5X using Tapatalk |
|
24th April 2017, 04:21 | #43479 | Link |
Registered User
Join Date: Feb 2016
Posts: 1
|
Does anyone know why no matter what I do my MadVR Control Panel will not show up. When i click on the filter in my filters list on a video the popup says Change Settings and Show Tray Icon. Clicking either opens another process in my process list but doesn't do anything and the tray icon will not appear. I have tried re-installing windows as well as 3 different versions of madvr / Nvidia drivers
|
24th April 2017, 05:01 | #43480 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,650
|
Maybe try another player, mpc-hc for example and see if you have the same issue.
Madshi, the .ax files are quite a bit larger than in previous releases, zip is now 10MB larger. Not that it's a big deal but, what gives? Last edited by ryrynz; 24th April 2017 at 09:12. |
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|