madVR - high quality video renderer (GPU assisted)

[j82k]

Originally Posted by 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.

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

[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]

Originally Posted by 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.

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]

Originally Posted by Asmodian

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...ostcount=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]

Originally Posted by Asmodian

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]

Originally Posted by iSeries

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

I just added a comment in this thread.

[Asmodian]

Originally Posted by iSeries

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.

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

[madjock]

Originally Posted by Ver Greeneyes

FWIW, I also noticed this line in the information 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]

Originally Posted by stax76

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/0spo...bScsVO_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_...ew?usp=sharing

[Warner306]

Is your issue triggered similar to this post:

https://forum.kodi.tv/showthread.php...748#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.