madVR - high quality video renderer (GPU assisted)

[Klaus1189]

why did you switch back to 399.xx?


But I am not a Nvidia user anymore for two years now

:rolleyes:


What are the HDR issues with 4xx.xx?
I think the following posts help:
Anyone try 411.70 yet to see if the HDR issues have been resolved? I'm downloading it now.

EDIT: Nope....still a broken mess for HDR. How nice. Back to 399 I go.

Can confirm HDR passthrouh doesnt work with nVidia 4xx.xx drivers on my 1070ti.
Maybe this has something to do with it

This driver release supports the Vulkan VK_EXT_swapchain_colorspace and VK_EXT_hdr_metadata extensions allowing applications to output HDR content to HDR displays via the Vulkan APIs.

Tested again, doest't work.

Tried HDR switch in Windows, it works.

Switching back to 3.99 for now.

Nvidia 4xx.xx triggers HDR properly only in fullscreen exclusive mode for me.

[mclingo]

windows 1809 update / MADVR AMD cards.

WORKING -

- HDR switch works as usual
- 3D switch works as usual (with FSE on as usual)


ISSUES (neither necessarily related to 1809)

- black screen with total HDMI loss coming out of 3D playback to 4k desktop using MADVR refresh rate switching
- over-saturation of colours, mainly reds with SDR 23hz (only) playback - HDR playback fine.

The oversat problem was fixed for me after installing latest MADVR in combination with latest AMD drivers, this didnt work this time, however calibrating for BT2020 display in MADVR still fixes this. I've fixed this before by installing drivers so I thinking this is something do with my system as only one or two other people seem to have this issue

[brazen1]

I don't think those posts help?
I don't have a broken mess for HDR?
Passthrough is no problem here?
"Tested again, doesn't work" means a lot of nothing to me?
I agree, HDR doesn't switch unless using FSE but I always use FSE.

Other than those, that's it?
There is a lot of badmouthing nVidia going on.
Maybe it's the AMD vs nVidia stock price that's really the issue?
Anyway, using the newest nVidia driver as of today and so far so good.
Note, I did modify the new installer with an earlier audio driver and the audio is working perfectly too.
3D frame packed MVC perfect switching.
UHD HDR mode switching perfect in FSE, not windowed.

[Klaus1189]

Not badmouthing!

Nvidia users have problems with their cards, me too with a 1080Ti one year ago, when I tested a new high end Nvidia card for me. The cards are not bad but the driver has major issues, that you can‘t talk away.
I am ready to pay 1k for a new Nvidia but it has to work as good as my current AMD which gets bashed all the time by so called experts/nVidia fanboys. I am not a AMD fanboy but I like it because it works like it should and every optional update is working fine, too.

[SamuriHL]

For me, the issue with the 4xx drivers is that I use windowed mode in madvr and HDR does not enable. madshi has contacted nVidia about the issue and hopefully we'll see a fix in an upcoming driver. I'm certainly not bad mouthing nVidia, however, I do consider HDR a mess with the 4xx driver for the above reason. Not a big deal to go back to 399.

[brazen1]

Not a big deal to use FSE either. I don't consider it a mess? Why do you need fullscreen windowed so bad that you would roll back the driver instead of simply switching FSE on? I was using windowed too. Just turned FSE on and I'm off and running. I use profiles for everything. Rendering too. I always use FSE for 3D so it's enabled in its profile. So now I've enabled it for the 2160p profile as well. FSE is still off for everything else. I don't think there is any detriment? I've heard others claim going into FSE makes their screen flash and therefore increases the time until the title starts. Except your display is going to flash when it goes into HDR mode anyway so no additional panel phasing time is occurring. Any other reasons FSE is a no, no other than rumor has it Windows may depreciate it some day?

[Asmodian]

Good point, we even have an "HDR" trigger for profiles now so you could even have FSE only for HDR content. All my 4K content is HDR and all my HDR content is 4K so this is moot for me. I will have to create a profile for rendering now. Thanks. :)

[SamuriHL]

For me, FSE is a non-starter. With my chosen player, going in and out of FSE is more than a simple flash. It actually takes time and can sometimes cause issues. Not that I do this during a normal watching, but, any mouse movement at all to get to a menu or to pause or anything like that takes time to switch modes and sometimes messes with my player. OTOH, once HDR is enabled, it's enabled...and doesn't switch in and out like FSE. It's a personal choice as to what works for each person and what workarounds you're willing to live with. For me, it's not really a problem to stick to a working driver until it's fixed in a new driver. Once it's fixed, I'll have no issue upgrading and won't have to set up profiles and deal with FSE issues in my setup. That's the beauty of madvr and why so many of us use it....there are MANY options available to us to configure it how we like. That power and flexibility doesn't exist anywhere else.

[mi3gai4rui4]

(3) And the ever popular Audio Video sync for common refresh rates such as 23.976 f/ps leads to dropped frames without creating custom timings.



Hi brazen1, can you please link me to instructions how to create custom timings to work around this issue?
I think I'm seeing it.
Or I'm seeing both A/V sync issues and stuttering video issues, I'd like to try this custom timings thing.

[gfxnow]

Hi, I realize I might be beating a dead horse but in my mind the possible benefit to implementing G-sync/Freesync support would be not having to change display modes (either manually or automatically). Freesync will match the display's refresh rate to the renderer's output, whether that's 24 fps for film, 30 fps for tv recordings, 60 fps for gopro footage... etc.

Now that Samsung TVs are also supporting Freesync it is relevant to the home theater crowd and not just a gaming monitor thing.

[huhn]

https://forum.doom9.org/showpost.php?p=1271416&postcount=2

feel free to send him one and don't forget the API.

and there a not many screens that work with 24 hz or lower even through for video rendering there is an easy workaround.

[jerryleungwh]

I see some comments saying we should choose 10 bit RGB instead of 12 (although it's not yet an option for nvidia users) because 12 could introduce banding aftee dithering, may I ask is that the case for Tv that supports 12 bits colors too? It says on the properties page in madvr that my TV can handle 12 bits, so will I get banding problem if I'm using 12 bit RGB full range or should I switch to 10 bits when it's an available option?

Sent from my SM-G9350 using Tapatalk

[huhn]

every none entry TV supports 12 bit input.

nvidia does not provide 10 bit for RGB when using HDMI because "reasons".
if your screen can't deal with 12 bit properly you may end up with banding but it's only the fault of your TV.
madVR doesn't change it's dithering based on that option.
i don't see a reason to send 12 bit if 10 bit is available but in the end it all depends on the quirks of your screen.

[mkohman]

The post is here: https://forum.kodi.tv/showthread.php?tid=223175&pid=2769562#pid2769562Thank you so much..

Sent from my moto g(6) using Tapatalk

[khanmein]

@mclingo AMD no issues & now guess what? :sly:

[creativeopinion]

@madshi

I don't want to turn this thread into nvidia topic but I would appreciate if you or someone else could clarify one thing for me. I'm using madVR custom resolutions and I've been told a while ago that the last driver that supports that is 390.65 but since then there are a lot of new releases. Since you have your nvidia contact I assume this was discussed as well at some point. Can you advise what's the last version that works with madVR custom resolutions? Currently I'm able to get '1 frame drop every 2 days' or even 'no frame drops/repeats expected' so I would hate to lose it by updating and not knowing if I still will be able to set this up.

I realize some drivers can introduce other problems so if someone can advise which one has the least amount of them + supports madVR custom resolutions that would be very helpful.

[madjock]

@creativeopinion

You will not get the answer you want. Not because there are no answers out there, it all is very subjective.

For example, if you do not have any issues, and you do not have any frame drops, why would you want to change ? I am guilty of this as well as I feel as though I am missing out, but the reality is, this computer is just for HTPC and browsing, so always roll back to 399.xx.

Some people have working custom resolutions with later drivers, but other things break, or don't.

The simplest reply is it all depends what you want to do, what graphics card you have, rev of Windows, but if it is working for what you want it to do, my advice would be leave it as is.

[khanmein]

FSE is working again with 1809.

[mytbyte]

I'd like to thank Madshi for the new option (finally) in calibration section to report BT.2020 to display (good for 4K non/HDR content and displays that are not HDR but support BT.2020) and it works.

The only gripe would be that one cannot apply the change if you check/uncheck only the option. If you select BT.709 you must also uncheck "report BT.2020" at the same time or you won't be able to do it if you only change to BT.709 and forget to change "report BT.2020". It's just a hassle, not a deadlock.

[jespermart]

Just recieved my new RTX 2010 ti card and has suddenly no frame packed 3d in madvr only side by side. Thought it might have something to do with the new Windows 10 build 1809, so I reverted back to my old Windows 8.1, but it's exactly the same, what the f**k are going on??? :confused:

Nvidia driver version are 411.70

Anyone else???

[Ver Greeneyes]

The 411.xx drivers have some issues. I guess you can't use older drivers on the new RTX cards, so you might just have to wait for a fix from Nvidia.

[mclingo]

Just recieved my new RTX 2010....?

BRAZEN1 is the Nvidia 3D expert on here, he should be able to help if he's about.

[VenomousNinja]

Nvidia has just released new Driver 416.16 WHQL with fixes for recent Win 10 1809 build. http://us.download.nvidia.com/Windows/416.16/416.16-win10-win8-win7-desktop-release-notes.pdf

[mclingo]

Nvidia has just released new Driver 416.16 WHQL with fixes for recent Win 10 1809 build. http://us.download.nvidia.com/Windows/416.16/416.16-win10-win8-win7-desktop-release-notes.pdf

are you still on win7, or is your sig just out of date mate?

Was just wondering what works in win7 now as I have an old machine I might put in my bedroom which I didnt upgrade to win 10 when I should have.

[madjock]

are you still on win7, or is your sig just out of date mate?

Was just wondering what works in win7 now as I have an old machine I might put in my bedroom which I didnt upgrade to win 10 when I should have.

You constantly say you are aware of messing up a thread, but you cannot seem to help yourself from doing it every day ?

Where do you think this conversation will go, what works on Windows 7 ?

:D

[mclingo]

fair play, yes i'm trying to get this kind of thing over to the other thread but also mend some bridges around here, at last for those who are willing to meet half way.

I meant what works in MADVR for windows 7, dont think this is an unreasonable question and I gave a reason for asking it. I would have asked it on the general thread if he'd gone there with that information.

:)

[AngelGraves13]

Nvidia has just released new Driver 416.16 WHQL with fixes for recent Win 10 1809 build. http://us.download.nvidia.com/Windows/416.16/416.16-win10-win8-win7-desktop-release-notes.pdf

Too bad the driver isn't WHQL signed and won't load once installed.

[Warner306]

Can you advise what's the last version that works with madVR custom resolutions? Currently I'm able to get '1 frame drop every 2 days' or even 'no frame drops/repeats expected' so I would hate to lose it by updating and not knowing if I still will be able to set this up.

I realize some drivers can introduce other problems so if someone can advise which one has the least amount of them + supports madVR custom resolutions that would be very helpful.

Any driver version should work or potentially can work with custom resolutions. If you aren't playing video games, there should be a good reason to upgrade your drivers if everything is already working correctly. Doing it just to have the latest drivers typically doesn't achieve anything.

[Warner306]

Hi brazen1, can you please link me to instructions how to create custom timings to work around this issue?
I think I'm seeing it.
Or I'm seeing both A/V sync issues and stuttering video issues, I'd like to try this custom timings thing.

http://madvr.com/crt/CustomResTutorial.html

[creativeopinion]

Any driver version should work or potentially can work with custom resolutions. If you aren't playing video games, there should be a good reason to upgrade your drivers if everything is already working correctly. Doing it just to have the latest drivers typically doesn't achieve anything.

I don't believe that is correct. I remember I've tried the latest driver that was released at the time back in April I think. I spend literally 3 hours trying with different pixel clocks and I'm sure you can imagine how annoyed I was getting my TV flashing every few seconds in order to check if the pixel clock has been accepted. I couldn't find one that would work.

Then, my friend has advised me that someone on this forum confirmed that nvidia did 'something' and that the last one that works with madVR CR is 390.65. I've installed it on the same day and I was able to find the correct pixel clock after like 2 mins without any problems. I just tested few different ones to get the best results and currently this vary from few hours/days to even no frame drops/repeats expected.

Now If i would aim to update my drivers I would like to make sure this can still be something I could set up. If I can benefit from newest drivers when it comes to HDR and other things I would like to.

[Warner306]

It works for some people and not for others. It seems like almost any driver version that doesn't work for one person works for Asmodian, and it would work for others. Cleaning your drivers between upgrades increases your chances of success.

[madjock]

@creativeopinion

Ok then, so how do you expect to get an answer when no one knows your Card Type, OS Rev and what you are trying to do.

If you go back a few pages you will see brazen1 has a massive list on what works and does not work for him with multiple drivers.
https://forum.doom9.org/showthread.php?p=1853608#post1853608

Nvidia have kept breaking things, they did a fix recently that was supposed to help the 23.976, this seemed to help some, but most of us cannot get a custom resolution to stick, others use CRU, others can get it to work with no problems.

MS have also broken things with updates, no one knows how, but these are also factors as well.

So what I said is correct, it all depends on what you have, your luck and what you want out of the driver reference HDR/FSE and the likes, the best thing is try yourself.

[brazen1]

@Warner306

I've been using drivers from roughly Oct 2017 with no problems. I agree about there is no need to upgrade drivers if you aren't having a problem. Then I read here newer drivers slowed down the amount of frame drops indicative of nVidia… that there is attention and improvements underway. I have always been aware that a frame drop occurs every 4.35 minutes. Personally, I am not sensitive to a single frame drop every 4.35 minutes unless I am watching my equipment instead of the movie.

Although I've tested custom resolutions provided by madVR, I've really had no use for them, again because I'm not sensitive to them especially at a 4.35 minute interval. Any more frequent, and I might be. That said, I'm an enthusiast. I strive for perfection without dedicating more to that than actually using the fruits of my labor(s). I prevented myself from upgrading drivers and pursuing further perfection simply because EVERY new driver to date offered, inherited a new audio problem that the old driver I'd been using didn't have. Yet that improved audio/video sync mismatch was always on my mind.

I decided to alter the newest driver installation package so I could enjoy the audio bug free and gain the benefit of newer video drivers with the claimed less frequent frame drops a couple days ago. In my case, updating was a success and well worth it... sort of. In my observations, the 4.35 minute interval remained unchanged. That was until I played Avatar in 3D frame packed. It went from 4.35 minutes, using my previous driver build, to 13 minutes exactly using the newer. This may not sound like much improvement to you and probably others, but to me, it's an advancement well worthy of the update. It also gives me confidence that further improvements might actually be possible given the decades there have been none.

I'm not trying to shoe-horn in another nVidia comment. I'm pointing out that one may think remaining stagnant with their setups, drivers in this case, may not be the best course of action and am just sharing my scenario why I say that. Had I not known the possible benefits updating provided by posts here buried long, long ago, I would still be using those old drivers unknowingly. The same could be said for any drivers, updates, or upgrades for any software or hardware so don't think this is 'specific' about nVidia. I'm sure there are many followers here keeping up with day to day comments and remember most of what they digest. But there are many who don't know the history let alone the details and come for specific hands on attention often relying on those that have previously already digested for them. You are one of these respected people and thought my words here worthy of your contemplation.

[Thunderbolt8]

as soon as I set highlight recovery strength to anything else other than 'none' my picture turns black & white. does anyone know why?

using madVR 0.92.17 hdrMeasure3 test build (but I already had this problem with earlier versions as well). rest of my setup --> signature

[Asmodian]

It works for some people and not for others. It seems like almost any driver version that doesn't work for one person works for Asmodian, and it would work for others. Cleaning your drivers between upgrades increases your chances of success.

I had been having good luck in the past but I am unable to automatically switch to a custom resolution for 23.976 Hz with 416.16 and Win10 1809. I also tried DDU in safe mode and a clean install.

I can add and optimize a 23 Hz mode if I do it immediately after adding it with madVR. Nvidia calls it a custom 24Hz mode as usual but now when madVR tries to switch to it I get the stock unmodified 23 Hz mode instead of the custom one. :(

I notice that when madVR first adds the mode it shows up in the Nvidia control panel under "PC" but after changing back to 60 Hz and reopening the control panel it shows up as a mode under "Custom".

Edit: If I add a custom mode in the control panel, and change to it manually, I can use madVR to optimize it but, again, I have to apply the optimization values manually. Even if I get a custom 23 Hz mode saved that Nvidia calls 23 Hz, when madVR asks the drivers for 2160p23 I get the stock 23 Hz mode (which I could no longer manually switch to in the control panel). If I manually switch to the custom one after that I still get the correct custom refresh rate. It is like the API madVR uses to change the resolution and refresh rate ignores custom modes completely now.

[blaubart]

Since W10 1809 HDR Flag switching is insane to dead (GTX 960). You may switch to HDR through Win10 "Anzeige > HDR on" but before 1809 madVR was able to switch to HDR by Win10 "Anzeige > HDR off".
Some insane flashing while madVR trying to switch. It "nearly" seems to work..

Next issue extists since before 1809. While madVR is HDR switching my Samsung TV obviously is cut off the PC for a part of a second. This time is enough to force Windows to switch to a small "panic" resolution. After that all explorer windows are in the left upper corner, apps right down.. If I let Win10 switch HDR by "Anzeige > HDR on/off" this does not happen.

[alps006]

Wow! So many issues with Windows 10!!! I am glad I gave up Windows 10 and went back to 8.1. So far so good! Playback is really perfect as I have nothing bad to report.Thanks madshi for always recommending 8.1, it indeed is a good OS for HTPC.

[j82k]

It's not Win10 1809 causing the HDR switching problems but the new nvidia driver, which automatically gets installed with the 1809 update.

399.24 still working fine with 1809.

[madjock]

It's not Win10 1809 causing the HDR switching problems but the new nvidia driver, which automatically gets installed with the 1809 update.

399.24 still working fine with 1809.

Not here, I still have 390.77 after update, although I did have to enable Full range and create a custom resolution again.

[j82k]

I used the Win10 update assistant and when it was done I had 411.XX installed... :angry:

[ryrynz]

Yeah I knew that was going to happen so I've decided to keep myself on 1803 on the HTPC for a while until madshi's Nvidia guy can sort out those driver issues.

[mclingo]

The Dark theme is quite nice for night viewing and to minimize possible burning in on OLEDs but your're not missing anything otherwise, the next update might be more interesting though as its going to have android mobile mirroring.

[alps006]

If you guys have a dedicated, problem-free HTPC and not being used for other purposes, the best thing is to refrain from updating it.

[mclingo]

I think most people on here have a usable system but have an small issues somewhere they'd like to fix, this is why whenever a new driver or relevant update is released there is often an itch that just has to be scratched and you end up going through the rigmarole all over again, then winding back :)

Thats me unfortunately, but I do spend 99% of my time actually watching movies and 1% dealing with issues which is propably contrary to how it seems :)

New LAV is out.

https://files.1f0.de/lavf/LAVFilters-0.73.exe

[mrmarioman]

Just installed the latest Windows update (1809) and the latest Nvidia drivers (416.xx). And HDR behaviour hasn't changed for me: Nvidia is still broken but Windows' HDR works fine.

[blaubart]

Just installed the latest Windows update (1809) and the latest Nvidia drivers (416.xx). And HDR behaviour hasn't changed for me: Nvidia is still broken but Windows' HDR works fine.

Same here but I won't roll back but wait for future improvements. The HDR thing is only tested. Normally I do the Win10 Upgrade half a year after release, this early one was an accident manually upgrading 1709 skipping 1803..

[Warner306]

I had been having good luck in the past but I am unable to automatically switch to a custom resolution for 23.976 Hz with 416.16 and Win10 1809. I also tried DDU in safe mode and a clean install.

I can add and optimize a 23 Hz mode if I do it immediately after adding it with madVR. Nvidia calls it a custom 24Hz mode as usual but now when madVR tries to switch to it I get the stock unmodified 23 Hz mode instead of the custom one. :(

I notice that when madVR first adds the mode it shows up in the Nvidia control panel under "PC" but after changing back to 60 Hz and reopening the control panel it shows up as a mode under "Custom".

So custom resolutions finally failed on you. I've had the same behavior on two occasions and had to change drivers. I wonder if it is the driver itself or something in the operating system that causes this to happen. I don't upgrade very often because it doesn't seem worth gambling that the whole process will fail. At least there are now dozens of drivers with HDR support to choose from.

[Asmodian]

The 2080 Ti is a lot faster for madVR. ;)

I see a bit over 40% for 1080p -> 2160p with NGU very high upscaling. :D
More tests to follow.

[ryrynz]

Highest quality madvr achievement unlocked. Can you notice a difference between high and very high though? :)

[JayeDog]

I use kodi dsplayer with madvr. Dsplayer and madvr are in full screen windowed mode. Nvidia drivers 385.28.

When I exit hdr mode the dsplayer window is almost always resized to a small window on the upper left corner of the tv. Anyone know how this can be fixed?