madVR - high quality video renderer (GPU assisted)

[Grimsdyke]

... , but will solve the problem with the duplication of frames.

It's been a while but IIRC what I did to avoid the repeated frames issue when watching old US-DVDs was to choose 'DXVA2 native' in LAV Videodecoder.

[Limberjork]

Try to use ivtc (https://drive.google.com/open?id=1ZW6kHaU1aXa87xBdimnX02DCceR9xOSn) (force film mode). It will not completely solve problems with combing artifacts in certain spots, but will solve the problem with the duplication of frames.

Yeah looks like this is the answer. I didn't realize that IVTC can't be performed in the automatic mode; I thought the deinterlacer would pick up on the need for it automatically.

[seiyafan]

Hi everyone,

I have made an optimized NVIDIA profile for MPC-HC/BE. Might be helpful for those who struggle with the configuration. Try it out.

This is NVIDIA Profle Inspector tool with a profile file and a .bat to import that profile.

Download (https://www.sendspace.com/file/ohoudl)

Most important settings it uses:
Power management mode = Adaptive
VSync = on
GSync = off
SLI = off
Prefer NVIDIA on Optimus systems

Thanks, your profile and 419.35 GRD fixed the issue on my 1660.

[ryrynz]

So it would seem like the VSync setting isn't being respected after upgrading or with certain Nvidia driver versions..

[jkauff]

A clean install will also wipe out any Control Panel settings.

[Sunset1982]

I will do a clean installation of my htpc the next days. Any suggestion which windows version i should use as a stable patform?

I have used Windows 10 build 1809 but had random freezes with madvr/kodidsplayer/lavfilters.

I have an amd rx vega 56 gfx card...

[Asmodian]

Windows 8.1 is still ideal for a madVR box.

[Sunset1982]

Windows 8.1 is still ideal for a madVR box.

Some time ago I read a post from madshi where he wrote some disadvantages of windows 8.1, but I can't find it anymore.

Wasn't there a problem with 10bit hdr and windows 8.1?

[madjock]

Not so sure about that, I think it is better as in the overlays side and other bits and bobs are supposed to be not as aggressive if thats the right word, maybe Exclusive is more Exclusive than 10 and the likes, sure HDR was much the same, but simple things like drivers, the Windows 10 ones are not compatible, so you have to try and find Windows 8.1 ones, and you are not sure if they are the same as 10 for issues.

A word of caution though, I thought the same as all I heard was it was better that 10 for this, but I have to say I only had 8.1 on for a matter of hours, a lot was to do with me having a fake monitor due to audio going to my AVR via Display Port, but my god it would not behave and it drove me mad with it jumping about to a fake disply etc.

I also noticed other things, that I cannot even remember now, simple things you take for granted in Windows 10 now, ultimately I put Windows 10 back on and all the problems vanished.

[huhn]

win8 can't do WFS 10 bit that's it FSE works totally fine.
madVR uses the API from nvida and AMD so the OS doesn't matter much for HDR what matter if there API are supported on other windows version then 0 which is still the case.

[Grimsdyke]

Hi Madshi, there were a few crashes since driver update to Intel-6618 related to the dll below.

callstack crc : $cc12cd00, $3d0d8150, $1a3e20d2
exception number : 1
exception class : Exception
exception message : Access violation at address $7ffe2a28b33d in module 'igd10iumd64.dll'. Write of address $4b886ce0.

[ryrynz]

That's all on Intel. Report it to them.

[madjock]

Is this not more of a Driver problem than a madVR one, multiple AMD/nVidia drivers have issues and everyone else rolls back or waits for a better driver ?

edit : ah beaten to the punch :)

[TheProfosist]

Alright so troubleshooting this has finally completed on my saga of trying to get reasonable video playback again after switching from a GTX1060 to a RTX2060


Trying to troubleshoot something. On my HTPC (Win10x64-1809v2, i7-4820K, 32GB ram, RTX2060, 4K HDR Sony TV) I cant seem to get pans to be smooth even though im withing the render times on a per frame basis. I can disable more things to lower it further and it doesn't seem to improve it. Yes smooth motion is on in the when needed but should be needed her 23fps content and display changed to 24fps. It doesnt show dropped or duplicated frames for how stuttery it is. Previously had the 1060 in there no real improvement going to the 2060.

Ideas on troubleshooting this would be helpful. I have tried:

using different decoders in lav filters. Anything other than CUVID just seems worse
MPC-HC versions 1.7.13 and 1.8.4
madVR versions 0.92.14 and now 0.92.17
upgraded the GPU
lower settings from NGU to superxbr to jinc
increasing buffer from 8 to 16 (though im not sure if 6GB vram is enough for this)

I have not completely wiped my madVR settings to see if it does it from scratch since I thought I would post here first to see if someone has ideas.

alright so I have made some progress I started by uninstalling, reinstalling, and reseting MPC-HC and madVR.

The stuttering has mostly been fixed I just get a little blip every now and then say every couple minutes at most. some time during fast actions or pans. I'm not using smooth motion just matching frame rate could this be buffer related? This seems more frequent than the 1 stutter every 4min or so that the madVR UI is suggesting.

I did fix exclusive mode as well.


both the stuttering and exclusive mode seem to have been related to having HDR enabled in Win10 at an OS level.


I have not yet tweaked scaling algorithms or anything like that yet. Just on default settings.



When playing back 4K HDR BD content I'm still getting stuttering on pans that should be smooth. This is with HDR turned off at the OS level and HDR set to pass through. Colors look very muted So I don't think it is actually doing HDR with this setup.

So its looking like most of my issues have been related to HDR.

looking like more HDR related issues then...

That setting was supposed to be flipped to on


I tried forced V-Sync with HDR content with HDR enabled at the OS level and still stuttered. I forced Vsync to On for MPC-HC as well as my madVR folder.

With these forced on and OS HDR disabled the playback is much less stutters but it is still stuttery and the colors are all muted so The display either sint getting HDR or doesn't know it is.

This testing was done playing back 4K HDR BD Content




Thanks to the below chart I no longer have stutter on my HTPC playing back even 4K HDR BD content. 418.91 did indeed fix my issues and large pans in GITS live action and Bladerunner 2049 are not buttery smooth. No random hiccups from 1080p playback on my 4K screen either so Ill now be able to start tweaking my actual settings which I thought were the issue all along. Thanks to the community for the help as always. Suck when I try to chill after work just to have the thing that's supposed to provide relation pissing me off.

Last thing to note is that with Windows 10 OS HDR enabled I still cant go fullscreen exclusive.



I just updated that info here:
https://forum.doom9.org/showthread.php?t=176013

419.67 GRD 2019-03-25 stuttering issues
419.67 CRD 2019-03-20 stuttering issues
419.35 GRD 2019-03-05 stuttering issues
419.17 GRD 2019-02-22
418.91 GRD 2019-02-14 NO stuttering issues

Did anyone test 419.17 about the stutter issues?

[katodevin]

Thanks to the below chart I no longer have stutter on my HTPC playing back even 4K HDR BD content. 418.91 did indeed fix my issues and large pans in GITS live action and Bladerunner 2049 are not buttery smooth. No random hiccups from 1080p playback on my 4K screen either so Ill now be able to start tweaking my actual settings which I thought were the issue all along. Thanks to the community for the help as always. Suck when I try to chill after work just to have the thing that's supposed to provide relation pissing me off.

Glad to hear going back to 418.91 fixes it. I can totally relate. I'm stuck with a 1660gtx that stutters no matter what. Much less with vsync on (every 2-3 min now), but unfortunately I can't go back to 418.x since they don't support the 1660 :(. I'm really hoping Nvidia figures out what the issue is, but I'm afraid I may have to dump my 1660 if it doesn't get resolved soon.

[stax76]

I have a problem which is likely a driver or OS problem, I just want to ask if it's known here and where I should report it, NVIDIA has a support forum, right? I reported it first to mpv, and they told me to test madVR. After I told them it's not working in madVR too they said it's a driver or OS problem. It happens when I do the following:

using Windows 10
using NVIDIA GT 1030 card
dual monitor with duplicate mode
use d3d11 which mpv and madVR use by default
use fullscreen windowed mode

The second screen is broken then, horizontally stretched showing only the left side of the image and everything is green.

[huhn]

working flawless here.

cloning two 1080p screens
windows 17134
1060 419.67
d3d11 windowed and FSE which isn't the default madVR option.

[stax76]

Thanks for testing. I've forgotten to mention that it happens only in full screen mode. I'm using the latest Win 10 and a driver installed about 3 weeks ago, screens are both UHD.

[huhn]

i tested FSE and WFS.

anything else that comes to mind?
screen scaling?

[stax76]

Maybe it happens only with UHD but it could be anything, much likely it relates to d3d11, when I use gpu-context=angle in mpv then it's fine. When I extend the screens instead of duplicating it then it's fine as long as I start the player directly on the TV, yesterday I started the player first on the desktop (because the TV wasn't on yet) and moved it to the TV screen afterwards which caused the problem to appear.

[tp4tissue]

Is there a way to change zoom percentage ? for when I want to squish or expand images on CRT ?

[Asmodian]

That is the player's responsibility, madVR will render to whatever size the player asks for.

Zoom Player is very good at that kind of thing. :)

[SirMaster]

So I can set a lens memory on my JVC when a video starts to play.

But how can I set a lens memory when a video stops playing?

I want to revert back to my main default lens memory when playback stops and only be in my special video lens memory when I’m playing any video in madvr.

[madshi]

Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.

[Ver Greeneyes]

FWIW, I also noticed this line in the information (https://support.microsoft.com/en-us/help/4490481) for the latest cumulative update for Windows 10: "Addresses an issue that prevents users from configuring their screens for high-dynamic-range (HDR) video playback."

What exactly that fixed or if it'll affect madVR in any way I don't know.

[huhn]

should be unrelated because that's about the windows API.

[Manni]

Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.

This is great news! Thanks for taking the time to let us know :)

[SamuriHL]

Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.

Oh thank God! That's fantastic!! Thanks, madshi!!

[sat4all]

Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.

Great news, Thanks madshi!

[j82k]

Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.

I bet it's gonna be fixed for 1 or 2 drivers and then they'll break it again. :rolleyes:

[SamuriHL]

Maybe, but, at least the 20xx guys and gals will have a useful driver they can roll back to. :) And the rest of us will have a later driver we can use.

[TheProfosist]

Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.

Good to hear because at least based on my testing most my issues revolved around 4K HDR content or display output. Whether it be windows or the content.

[ryrynz]

Some calming down on the madshi quoting would be nice, that's five times over six posts. Do you really need him to be notified of your reply? Do we need to a full quote to understand you're replying to madshi?
A simple "thanks madshi" works fine to show you're replying to a post of his.

Honestly, it looks a lot worse on mobile, but can ya make an effort to not spam quote madshi's posts? Especially when he does release posts as it's much much larger, cheers.

[Sunset1982]

I managed to make a video of a direct comparison between the working D3D11 windowed 8 bit mode with my AMD card and the "overblown reds bug " in D3D11 fullscreen windowed 10bit mode. Any suggestion where I should upload the video that you guys can watch it?

[Klaus1189]

Google drive, so the user can download full bitrate file

[Solitaire01]

Hi everyone,

I own an RTX 2070 and as most of you have been suffering with stuttering in HDR at 24 FPS. Ultimately I’ve discovered that turning on windows 10 HDR in advance and letting Madvr run with "OS HDR" clears up the stuttering. Other than having to toggle it manually (especially as it is incompatible with 3D content when left enabled) is there a qualitative downside versus the Nvidia mode?

Cheers!

[Asmodian]

Yes, Windows does its own HDR tone mapping that nothing can control and does not take metadata into account. I am not sure how this interacts with madVR's tone mapping, if you are using madVR to process the HDR.

I use 60 Hz smooth motion instead of stuttering 24 Hz. It really is a good option in my opinion.

[Solitaire01]

Yes, Windows does its own HDR tone mapping that nothing can control and does not take metadata into account.

Thanks - very interesting. Is there a way to empirically test this? If I play an HDR MKV through the Windows Movies and TV app with OS HDR on, through JRiver/MadVR with OS HDR on and metadata pass through enabled, and through JRiver/MadVR with NV HDR and pass through on, the results aren’t distinguishable to me aside from the stuttering.

[madjock]

Well there was a post a little while ago that showed nVidia drivers after 398.11 were also not passing metadata properly.
https://forum.doom9.org/showpost.php?p=1865444&postcount=54686

The thread below is a list of drivers and issues that people have reported.

https://forum.doom9.org/showthread.php?t=176013

So it may be a case of if you are using a later nVidia driver that may be the case and both Windows and nVidia are doing the same thing.

I use 385.28 as it seems to have the best feedback for most things working, but I also never knew the difference between working metadata or not, I only found this out due to this thread.

[iSeries]

I use 60 Hz smooth motion instead of stuttering 24 Hz. It really is a good option in my opinion.

Hey, on your oled, how do you find Smooth Motion vs 23p with Real Cinema?

[brazen1]

In my case, when matching refresh rate 23.976 (99% of all titles) 24Hz doesn't stutter at all. It's matched. It's smooth as butter unlike 60Hz (which is not a multiple of 24) using SM - A band-aid to (help)mend 3:2 pulldown but is still noticeable to the eye. Imo, a blanket statement "I use 60 Hz smooth motion instead of stuttering 24 Hz. It really is a good option in my opinion" is only relevant if (A) your display is only native 60Hz capable and not at least 120Hz or (B) your display has poor motion handling such as OLED's commonly reported by users.

[chros]

Hey, on your oled, how do you find Smooth Motion vs 23p with Real Cinema?

:) I just added a comment in this thread (https://forum.doom9.org/showthread.php?p=1871312#post1871312).

[Asmodian]

Hey, on your oled, how do you find Smooth Motion vs 23p with Real Cinema?

I require 4:4:4 so no Real Cinema for me. :mad:

I really do like and use smooth motion a lot though, it is much better than dropping to 4:2:2 chroma.

[madjock]

FWIW, I also noticed this line in the information (https://support.microsoft.com/en-us/help/4490481) for the latest cumulative update for Windows 10: "Addresses an issue that prevents users from configuring their screens for high-dynamic-range (HDR) video playback."

What exactly that fixed or if it'll affect madVR in any way I don't know.

Well think I have just found out what this does. I stopped using 12bit but thought I would try again.

Now when I manually changed the refresh rate to 23.976 12bit it enabled OS HDR, they also seemed to have sorted the messed up washed out desktop as well.

I switched OS HDR to off in settings, so now when it goes to 23.976 12bit it uses the nVidia HDR as normal.

[tony359]

The second screen is broken then, horizontally stretched showing only the left side of the image and everything is green.

I have just updated to windows 10 1809 and as usual I am fixing all the things that Microsoft resets at every update.

However I am also experiencing what Stax76 reports.

I am using a "dual monitor" setup only because my ONKYO does not see 4K output so I am extending my main monitor to it in 1080p to have sound.

As it stands, whenever MadVR goes full screen (not FSE) and the cursor disappears, the whole screen turns greenish, only the left part of the picture is displayed and it's stretched. If I move the cursor again, the screen is back to normal for a few seconds.

It only seems to happen when MadVR is being used. I've moved from D3D11 to Cuvid, disabled game mode as found on some forums but nothing.

I am using a 1050Ti and driver 416.94. Everything was working fine before updating the OS.

Please see a video here - it's a paused playback, it does not need to be playing for that to happen!

https://share.icloud.com/photos/0spoWocPHtBbScsVO_QtAVtcA

Any help?

Update: found the solution. I updated the nvidia drivers to 419.67. The installer reported that "none" driver was installed. After installing an rebooting, all works as expected. In fact, I found a change in the behaviour: where previously the nvidia control panel would report 16-235 levels but my projector would clearly see 0-255 input, now things match up. So OS reports limited 16-235 and projector senses 16-235.

[Sunset1982]

Here is a Link to the strange overblown red bug with amd cards and fullscreen windowed 10 bit mode...

https://drive.google.com/file/d/1WA_8hqBUNmsASYIhjl_DCF-lGPFUOv0b/view?usp=sharing

[Warner306]

Is your issue triggered similar to this post:

https://forum.kodi.tv/showthread.php?tid=223175&pid=2788748#pid2788748

[Sunset1982]

Is your issue triggered similar to this post:

yes, exactly the same

[mclingo]

i got nowhere with amd and this, and MADSHI doesnt have a contact at AMD to deal with issues like he can sometimes with NVIDIA, i just calibrate to BT2020 and it fixes it for me, none of this makes sense, i've discussed this in detail.

Anyway, its not a MADVR issue so we shouldnt discuss it here, go to the general thread.

[Warner306]

yes, exactly the same

Might as well complain again to AMD. You could send that link as a summary. It sounds like it isn't that hard to reproduce. It must not effect all AMD cards.