madVR - high quality video renderer (GPU assisted)

[ryrynz]

First off determine whether madVR is even related to what you see by changing the renderer.

[Manni]

Originally Posted by ryrynz

I only have one custom mode in the Nvidia Control panel set for 23Hz and I tried this driver hoping that I may not even need to set that..
I get a frame repeat every twelve minutes as opposed to a frame drop every three minutes with 385.28 when not using the custom mode.
However, once again like every other driver after this it won't add the custom mode if I change the drop down box to select manual timings, so back to 385.28 I go. Pathetic.

Ayy, I got it to stick by modifying 24Hz instead and added that to the list of resolutions madVR can switch to. Hurrah, now no frame drops/repeats with 398.11.

Are you using HDMI or DP? I thought the new f/w only improved DP, which I don't care about.

Also please could you detail what you are doing so that 24p applies to 23p?

When editing 23p with MadVR custom res, it creates a 24p custom mode in the nVidia CP that is applied with 23p content. That's the way it works here, with all drivers (at least with 4K23, but I think you're using 1080p).

I don't understand what you are doing/modifying, so please could you detail step by step?

Thanks!

[ryrynz]

I'm using HDMI. This is just the results of driver update not the DP firmware, I haven't applied that update.
What I did was via the Nvidia control panel, I haven't saved any custom modes with madVR because Nvidia's custom mode works so well.. when Nvidia's drivers save the config that is.

[nevcairiel]

Not all cards even require the fw update, my 1080Ti didn't, and to be clear, it only updates the UEFI part of the firmware, not the whole thing.

[Manni]

Originally Posted by ryrynz

I'm using HDMI. This is just the results of driver update not the DP firmware, I haven't applied that update.
What I did was via the Nvidia control panel, I haven't saved any custom modes with madVR because Nvidia's custom mode works so well.. when Nvidia's drivers save the config that is.

OK thanks.

Originally Posted by nevcairiel

Not all cards even require the fw update, my 1080Ti didn't, and to be clear, it only updates the UEFI part of the firmware, not the whole thing.

Yes I guess it depends on the brand/model, my 1080Ti (EVGA) did need the fw update. I applied it even though I'm not using DP right now.

I don't think it should make any difference with HDMI, I think the reference to 10bits being handled by the driver is about DP, not HDMI. I haven't tested the 398.11 driver yet though.

I expect the video levels will still be borked, but I'm curious to see if it improves the 3D performance even further than 397.93, and also maybe the 8bits HDR bug will be fixed. These two bugs seem to be JVC only, as few seem to be affected.

[madjock]

No joy from me with latest Drivers 398.11.

Strangely I did a clean install, went in and checked and has been stated it sits at Full as defaults for colour, but I also noticed it had saved my custom 23.976 profile from the previous drivers.

Started a Video and it calmed down to 1 frame drop every 12 Minutes which is no good, but I noticed even though the composition said 23.976, the display was now higher than previous driver at that custom res and was now 23.9767 and hence the quicker frame repeats.

Deleted the custom res, and started the same video agaiin, and yes the composition is sat at 23.976, so I assume this is Nvidias fix and it looks like it ignores custom res well at least for me.

So created a custom res and like some other drivers it would not save either.

Re-Installed 390.77 and set it up as before and back to 1 frame repeat in hours. So no joy for me with them.

[jkauff]

Originally Posted by madjock

No joy from me with latest Drivers 398.11.

This was the first driver install that didn't wipe out my madVR custom resolutions (not a clean install, which probably would have).

I've had the best success creating my custom resolutions in CRU, and then optimizing them in madVR. No "GPU rejected this mode" messages that way.

[Mano]

Originally Posted by ryrynz

First off determine whether madVR is even related to what you see by changing the renderer.

I switched around the directshow setting and

madvr: tearing
Haali video render: tearing
Video mixing render 9 (windowed): tearing

Video mixing render 9 (renderless): no tearing
Enhanced video renderer: no tearing
System default: no tearing

VLC also shows tearing similar to madvr.

So where do you think the problem is?

[huhn]

what system are you using, please make a screen of the OSD and did you changed any settings in your GPU control panel.

my blind guess is an optimus system

[Manni]

Report on 398.11 (see sig for config)

The Good:
- Asio4all compatibility isn't broken anymore, so you can use it with REW etc
- 3D (1080p23FP) timings improved (same as 397.93, around 13-14min for a frame repeat vs every 3min with any of the former drivers)

The Bad:
- They have broken 12bits support entirely in custom res. Even if you create the custom res with say 4K30 12bit selected, the custom res will always be 8bits and won't let you select 12bits (as before). Former drivers didn't let you select 12bits, but the bit depth way greyed out and 12bits was in fact applied. There is no way around that. So not an issue if you want 8bits, but if you want 12bits that's a no go.
- JVC specific: the video levels are still borked, but we're back to 390.65 level, where you can actually get the correct level by setting GPU to Full, MadVR to 0-255 and the JVC to standard. No other combination works, including the correct one which should be to set MadVR to 16-235 for a display set to Standard video levels. I couldn't get good results with Enhanced (0-255) on the JVC either. But at least, you can get the correct levels, unlike 390.x, 391.x and 397.93 which are not usable with the JVCs.

The Ugly:
- JVC Specific: HDR in 8bits is still borked and produces the Magenta bug at all frame rates unless you disable HDR metadata in the HDR tab in MadVR. Pre 391.35 only produce the Magenta bug in HDR at 60fps.

Conclusion:

I didn't test the banding in 10bits in full screen windowed because 10bits is disabled with the current MadVR build.

I tried to create a custom RES using nVidia CP (no back porch accessible, so not good enough) and CRU (wouldn't accept my front porch of 1276). So although 3D is improves, Asio4All incompatibility is fixed, video levels are half borked but usable and the magenta bug is fixable by disabling HDR metadata, the lack of 12bits custom res is a no go. It also looks like the driver doesn't always save the custom modes, or reverts to 60p in the GUI when the actual frame rate is lower.

Big mess of a driver for JVC users, possible a good choice for those who don't need custom res or can get one with CRU.

As for me, back to 385.28, as the only downside there is a frame repeat every 3mn vs 13-14min in 3D...

[x7007]

Originally Posted by Mano

I switched around the directshow setting and

madvr: tearing
Haali video render: tearing
Video mixing render 9 (windowed): tearing

Video mixing render 9 (renderless): no tearing
Enhanced video renderer: no tearing
System default: no tearing

VLC also shows tearing similar to madvr.

So where do you think the problem is?

Do you have Vsync Off in the NVCP ? what GPU do you have ?

[giulianoprs]

Hello everyone, how do you think my OSD? for now only fullHD, when I get the new 4k tv I'll try the HDR .thanks to everyone.

[NoTechi]

Originally Posted by Manni

Report on 398.11 (see sig for config)

- JVC specific: the video levels are still borked, but we're back to 390.65 level, where you can actually get the correct level by setting GPU to Full, MadVR to 0-255 and the JVC to standard. No other combination works, including the correct one which should be to set MadVR to 16-235 for a display set to Standard video levels. I couldn't get good results with Enhanced (0-255) on the JVC either. But at least, you can get the correct levels, unlike 390.x, 391.x and 397.93 which are not usable with the JVCs.

Which chain are you using with 385.28. GPU full, MadVR 0-255 and JVC enhanced?

NoTechi

[Manni]

Originally Posted by NoTechi

Which chain are you using with 385.28. GPU full, MadVR 0-255 and JVC enhanced?

NoTechi

Nope, GPU Full, MadVR 16-235 and JVC Standard.

[NoTechi]

Thx Manni

[Mano]

Originally Posted by x7007

Do you have Vsync Off in the NVCP ? what GPU do you have ?

I am using sapphire R9 290.

Driver version 13.12 without the AMD Control centre.

p/s: also exclusive fullscreen mode seems to get rid of the tearing.

[huhn]

Originally Posted by giulianoprs

Hello everyone, how do you think my OSD? for now only fullHD, when I get the new 4k tv I'll try the HDR .thanks to everyone.

don't attach screen like this it need admin approval first.

@Mano

ok i try one more time what system of windows is used and can you make a screen of the OSD?

[Mano]

Originally Posted by huhn

@Mano

ok i try one more time what system of windows is used and can you make a screen of the OSD?

Windows 7.

By OSD you mean this? https://i.imgur.com/ztaVlC5.png

[ryrynz]

Why is your screen using 1280x720? Any reason for using d3d9 without present several frames in advance?
Tried d3d11? Any apps running that could be possibly interfering with the display? Shut all non essential apps down.

[huhn]

did you disable aero?