madVR - high quality video renderer (GPU assisted)

[ashlar42]

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]

the problem with FSE is the black screen

working fine here what player are you using?

[Manni]

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]

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]

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]

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.

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.

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.

the problem with FSE is the black screen

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.

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

10bits works fine in 385.28 here.

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.

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]

working fine here what player are you using?

mpc-be

[stefanelli73]

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

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

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

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]

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]

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]

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]

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?

[Manni]

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?

Because in one case MadvR uses the nVidia API to switch the display to HDR, and in the other it doesn’t, so the video path (and possibly the driver code used) isn’t the same, because in passthrough the driver outputs HDR (with associated metadata) and in pixel shader it outputs SDR, without any metadata. At least that’s my assumption, I’m sure Madshi will correct me if I’m wrong.

[stefanelli73]

However, going to 92.14 at 92.12 the "problem" of the 8bit is no longer in passthrough hdr comes out to 10bit again

[Manni]

However, going to 92.14 at 92.12 the "problem" of the 8bit is no longer in passthrough hdr comes out to 10bit again

Yes, Madshi has only started to force 8bits in passthrough (and in pixel shader possibly due to a bug) in the latest public release. You do get 10bits in previous versions in passthrough (up to and including test build 5), but there is minor banding in passthrough (not in pixel shader), which is why Madshi decided to force 8bits.

If you can use FSE in any version, there is no banding so 10bits should be enabled.

[x7007]

Yes, Madshi has only started to force 8bits in passthrough (and in pixel shader possibly due to a bug) in the latest public release. You do get 10bits in previous versions in passthrough (up to and including test build 5), but there is minor banding in passthrough (not in pixel shader), which is why Madshi decided to force 8bits.

If you can use FSE in any version, there is no banding so 10bits should be enabled.

So is there a difference between FSE 10 bit and Full Windowed mode 10 bit ? or using Windowed mode and not Full Windowed is the issue ? Is it ok to use HDR ( OS MODE ) Full-Windowed mode 10 bit ?

[Manni]

So is there a difference between FSE 10 bit and Full Windowed mode 10 bit ? or using Windowed mode and not Full Windowed is the issue ? Is it ok to use HDR ( OS MODE ) Full-Windowed mode 10 bit ?

Yes there is a difference.

FSE = no banding in 10bits.
Full windowed mode on win 10 with nVidia and passthrough = minor banding in 10bits until 94.12.

In 94.14, all modes are forced to 8bits, except if FSE is used,

Hopefully in the next build, only passthrough will be forced to 8bits, except if FSE is used.

Don’t know about OS HDR mode, I never use it as the nVidia API works great and is much preferable.

Just use whichever mode you normally use and live with 8bits dithering until a fix is available. This doesn’t make much difference visually, as MadVR’s dithering is excellent. This is a very small amout of noise, but hardly perceptible. Or revert to 94.12 if you really want 10bit dithering and can’t use FSE,

[Asmodian]

Because in one case MadvR uses the nVidia API to switch the display to HDR, and in the other it doesn’t, so the video path (and possibly the driver code used) isn’t the same, because in passthrough the driver outputs HDR (with associated metadata) and in pixel shader it outputs SDR, without any metadata. At least that’s my assumption, I’m sure Madshi will correct me if I’m wrong.

You mean pixel shader to SDR? That puts madVR into an SDR mode, I was talking about modes that output HDR. There are more than just passthrough. :devil:

"passthrough HDR content to the display"
"process HDR content by using pixel shader math"
"process HDR content by using an external 3DLUT"

[Manni]

You mean pixel shader to SDR? That puts madVR into an SDR mode, I was talking about modes that output HDR. There are more than just passthrough. :devil:

"passthrough HDR content to the display"
"process HDR content by using pixel shader math"
"process HDR content by using an external 3DLUT"

Process HDR doesn't work on any display I know. It creates metadata that no display can understand and process. Are you using any of these with success? I don't know of anyone who does.

As far as HDR is concerned in MadVR, there is passthrough and pixel shader. Process is a dead end, except maybe process with a 3D LUT.

Still, there is only one pass-through mode.

[nussman]

Come on ... this is way too much off topic here ...

[NoTechi]

Come on ... this is way too much off topic here ...

Sorry. Could you point me to a better place where I should ask? I will delete my post then (if thats possible)

NoTechi

[nussman]

Maybe start your own thread here @doom9 (software players section should be fine). :)

[NoTechi]

Maybe start your own thread here @doom9 (software players section should be fine). :)

Done and posted here as you sugested :)
https://forum.doom9.org/showthread.php?p=1840475#post1840475

Sorry again :)

NoTechi

[brazen1]

#1 Use KODI 17.6 because Alpha v.18 is not even close to usable yet.
#2 Windows HDR and color settings switch is NEVER enabled and will significantly hamper madVR if it is.
#5 Don't covert HDR to SDR unless your display is not HDR compatible. Use passthrough.
#6 Driver v.385.28 is the last driver that half way works. Anything newer presents even more problems.

The guide in my signature will offer more details for your general questions than this specific madVR forum.

[NoTechi]

#1 Use KODI 17.6 because Alpha v.18 is not even close to usable yet.
#2 Windows HDR and color settings switch is NEVER enabled and will significantly hamper madVR if it is.
#5 Don't covert HDR to SDR unless your display is not HDR compatible. Use passthrough.
#6 Driver v.385.28 is the last driver that half way works. Anything newer presents even more problems.

The guide in my signature will offer more details for your general questions than this specific madVR forum.

Thanks Brazen and sorry again for capturing this thread :scared:

[Warner306]

Hi everyone,

hopefully my madvr questions are not too newb for this thread ...

Really looking forward to "play" with madvr and other settings on upcoming months and hope you could let me know your opinion if the software setup I described above sounds like a good way to go and again sorry if it is too newbish :)

NoTechi

1. Kodi DSPlayer is a valid alternative for the next couple of years. I used Jarvis 16.1 for two years and the only thing it lacked was support for three add ons out of the 88 installed on my system. I did miss a couple of those addons, however.

Future releases are in doubt but it can work for a couple of years and updates have always been provided by the original developer in the past despite ceasing active development. The benefit of DSPlayer is that content from video addons can be played through the player, which has madVR support. This includes YouTube, various public broadcasters, online sites, magazines, etc. There are also piracy add ons, if that's your thing. There is even such as thing as madVR-enhanced porn (not that I'm an expert on that subject, but it's out there in large quantities). Be careful when installing any third-party add ons, as this can corrupt your Kodi install with badly-written scripts that constantly run in the background.

Regular Kodi with MPC will offer the best add on support and some of those add ons (but not all) can be played with MPC. This varies based on the type of links in the add on. DSPlayer is more reliable than MPC with video add ons.

I don't know if external players work well for live TV. DSPlayer has native support for some backends, but I don't know if it still works with new versions.

2. There is a Netflix add on in Kodi, but it is limited. Something has been planned for v18, but I don't know how complete it will be. If you use the official Windows Netflix app, you will have to toggle the HDR switch and then turn it off again before using Kodi.

3. Use the official YouTube app in Kodi.

4. I don't think you can play a game in Steam and render it with madVR.

5. For projector owners, HDR -> SDR conversion is the same thing as HDR mode in most respects due to the limited lumens of projectors in all modes. HDR -> SDR conversion still uses PQ gamma and similar tone mapping techniques, so it is no different than your projector's HDR mode, just with different algorithms. It could be better; it could be worse. This technology is still being improved for future releases and hasn't finished the testing stages yet.

6. Driver 385.28 seems to have the least issues of all recent drivers, but newer drivers are working for many users. There are still some quirks and bugs with HTPC use, but there is no need to upgrade the driver as no new features have been added to enhance video playback. All features in newer drivers deal with video games alone.

[NoTechi]

Many Thanks Warner and others this really helps me to get started!

Please if there is more assistance on my questions please use the other thread I started to not get even more offtopic for this thread ...
https://forum.doom9.org/showthread.php?t=175414

I know those who replied here just have been super fast answering and I would like to thank for that :)

NoTechi

[Darkmatterx76]

Hi, starting last night I started hearing a quiet chirping sound that sounds not unlike a cricket. I've tracked the problem back to MadVR by uninstalling everything installed for playing videos, MPC-HC, MadVR, Re-Clock, and SVP 4 Pro.

I reinstalled everything 1 at a time and tested a video that starts out quiet so it is easier to hear it. It came back near the end of my trial after installing MadVR. I tried resetting MPC-HC and played the video. No chirp. I set MadVR as the preferred rederer and the chirp comes back. It does this in MPC-HC and BE, but not VLC which doesn't have MadVR. I tried applying each component 1 by 1 and still only got the problem once MadVR was activated as a preferred external filter.

Here is a link to an MP3 I recorded of the sound. The sound seems to be constant but is often drowned out by louder sounds. I'm sure it still has an effect on quality though.

http://s000.tinyupload.com/index.php?file_id=98334376119381288677

I'm using the latest ver of all software and have updated my audio and video drivers.

My system is Windows 10 Pro 64
MB: Asus Z97M-Plus (Latest Firmware)
CPU: i5 4690K
Video Card: Asus ROG GTX 1070
Audio Card: Asus Strix SOAR
Audio Listening Hardware Used: Sennheiser HD558 Open Back Headphones
Memory: DDR3 Corsair PC3-10700 (XMP-1600) 800MHz (Dual) 9.0, 9, 9, 24, 41, 2T, 1.5V


Thanks.

DM

[lvqcl]

Sounds a bit like www.youtube.com/watch?v=HP73edpQwgc

[Asmodian]

I am almost positive that is coil whine, a manufacturing defect that specific loads can cause to manafest. Try different madVR settings, more or less load can change or eliminate the sound. :p

[Darkmatterx76]

I only JUST bought this Asus SOAR a couple weeks ago. If this is in fact a defect I should be returning it. It has a shield over it to prevent this sort of thing. (I thought)

Will Asus see this as a defect, or a "feature?"

Thanks.

[el Filou]

The problem with Kodi has to do, unfortunately, with too few Windows developers on board. Being open source, I hoped for quite a long while that somebody would fork it to something Windows only and be done with it.That already happened 14 years ago when Kodi was called XBMC, and the result was MediaPortal 1. It supports madVR too, by the way.

[Asmodian]

I only JUST bought this Asus SOAR a couple weeks ago. If this is in fact a defect I should be returning it. It has a shield over it to prevent this sort of thing. (I thought)

I would not assume it is being caused by the sound card, I actually suspect the video card. Coil whine is usually the video card or motherboard but given that it happens when using madVR I suspect the video card. Does it go away if you switch to motherboard audio or swap the video card (if possible)? It can also show up and disappear on its own. I have had both a monitor and video card that eventually stopped whining, but the monitor took months, and it often doesn't ever go away.

Coil whine is very frustrating because it usually only shows up with very specific loads. I have even seen (heard) power supply based coil whine that changed pitch when scrolling the mouse wheel. :confused:

People sometimes get some 2-ton epoxy or similar and try to lock down/dampen the chokes enough that they stop whining... with mixed results.

Manufactures rarely accept coil whine as a reason to RMA unless it is really bad, and even then they are sometimes difficult. :(

[Darkmatterx76]

OK I tracked it down to the option to reduce compression artifacts. I can change anything else, turn stuff on, but once that 1 setting is off, the noise stops. So is this a real defect in my sound card or just that this 1 option pushes the card past its intended limits?

Also, I might as well ask. I've been using JINC with reduced ringing artifacts. There's other options like the multiple NGU options, DXVA2, Super-xbr, and I believe in the player I can pick CUDA since I have a GTX 1070.

Which options should I use, and if I should use one that has other options like doubling, quadrupling, etc, what settings would be best for my system?

Thanks

[Darkmatterx76]

Well when I changed the "reduce compression artifacts" from High to Medium the pitch of the whine changed.



I would not assume it is being caused by the sound card, I actually suspect the video card. Coil whine is usually the video card or motherboard but given that it happens when using madVR I suspect the video card. Does it go away if you switch to motherboard audio or swap the video card (if possible)? It can also show up and disappear on its own. I have had both a monitor and video card that eventually stopped whining, but the monitor took months, and it often doesn't ever go away.

Coil whine is very frustrating because it usually only shows up with very specific loads. I have even seen (heard) power supply based coil whine that changed pitch when scrolling the mouse wheel. :confused:

People sometimes get some 2-ton epoxy or similar and try to lock down/dampen the chokes enough that they stop whining... with mixed results.

Manufactures rarely accept coil whine as a reason to RMA unless it is really bad, and even then they are sometimes difficult. :(

[YxP]

I only JUST bought this Asus SOAR a couple weeks ago. If this is in fact a defect I should be returning it. It has a shield over it to prevent this sort of thing. (I thought)

Will Asus see this as a defect, or a "feature?"

Thanks.

It's annoying and I have it too with my 1060. Try using DX11 decoder in lavfilters and dropping NGU quality to high. Should make a big difference. I also stopped using RCA since it helps a bit. I very much doubt you can return the card, but you're welcome to try.

[YxP]

I did try to troubleshoot the problem further at one point and I'm pretty sure it has something to do with Vrel limit, but I kinda gave up at that point and admitted my loss. I wonder if undervolting would help...

[Clown shoes]

Hey all, I'm having a torrid time trying to get custom resolutions working on my system :(

I feel like I've tried everything but I always seem to get a frame drop every 4 and a bit minutes.

Is this currently just not possible with the latest Nvidia drivers?

I'm almost ready to give up getting this to work as it's becoming so frustrating

[Asmodian]

It isn't quite not possible, at least for one refresh rate, but it is not easy. :(

I have had a lot of trouble getting Nvidia to actually USE the custom refresh rate with the new drivers... I found that deleting everything out of Nvidia's custom resolutions, effectively disabling that feature in the drivers, and then letting madVR do everything including adding and changing to the custom resolution worked better for me.

Giving up and using smooth motion... is not totally crazy. ;)

[leeperry]

Coil whine usually occurs with a specific combination of graphic card & PSU as in another PSU might not trigger the whine at all FWIR.

The funny thing with mVR is that upscales made by HDTV channels look totally facepalmic in comparison but then again I know a guy who does encodes for netflix and he's using the same crappy profile for everything in single pass so I guess HDTV technicians don't care any more than he does.

[YxP]

So you are saying you prefer mVR? That's very surprising coming from you! x)

[ryrynz]

Oh yeah, he loves madVR, always has. What's not to like?