madVR - high quality video renderer (GPU assisted)

[sauma144]

MadVR should be installed in %appdata%.

[jkauff]

I have an EDID editing utility that reads the EDID values from the registry for my displays. The data in the utility does not always match the EDID data madVR displays. For example, I have a monitor that supports 10-bit color, but according to madVR it only supports 8-bit color.

I assume madVR is reading the registry values, too, so why don't they match?

[FDisk80]

After latest windows 10 update yesterday (1803)
With 397.31 driver 10-bit output doesn't work even with FSE mode anymore. It doesn't even let you run FSE Mode.
With 397.40 driver 10-bit output freezes when in FSE mode.

Going back to madVR v0.92.12 with 397.40 driver 10-bit works fine in D3D11 Fullscreen windowed mode.

[mclingo]

Yes, but I think you misunderstood me ... you wrote there : madVR's settings can be backed up or shared via a settings.bin file.

But I would like to know how to do that. Backup my own settings

TIA, Sven

Windows 10 doesn't automatically give full write access to MADVR folder, you need to add it in security or place it outside of Program files as Warner advises. it doesnt matter where you put it though as long as it has full R/W access.

My preference is to just give myself write access to program files as I prefer all my progs in one area.

However, this periodically gets removed by windows updates i've found, it happened with creators update.

[stefanelli73]

So let me understand well for those like me who use the HDR passthrough is better to exit in fse 10bit or windowed mode to 8bit as in the current version of madvr the 92.14? .... I have the impression that in windowed mode 8bit the image is better ..... for the HDR is it better to stay with the NVIDIA 385.28 drivers or switch to the last one 397.40?

[Betroz]

After the 1803 update to Win10 I'm dropping frames like mad here. Render & present queues are going way down. I'm using the same settings as before. I have tried 3 different nVidia drivers too, but same thing. So is there a problem with MadVr in Win10 build 1803?

Edit : I lowered the settings down to NGU High and it's not dropping frames now, but look at the render & present queues. Well under 10ms stats.

Edit 2 : Removed an image that takes for ever to get approved. Will make a new post.

[nussman]

Windows 10 doesn't automatically give full write access to MADVR folder, you need to add it in security or place it outside of Program files as Warner advises. it doesnt matter where you put it though as long as it has full R/W access.

My preference is to just give myself write access to program files as I prefer all my progs in one area.

However, this periodically gets removed by windows updates i've found, it happened with creators update.
Software for windows should not need write access anyway for the program files folder.
If madVR need this for a feature imho this should be changed by madshi.

[nevcairiel]

madVR doesn't even come with an installer, if you place it in Program Files, thats your own fault. :) Also, it stores its settings in the registry as well, so its never "required" to have that write access. The file is just a secondary settings storage, its not mandatory to retain the configuration.

[nussman]

I disagree here.
Program files folder is for Applications and windows offers special folders where settings can be saved. ;)

[nevcairiel]

Windows also has the registry, where madVR stores its settings. So what exactly is the problem now? =p
I like that it stores the settings in its own directory, that lets you more easily ship pre-configured settings or have madVR be more self-contained if you try to handle it "portable" without installing it in the system (if the player supports that).

[nussman]

But you can see what other users (i.e. mclingo) are doing to get this settings.bin?
Imho this should not be encouraged. ;)

[wolfman2791]

Guys... I have a problem. Ever since I upgraded to the last version, I get this strange sound from my R9 390. I know it's from madvr because it goes away as soon as I turn it off. Anyone else have this problem?
Help lol.

Ran Unigine to see if my GPU was the problem... not a sound at all at max capacity. So it has to be madvr. Has there been issue with compatibility with the R9 390?

[mclingo]

its a personal choice, i could have it anywhere on my 12 hard drives if I so chose, i've had it elsewhere in the past but I prefer it where it is now, nobody should be trying to discourage anyones personal preference as it make sod all difference where it is as long as you have R/W access.


NEV, are you suggesting settings.bin is not required?, how else would you restore settings after a wipe/reinstall/rebuild?

[nevcairiel]

You could just export the registry key if you want to backup settings. Same settings, just slightly different procedure. Most Windows things store settings in the registry.

[mclingo]

Help lol.

Ran Unigine to see if my GPU was the problem... not a sound at all at max capacity. So it has to be madvr. Has there been issue with compatibility with the R9 390?

where is the sound actually coming from, is it coming out of your speakers?, does it stop if you disable/enable bitstream?

[mclingo]

You could just export the registry key if you want to backup settings. Same settings, just slightly different procedure. Most Windows things store settings in the registry.

i'd actually prefer that, whats the location of the reg entries, I could find them but if you have them to hand that would be useful.

[cyberscott]

After the 1803 update to Win10 I'm dropping frames like mad here. Render & present queues are going way down. I'm using the same settings as before. I have tried 3 different nVidia drivers too, but same thing. So is there a problem with MadVr in Win10 build 1803?

Edit : I lowered the settings down to NGU High and it's not dropping frames now, but look at the render & present queues. Well under 10ms stats.

I have the same issue. Happened right after installing Win10 build 1803. Reinstalled Nvidia drivers, madVR, MPC-BE/CE, no change, Definite issue caused by the new Win10 build 1803.

[nevcairiel]

i'd actually prefer that, whats the location of the reg entries, I could find them but if you have them to hand that would be useful.

The obvious place:
HKEY_CURRENT_USER\Software\madshi\madVR

[mclingo]

I have the same issue. Happened right after installing Win10 build 1803. Reinstalled Nvidia drivers, madVR, MPC-BE/CE, no change, Definite issue caused by the new Win10 build 1803.

When you say you are dropping frames, what does you CONTROL-J screen look like?, are you using refresh rate switching and playing movies at 23,976, how close are to this now, are your CRU's working? Have you reinstalled MADVR and LAV filters from scratch, I had to do that after creators update, i'm using an AMD RX card though.

[mclingo]

The obvious place:
HKEY_CURRENT_USER\Software\madshi\madVR

Thanks.

[Betroz]

I have the same issue. Happened right after installing Win10 build 1803. Reinstalled Nvidia drivers, madVR, MPC-BE/CE, no change, Definite issue caused by the new Win10 build 1803.

Good to know I'm not the only one who has this problem. I wonder if Madshi must change MadVr in some way, or if it is a Win10 1803 bug.

[Betroz]

When you say you are dropping frames, what does you CONTROL-J screen look like?, are you using refresh rate switching and playing movies at 23,976, how close are to this now, are your CRU's working? Have you reinstalled MADVR and LAV filters from scratch, I had to do that after creators update, i'm using an AMD RX card though.

I added a screenshot to my original post, pending approval. I formatted my SSD and installed Windows, MadVR and everything from scratch.

CRU's ?

[mclingo]

I added a screenshot to my original post, pending approval. I formatted my SSD and installed Windows, MadVR and everything from scratch.

CRU's ?

you need to add custom resolutions to madvr for nvidia cards if you want to get close to 23,976 smooth playback, that probably isnt the issue but you'll get dropped frames.

post your sceen again using a web link like drop box, they take ages to get approved on here.

[ryrynz]

I have the same issue. Happened right after installing Win10 build 1803. Reinstalled Nvidia drivers, madVR, MPC-BE/CE, no change, Definite issue caused by the new Win10 build 1803.

But did you change the power management mode back to Adaptive? I kinda doubt this is "definite Windows issue"

[zaemon]

I switched to Win 10 from Win 8 and did a clean install. Now native D3D11 works as expected. The only « problem » being that zoom control doesn’t seem to work. So I’m back to copy-back and I’m fine with that.

[cyberscott]

But did you change the power management mode back to Adaptive? I kinda doubt this is "definite Windows issue"
Yep, even set it to Maximum Performance. No change.

For fun, I tried a few things.

I installled the Windows 10 1803 Spring Update on another older computer, different processor brand (Intel) and different Nvidia card and the same issue with the madVR happened on that system.

For more fun, I rolled back my main rig to the previous Windows 10 build and MadVR worked as it did before the update.

So, for me and my system, Windows 10 1803 is the culprit.

I have reinstalled Windows 10 1803 on my main rig again, and the problem came back. I'm sticking with it for now as I've seen performance increases with games and I want to mess around a bit with the new features.
**

More info I can provide, after further testing is that standard definition upscaling to 4K is more affected. I've had to lower NGU settings down from Very High to High (luma) and drop "reduce compression artifacts quality from "very high" to "high" to make things playable. Render and Present queues will go no higher than 6, even if set higher.

Upscaling 720 or 1080p material to 4k, the GPU queue will not fill above 16 now but I could max it to 24 prior to the Windows update. 720 or 1080p material at 4K still work at my old settings and render times are nearly 5 miliseconds *less* than before the Windows 10 update. Not sure if that is real or not but I'll take it. :p

A side note, I even removed all over clocking to my rig with no change.

For full clarification, I have a Ryzen 1800x @ 4.25, GTX 1080 Ti, madVR 92.14, LAV 0.71.0.16, and use the latest versions of MPC-BE and MPC-CE. I upscale everything to 4k (using profiles for different resolutions) with frame rate switching, on a LG 4k OLED TV.

[ryrynz]

Updated to 1803, I have no problems with madVR on my 1060.

[ryrynz]

Windows 10 doesn't automatically give full write access to MADVR folder

Might be an idea at least until a proper installer is added to madVr that the batch file is improved to provide RW access to the installed folder.

[rahzel]

Can someone help me narrow down my issue?

I don't use my HTPC a whole lot, the last time I watched a video on it was probably a little over a month ago and I didn't have any issues.

I recently updated my HTPC (Win10) to the new April 1803 build and now when I put my videos in full screen exclusive mode, I get around 4 seconds of black screen, then when the video appears there are a few hundred dropped frames within a few seconds, and then the video finally plays smooth as normal. While this is all happening, the audio is still playing back at normal speed without interruption. So basically when I enter FSE, it takes like ~8 seconds to finally start playing back normal with zero dropped frames.

I'm using the same settings as before, so I'm confused as to why I'm suddenly having this issue. Maybe Win10 updated the video driver?

Anyway, my specs are:
Intel Celeron G1820
Radeon 7750
4GB RAM
Win 10 64-bit 1803 build

Latest MPC HC 64-bit and latest Madvr. I was actually using a slightly older MPC/MadVR when I first noticed the problem, then I updated them both to the latest.

edit: Apparently it's Win10's new 'focus assist' feature which mutes notifications when doing select activities. When I enter FSE it thinks I'm playing a game and turns focus assist on. I turned focus assist off when playing games and it's fine now.

I'll leave this post up in case someone else has this issue.

[ntropy]

I suggest 8bit and “this display is already calibrated” to DCI-P3.


Thanks. What about hdr settings?

[Asmodian]

Passthrough is what I use now.

[tzr916]

Updated to 1803, I have no problems with madVR on my 1060.


Same here. GTX1060, no issues after Win10 v1803.
Before the update, I was running nvidia v388.59.
After the update windows installed v391.35.
Upscale to 4k (No HDR, No FSE mode).

[cyberscott]

Yep, even set it to Maximum Performance. No change.

For fun, I tried a few things.

I installled the Windows 10 1803 Spring Update on another older computer, different processor brand (Intel) and different Nvidia card and the same issue with the madVR happened on that system.

For more fun, I rolled back my main rig to the previous Windows 10 build and MadVR worked as it did before the update.

So, for me and my system, Windows 10 1803 is the culprit.

I have reinstalled Windows 10 1803 on my main rig again, and the problem came back. I'm sticking with it for now as I've seen performance increases with games and I want to mess around a bit with the new features.
**

More info I can provide, after further testing is that standard definition upscaling to 4K is more affected. I've had to lower NGU settings down from Very High to High (luma) and drop "reduce compression artifacts quality from "very high" to "high" to make things playable. Render and Present queues will go no higher than 6, even if set higher.

Upscaling 720 or 1080p material to 4k, the GPU queue will not fill above 16 now but I could max it to 24 prior to the Windows update. 720 or 1080p material at 4K still work at my old settings and render times are nearly 5 miliseconds *less* than before the Windows 10 update. Not sure if that is real or not but I'll take it. :p

A side note, I even removed all over clocking to my rig with no change.

For full clarification, I have a Ryzen 1800x @ 4.25, GTX 1080 Ti, madVR 92.14, LAV 0.71.0.16, and use the latest versions of MPC-BE and MPC-CE. I upscale everything to 4k (using profiles for different resolutions) with frame rate switching, on a LG 4k OLED TV.

One more thing to add before I head off to bed.
If I activate full screen exclusive mode, the queues fill up properly and the display rate changes correctly but the composition rate is stuck at 60Hz. This causes incrementing presentation glitches. If I go windowed, the composition rate goes back to mirroring the display rate.
Done troubleshooting shooting for tonight. Everyone have a good day/evening!

[ntropy]

Passthrough is what I use now.

That looks washed out on the iMac.

[Asmodian]

Oh right, sorry. You don't have an HDR display. Do you have the brightness all the way up? I would not like to use a display at 500 nits for SDR content.

On that display you would definitely convert to SDR, probably "process HDR content by using pixel shader math" on default settings but with peak nits somewhere between 400 and 1000 (or lower, where you like it).

[ntropy]

Oh right, sorry. You don't have an HDR display. Do you have the brightness all the way up? I would not like to use a display at 500 nits for SDR content.

On that display you would definitely convert to SDR, probably "process HDR content by using pixel shader math" on default settings but with peak nits somewhere between 400 and 1000 (or lower, where you like it).

Brightness is at about 30%. At first I tried "convert HDR content to SDR by using pixel shader math" with "target peak nits" at 500 which worked for most content but not all and then I selected "let madVR decide" which seems to work for all content.

[Asmodian]

If your brightness is at 30% then don't using the "500 nits" marketing as a data point, it is probably closer to 120-180 nits. It is 500 nits at 100% brightness (and nits is not linear with brightness).

I thought that "let madVR decide" would be the same as converting to SDR with your display, it converts to SDR with pixel shader math on SDR displays and does passthrough on HDR displays. That said maybe it does do something different, ignoring or overwriting bad metadata comes to mind from past discussion. We do know the paths are different, based on a recent bug that had an effect when set to convert to SDR with pixel shaders but not when using let madVR decide.

[Betroz]

Sorry for the bad image quality, but I used my phone to take a screenshot of a episode av SG-1 to show my performance problem with MadVR in the new 1803 build of Windows 10.

The MadVr settings i use here worked perfectly before the Windows update, with no dropped frames. As you can see from the screenshot, is that after only a minute or so, there is a lot of dropped frames. Again, I have also tried 3 different nVidia drivers with no change. 388.13, 391.35 and the newest 397.31 drivers. So there seems to be a problem with the 1803 update to Win10.

http://bildeopplaster.no/BoU

Edit : Uploaded a smaller image.

[huhn]

can you try normal queue sizes?

[Betroz]

can you try normal queue sizes?

I could try, but again these are the same settings in MadVr I used before the update to Win10, and I got no dropped frames back then. So why change to normal queue sizes?

[oldpainlesskodi]

In the latest Win10 there is a new power plan in Windows Power Settings called "Bitsum Highest performance" - might be worth checking our for those with issues using MadVr after upgrading.

[Betroz]

In the latest Win10 there is a new power plan in Windows Power Settings called "Bitsum Highest performance" - might be worth checking our for those with issues using MadVr after upgrading.

I have mine at High Performance. I can't see what you are talking about on my system.

[oldpainlesskodi]

I have mine at High Performance. I can't see what you are talking about on my system.

Under Control Panel\Hardware and Sound\Power Options there is a new power setting, as I mentioned above, and it may or may not help.

[svengun]

If you install madVR in a folder with write access--for example, "c:\madvr"--the program itself will create/update the settings.bin file in that folder whenever you make a change to the settings. Otherwise, the settings are stored in the registry.

To make a backup, change any setting and save it. Then change it back again and save it. Now you'll have your backup. You can copy the settings.bin file somewhere else if you want.

Thanks , works like a charm !

[Betroz]

Under Control Panel\Hardware and Sound\Power Options there is a new power setting, as I mentioned above, and it may or may not help.

Maybe it is only for laptops. That power plan is NOT available on my desktops systems.

[oldpainlesskodi]

Maybe it is only for laptops. That power plan is NOT available on my desktops systems.

If you read my signature, do you see a laptop? :)

[khanmein]

@Betroz Disable FSE mode. The dropped frames caused by the freeze when you are entering full screen mode.

[Betroz]

can you try normal queue sizes?

Ok I lowered the queue sizes down to 8, and yes that helped. I only dropped 3 frames when I opened the file now. But as you see in this image, the render queue and present queue is still very low. Something is wrong or has changed.

http://bildeopplaster.no/BoW

[Betroz]

@Betroz Disable FSE mode. The dropped frames caused by the freeze when you are entering full screen mode.

No it is not that. As I said, same settings as before 1803 update...

Edit : The frames are not only dropping in the beginning, they are dropping during the entire episode.

[jkauff]

Updated to 1803, I have no problems with madVR on my 1060.
Same here with my 1080 and latest drivers. 1803 did hose my custom refresh rates, but I expected that since it also happens whenever I update the Nvidia drivers.