madVR - high quality video renderer (GPU assisted)

[ashlar42]

Originally Posted by Warner306

Didn't know that. I think they still rely on the same video player code, but it could be different.

Nope, it switched to DirectX many years ago. For some time OpenGL builds were available, then they stopped.
https://forum.kodi.tv/showthread.php?tid=181352

Sorry for the offtopic, everybody.

[huhn]

Originally Posted by stefanelli73

the problem with FSE is the black screen

working fine here what player are you using?

[Manni]

Originally Posted by huhn

full range is working perfectly here using 397.31.

is your problem related to SDR/HDR/3D all all together?

Yes. Only with 391.xx and on the JVC. Full/Full/Full or any other combination doesn't work, the levels are simply wrong.

390.65 is simply inverted, so I can do Full Full Limited instead of Full Limited Limited.

It might be specific to the JVCs.

385.28 is the last driver that works properly here, regarding this levels issue and many others.

[huhn]

you can try the "adjust desktop colour settings" in the nv control panel and disable auto it may have something todo with it.

[ryrynz]

How is 'perform tone and gamut mapping in less accurate color space' under Trade quality.. changed? It's grayed out for me.

[x7007]

Hey, NV HDR mode doesn't enable 10 bit mode , it stay 8 bit. OS HDR works fine 10 bit . can you fix it ?

[Warner306]

Originally Posted by Manni

Doesn't work here on my JVC RS500.



In this build diffuse white is set to 100nits. I guess you can't set target nits below diffuse white, which makes sense.

I think this is isolated. There are many other Full -> Full -> Full Nvidia users out there.

[Warner306]

Originally Posted by x7007

Hey, NV HDR mode doesn't enable 10 bit mode , it stay 8 bit. OS HDR works fine 10 bit . can you fix it ?

This was done on purpose because of a driver bug which was creating banding in 10-bit windowed mode with HDR playback. This only impacts HDR content. But you'll have to use fullscreen exclusive mode with HDR playback to get 10-bit output on Nvidia.

[Manni]

Originally Posted by huhn

you can try the "adjust desktop colour settings" in the nv control panel and disable auto it may have something todo with it.

Thanks, I'll give it a try but I don't see why it would stop working as it should past 385.28.

Originally Posted by x7007

Hey, NV HDR mode doesn't enable 10 bit mode , it stay 8 bit. OS HDR works fine 10 bit . can you fix it ?

Originally Posted by Warner306

This was done on purpose because of a driver bug which was creating banding in 10-bit windowed mode with HDR playback. This only impacts HDR content. But you'll have to use fullscreen exclusive mode with HDR playback to get 10-bit output on Nvidia.

Originally Posted by huhn

windowed HDR is limited to 8 bit with nvidia because it is buggy with 10 bit.
10 bit FSE should work fine.

No, this is a mistake/bug in the last release. The banding only occured in passtrough, so only passthorugh should have been limited to 8bits, but Madshi has forced 8bits in all HDR modes. This isn't necessary in pixel shader, as 10bits works fine in pixel shaders, so hopefully Madshi will fix this soon.

Originally Posted by stefanelli73

the problem with FSE is the black screen

Originally Posted by huhn

working fine here what player are you using?

It's not player related. The black screen comes from the HDMI resync caused by the use of FSE, not only on the start of playback, but also every time you use the interface, for example to select an audio track or a subtitle. Most monitors do this almost instantly, but some displays take a lot longer. With the JVCs and MPC-BE (it would do the same with any player), the black screen is 10-15 seconds or more, which makes FSE not usable.

Originally Posted by stefanelli73

...IN 385.28, but with the last driver this problem is not there, it reads 10bit regularly.

10bits works fine in 385.28 here.

Originally Posted by stefanelli73

I went from the latest version of the NVIDIA drivers to 385.28, after reading this your post, but as in the previous one I continue to have "1 frame repeated every 5 minutes" and I can not in any way go beyond 5 minutes, even changing the settings in LAV VIDEO or Madvr, any suggestions? I have a GTX1080, first an AMD RX480 and I did not have these problems.

You need to use MadVR's custom refresh rate to address this. See post 1 for details.

Originally Posted by Warner306

I think this is isolated. There are many other Full -> Full -> Full Nvidia users out there.

I never said otherwise. I said it might be limited to the JVCs. In any case, the levels are working as expected in 385,28, so nVidia has clearly changed something for those that used full>limited>limited.

[stefanelli73]

Originally Posted by huhn

working fine here what player are you using?

mpc-be

[stefanelli73]

Originally Posted by Manni

, so only passthorugh should have been limited to 8bits, but Madshi has forced 8bits in all HDR modes. 10bits works fine in 385.28 here.

I in fact use passthrough for which 8bit is normal then?

[stefanelli73]

But I have to say that with the AMD RX480 also with passthroough hdr I get 10bit so it's just a problem of NVIDIA?

[Manni]

Originally Posted by stefanelli73

I in fact use passthrough for which 8bit is normal then?

Yes, normal, to prevent banding until nVidia/OS solves it.

Originally Posted by stefanelli73

But I have to say that with the AMD RX480 also with passthroough hdr I get 10bit so it's just a problem of NVIDIA?

Yes nVidia windows 10 windowed mode only. If you can bear FSE, you can use passthrough in 10bits.

You can also try pixel shader, the HDR to SDR conversion is very good, and you're still watching HDR, it's just that the content is converted to SDR by the source (MaDVR) instead of the display. But it looks like 10bits is also disabled in pixel shader in the current build, so you might want to wait for the next one to try this.

[Charky]

Originally Posted by Q-the-STORM

Just did some more testing with 0.92.6 and tweaked madHcCtrl.exe and it seems to work now, I'm posting my steps that got it working, so people with a nvidia card can easily replicate, though I'm doing this by memory, so I might miss something.
(So you don't have to find my original posts: I'm using gtx 1080 ti, windonw 10 pro x64, MPC-HC x64 and my original problem was since I have standard modes for 23 and 24Hz, I couldn't create a custom mode inside madVR and also couldn't edit the existing modes. With the tweaked madHcCtrl.exe, editing is possible now)


At the end some notes for madshi


- I deleted my custom resolutions, so I'm back to zero.

- Went into nvidia control panel, changed into 2160p30, full RGB and 12bit.

- Opened a 23.976fps video, went into madVRs custom modes tab and clicked on the 2160p resolution with 23Hz (listed as standard mode) and clicked on edit

- increased pixel clock by 0.01 mhz and clicked on test mode and clicked on Yes to save the custom mode.

- the 23hz mode is now listed as "custom timings"

- clicked on reset GPU

- closed MPC-HC, reopened the video.

- opened nvidia control panel and switched to my new custom mode (Note that in nvidia control panel the new custom mode is for 24Hz, not 23Hz for some reason)

- checked custom modes tab in madVR to see that the custom timings 23Hz mode is selected as active, which it is and clicked on optimize

- closed all menus and played the file for over 10min.

- in custom modes tab in madVR, I clicked on "optimize", there I selected "optimized pixel clock #1" (which was the first option that had no frame drops.) and clicked on test mode, then on Yes.

- played the file again and checked stats

- in the first 10 sec "1 frame repeat" climbs to 2 hours, in the next 30 secs it climbs to about 4-6hours and eventually stablizes at about 9.0X hours

This is again only for windowed fullscreen, with FSE I get the same output as standard 23 and 24Hz modes in FSE.

As a new Nvidia card owner, this guide saved my life. I strongly suggest making it more visible to everyone, maybe with a link in the first post of this topic.

My detailed experience:

I recently upgraded my Intel iGPU to a GTX 1060. With my old integrated GPU, I luckily never needed to use either ReClock or madVR custom resolution tool to achieve perfectly smooth playback. With my brand new GTX 1060, I had a dropped frame every 13mn. Yikes.

I spent hours trying to make madVR custom resolution tool work with the latest Nvidia driver (391.35), reading again and again madshi’s own guide, reseting my GPU, trying to understand why a 23,976 Hz custom res was listed by Nvidia driver as a 24 Hz res and not a 23 Hz, rebooting windows, creating, editing and deleting custom res through madVR or the Nvidia control panel, using timings that didn’t even seem to be actually applied by the driver even if madVR said so, playing videos for 10 minutes (I know by heart the first 10 minutes of Star Wars: The Last Jedi by now), and that’s only when I didn’t get the dreaded “GPU driver rejected this mode for unknown reasons” error.

At one point, I even gave up, I installed ReClock and of course everything worked fine, before changing my mind again: I wanted to make this freaking setup work like it was supposed to and didn’t want to lose audio quality and bitstreaming.

Eventually, after hours of using Google and searching this topic, I found the above guide, installed old 385.28 Nvidia drivers (because why not), followed the steps, and everything worked at once.

So, with deserved caps, THANK YOU!

I don’t know if the last driver is bugged, or if I was doing something wrong, or maybe both, but here we are: if, like me, you own a Nvidia graphics card, and struggled to create a custom resolution with madVR and the Nvidia driver, save your time, install old drivers, follow these steps by Q-the-STORM, and you’ll be ready to go.

[FDisk80]

After installing latest 397.31 custom resolution with 1080P HDTV's is still broken. madVR just gives that it is unsupported error as usual.
But now there is another issue. 10bit had stopped working while in D3D11 Fullscreen Windowed mode. Only way to enable 10bit now is to use the D3D11 Exclusive mode.

[Manni]

Originally Posted by FDisk80

After installing latest 397.31 custom resolution with 1080P HDTV's is still broken. madVR just gives that it is unsupported error as usual.
But now there is another issue. 10bit had stopped working while in D3D11 Fullscreen Windowed mode. Only way to enable 10bit now is to use the D3D11 Exclusive mode.

That's a bug in the latest MadVR release unless you are in passthrough on Windows 10, because in that case there is minor banding due to OS/nVidia driver bug. In pixel shader, 10bits should be brought back shortly, as I don't think it was Madshi's intention to force 8bits in that mode as well.

[FDisk80]

Originally Posted by Manni

That's a bug in the latest MadVR release unless you are in passthrough on Windows 10, because in that case there is minor banding due to OS/nVidia driver bug. In pixel shader, 10bits should be brought back shortly, as I don't think it was Madshi's intention to force 8bits in that mode as well.

Ah, thanks. I thought it was driver update that did this.

[Asmodian]

10-bit was broken in all windowed HDR modes, not just passthrough.

[Manni]

Originally Posted by Asmodian

10-bit was broken in all windowed HDR modes, not just passthrough.

Not here, there was no banding in pixel shader in 10bits (nVidia set to 12bits) in test build 5 and before, at least on my JVC. This isn't what Madshi himself said either, both when he announced his intention to force 8bits in passthrough (only) in this thread (look for it), and when I reported to him that 8bits was also forced in pixel shader as well in the latest release a few days ago (in the AVS thread). He did say that it might be a bug and that he would double check:

Me: Possible bugs:
1) It looks like you're forcing 8bits on nVidia 12bits even with pixel shader, not only with passthrough.
Madshi: Hmmmm... I'll double check the 8bit vs 10bit thing, might be a bug.

[Asmodian]

Ah, OK, I probably mis-remembered. That seems really odd though. How does the driver know if madVR processed the HDR video first or not?