madVR - high quality video renderer (GPU assisted)

[tp4tissue]

Originally Posted by SamuriHL

madshi's response in that nVidia thread is troubling. If there's no "windows api for hdr" that he can call to enable/disable hdr and nVidia removes their deprecated api that's going to leave us in quite a bind when it comes to new drivers. Awesome....sigh

Doesn't he also say nvapi is not going away ?

[iSeries]

Originally Posted by tp4tissue

Doesn't he also say nvapi is not going away ?

It may or may not be going away but it's definitely not working as we'd want it, really just looks like it merely hands HDR control over to Windows.

The good news is, 398.11 seems to work perfect. Custom res works great too. I haven't tested anything after this, but apparently this is the last driver that doesn't have this bogus metadata issue.

[nevcairiel]

Originally Posted by SamuriHL

madshi's response in that nVidia thread is troubling. If there's no "windows api for hdr" that he can call to enable/disable hdr and nVidia removes their deprecated api that's going to leave us in quite a bind when it comes to new drivers. Awesome....sigh

Even if the MS HDR API doesn't have a "toggle" function (I didn't check), informing windows about the wanted HDR metadata might still be quite reasonable.

[SamuriHL]

Originally Posted by nevcairiel

Even if the MS HDR API doesn't have a "toggle" function (I didn't check), informing windows about the wanted HDR metadata might still be quite reasonable.

That's a good point. Windows might internally decide "uh, hey, that looks like HDR maybe I should turn that on". Then again, it might just ignore it until the user enables it in the CP. One never knows with windows. The one thing we DO know about windows is that it's not likely to be consistent between versions.

[RXP]

Thanks j82k for doing the measurements. Feel much happier and more confident that I downgraded.

I used to be a pure dedicated media guy since 2008/09. Prior to the Popcorn Hour I was so frustrated in using a HTPC for media playback. But MadVR's tempted me back into the HTPC game again. And this reminds me why I went to a dedicated player - it's a minefield of compatibility issues. I downgraded to the correct drivers for HDR passthrough but that broke CUDA playback as I was getting macro blocking. Eventually figured out I had to switch to DXVA Copy back but in the middle of a movie which I was looking forward to and never ended up finishing. Instead I shouted at the computer haha. On the positives I fixed the HDR tone mapping on the OLED, got Rec2020 output in SDR for my RS49 though.

I'm planning on creating a "production/live" system which I will use as a dedicated HTPC. I won't apply any software/driver updates to avoid this situation happening again. But I'm sure Win 10 will get very upset and try and install updates behind my back.

[madjock]

Originally Posted by RXP

I'm planning on creating a "production/live" system which I will use as a dedicated HTPC. I won't apply any software/driver updates to avoid this situation happening again. But I'm sure Win 10 will get very upset and try and install updates behind my back.

I know what you mean. I think the part I struggle with, is that things can just change with nothing having been altered to change it. I had my Qs rock steady during testing of files by reducing them for 4K content. Watched a file last night and I had over 28 Presentation issues and it sort of ruined the film as I could see the flashes.

This latest HDR metadata issue has also freaked me out as it was not really mentioned when everyone talks about the latest driver still allows passthrough etc, but it has obviously raised its head again and has been broken for months, you then find out your life has been a lie for all this time.

[tp4tissue]

Originally Posted by madjock

it has obviously raised its head again and has been broken for months, you then find out your life has been a lie for all this time.

This is exactly how I feel.

Recalibration also takes forever..

Wish there was a faster probe than i1displaypro that I can afford.

[chros]

Originally Posted by RXP

I'm planning on creating a "production/live" system which I will use as a dedicated HTPC. I won't apply any software/driver updates to avoid this situation happening again. But I'm sure Win 10 will get very upset and try and install updates behind my back.

You can block them from Win10 Pro and upwards.

[madjock]

Originally Posted by chros

You can block them from Win10 Pro and upwards.

I thought I would give 8.1 a go the other day, as it is recommended by madshi and others as a more stable OS. By god did I have problems, a lot were due to having a dummy 2nd display due to using the DP port for audio to my AVR.

Simple things like Text looking terrible and general DPI issues made me rethink in no time and back to Windows 10, for all of W10 faults sometimes when you do go and revisit an OS, you remember that it was not as good as you remember especially with advances in 4K displays and the like.

[RXP]

Originally Posted by madjock

This latest HDR metadata issue has also freaked me out as it was not really mentioned when everyone talks about the latest driver still allows passthrough etc, but it has obviously raised its head again and has been broken for months, you then find out your life has been a lie for all this time.

I think it shows that we don't really notice the minutia of detail. When you're engrossed in a film it won't matter if the highlights aren't recovered etc. I find it's almost like a Placebo kick for me. To know it's the best possible solution.

On a projector though it's a huge difference ofc.

I successfully watched a movie just now, looked amazing and very happy MadVR works. Now do I try and tweak the dropping frames every 4.73mins or do I just leave alone before I break something else

[j82k]

Originally Posted by iSeries

It may or may not be going away but it's definitely not working as we'd want it, really just looks like it merely hands HDR control over to Windows.

The good news is, 398.11 seems to work perfect. Custom res works great too. I haven't tested anything after this, but apparently this is the last driver that doesn't have this bogus metadata issue.

Yep 398.11 seems to be the last "correct metadata" driver. I just tried a lot of drivers after that and none had the correct metadata when playing 4000 nits content.
Gonna stick with that for now. I wonder what they messed up after 398.11.

[Charky]

Originally Posted by madjock

obviously raised its head again and has been broken for months, you then find out your life has been a lie for all this time.

Seriously, if that's the case, then it's not an issue.

A problem you can't see for months is not a problem.

[madjock]

Originally Posted by Charky

Seriously, if that's the case, then it's not an issue.

A problem you can't see for months is not a problem.

Yes this is a fair point. But you could also say that about most things we are trying to do with madVR. If it was a case of fire and forget I guess we would just use normal KODI with the built in Video player.

I think we are always striving to get things to look better whether that being a placebo effect or not, I think when you hear that others are doing A/B/C/D you give it a try to see if you can have the best you can get with the equipment you have.

Just makes it a little disappointing that things get put in the way that makes you doubt what you are trying to achieve really.

I probably speak for a lot if us when I say I mess more with the settings than actually watching full movies all the time, part of the joys and woes of tweaking things I guess.

[chros]

Originally Posted by RXP

Now do I try and tweak the dropping frames every 4.73mins or do I just leave alone before I break something else

I got 41 seconds with my laptop and I used it for years!

[angmav]

Hi sorry if this has been asked before but can someone point me in the direction on what Nvidia drivers to use and how to make Rgb 12bit 3840 *24hz using the latest version of win10 thanks no problem running ycbcr 12bit 4K


Sent from my iPhone using Tapatalk

[Klaus1189]

I beg Nvidia users to let me know the driver information which one to use, so I can update Nvidia section of the following thread to a true working one without any problems.
https://forum.doom9.org/showthread.php?t=176013

[madjock]

Originally Posted by Klaus1189

I beg Nvidia users to let me know the driver information which one to use, so I can update Nvidia section of the following thread to a true working one without any problems.
https://forum.doom9.org/showthread.php?t=176013

Well heres the problem, up to a couple of days ago I would have said a few of them were good, but the term "HDR passthrough" has taken on a new meaning now.

So as of today only 385.28 up to 398.11 are the only ones that seem to pass "HDR Passthrough and correct metadata" even then the ones between them I don't know if that is correct. But the two I have named seem to work in the last few threads ?

As I think was mentioned when you had the great idea with a separate thread, it seems to vary obviously between what people want, what equipment they have. some are happy to use Tone Mapping HDR-SDR and don't need the passthrough, or like the option of better framerate stability with newer drivers, or older drivers as its easier to make custom resolutions. So defining "good drivers" seems to be a minefield.

[Charky]

Originally Posted by madjock

I probably speak for a lot if us when I say I mess more with the settings than actually watching full movies all the time, part of the joys and woes of tweaking things I guess.

Yeah, I used to be like that when I first discovered madvr a few years back...

Now, tinkering for the sake of tinkering annoys me. I mostly focus on things I can actually see (mainly color accuracy, smooth playback with no dropped/repeated frames, no banding, and picture sharpening).

TBH, on my 55" LG OLED C8, at couch distance, i'm not sure I could tell the difference between a native 4K movie and an 1080p NGU upscaled one. So when I read posts from people claiming to see differences in real life content when they mess with dithering or chroma upscaling options, I'm kind of doubtful and wonder if they have Superman eyes and if they could really, really tell the difference in a ABX test..

But hey, this is probably blasphemy to write this in one of the most nerdiest topic on the Internet

[Klaus1189]

I agree madjock, I think I just list the feature(s) which do(es)n't work in the specific driver version, so the user can look up and use exactly that version because (s)he has a RTX card and doesn't use passthrough, so version XXX ist he best choice for her/him. Another user who want to use passthrough uses version XYZ because passthrough doesn't work in XXX.

[madjock]

Originally Posted by Charky

Yeah, I used to be like that when I first discovered madvr a few years back...

Yeah it does sort of get to be a chore, for example I thought I had everything setup with 385.28, I know from reading it has correct HDR metadata. I am playing 2160p to a 2160p screen, so only Chroma and I keep that to a minimum scaling since apparently its not that big a deal,

Took my Qs down as I noticed they were jumping about, all good rock solid, I have a 12bit RGB Custom resolution all good.

To last night watching a 4K rip and I was getting presentation errors, so that ruined that. Messed about today and I think its sorted again by using D3D11 Copy Back instead of Native....well till the next time, so yeah unsure if its due to the driver that I suddenly feel the need to use now I know metadata does not work correctly with as I was using 390.77, but always seems to be something.