madVR - high quality video renderer (GPU assisted)

[LordX2]

No biggie. :cool:
mpv is affected too. I'll try with the new Nvidia driver and then report it to them with some hopefully helpful data.

Yes - I can't believe this wouldn't be a warning when installing the driver - or just an option under 3d settings. Nope - registry tweak..... you can tell they never thought this would happen.

[LordX2]

Now back to technical questions:

I always thought MadVR was isolated to its install folder. However, when I was running some tests on my issue the settings seemed to follow.

I ran the uninstall.bat file on my beta install, and then installed the regular madvr release in a totally separate folder elsewhere on the hard drive. I ran its install.bat, and was surprised to find all my settings from the beta release already loaded into it! (It also UNDID some of my settings for HDR tone mapping since it wasn't a beta).

Where are the settings really stored? Is there an appdata folder somewhere?

[huhn]

registry.

[Ultimathor]

Also, if your display is a native 4k projector, just have it at 2160p23 and eliminate the 1080p23. That way MadVR will do the upscaling of the image to the PJ. You can set the various upscaling options under MadVR options - it does an EXCELLENT job. I am watching a 1080p series right now, and it looks SO sharp and crisp on my PJ it's almost like I am watching a 4k release!

Hi LordX2,

Thanks so much for your reply. We're definitely moving in the right direction :-).

I removed the 1080p 23/24/30/60 entries from the display modes for profile 1080p23 and now the scaling works. That's great.

I have unchecked the "report BT.2020 to display" on 2160p 23/60. However, it seems like the projector understands everything coming from madVR as HDR BT.2020 and shifts into HDR mode with high lamp, BT2020 and enables the JVC Frame Adapt on top of madVR. I'd been hoping for DCI-P3 where I should then select high lamp through User 2 rather than Cinema.

The projector shows HDR BT.2020 for 2160p23 HDR material, 2160p23 SDR-material and 1080p (upscaled to 2160p) material. I've attached screen shots for madVR OSD and the JVC N5 info that shows what the projector receives for a 2160p23 HDR movie (Blade Runner 2049) and a 1080p23 movie (About Endlessness).

I've also attached my updated settings.bin file.

I really appreciate that you take the time to assist with this. I would not have been able to figure it out on my own.

[huhn]

why do you even use profiles in the first place?

the black screen has nothing to do with the source.

[ashlar42]

Now back to technical questions:

I always thought MadVR was isolated to its install folder. However, when I was running some tests on my issue the settings seemed to follow.

I ran the uninstall.bat file on my beta install, and then installed the regular madvr release in a totally separate folder elsewhere on the hard drive. I ran its install.bat, and was surprised to find all my settings from the beta release already loaded into it! (It also UNDID some of my settings for HDR tone mapping since it wasn't a beta).

Where are the settings really stored? Is there an appdata folder somewhere?Read here: https://forum.doom9.org/showpost.php?p=1840877&postcount=50503

Watch your GPU and Present Cue's at the 30 second mark after playing a file. See if they temporarily dip right at that point. (Don't skip to 30 seconds, just play from the beginning).

Also assuming you run in D3D Fullscreen Windowed mode. (see my next post)
Tried what you suggested, queues remain rock solid. I did not install the registry hack. Who knows what makes it act up for some configurations...

[LordX2]

Read here: https://forum.doom9.org/showpost.php?p=1840877&postcount=50503


Tried what you suggested, queues remain rock solid. I did not install the registry hack. Who knows what makes it act up for some configurations...

Yeah, definitely a 'some users' kind of thing. Oddly, I tried it on a brand new windows 11 system that I had for a customer - and it did it too. Who knows - just super happy that Nvidia had enough complaints to do something about it!

I read the post there about the settings - oddly, the folder I have MadVR in does have read/write privileges, and I do notice my settings.bin file 'modify date' update after every setting change - so it IS writing to that file, but must also be doing it in the registry somewhere since it copied OVER the settings on a fresh install.

[brazen1]

Afaik, madVR folder should be in the root of C:.

[LenniePaz]

Afaik, madVR folder should be in the root of C:.I've always had my MadVR folder on my desktop, and never had any issues.

Sent from my SM-N975U using Tapatalk

[SamuriHL]

It doesn't really matter where it is so long as the user has access to the location. I have it on my D drive on my laptop. JRiver MC puts a private copy inside its plugins folder in the appdata folder. It's not really relevant as long as it's local.

[aufkrawall]

Yeah, definitely a 'some users' kind of thing. Oddly, I tried it on a brand new windows 11 system that I had for a customer - and it did it too.
The issue still exists with 496.76/.84 driver. However, enabling the new GPU upscaling resolutions "fixes" it for me. Well, it could of course also just secretly disable MPO as well.

[Siso]

The issue still exists with 496.76/.84 driver. However, enabling the new GPU upscaling resolutions "fixes" it for me. Well, it could of course also just secretly disable MPO as well.

What is the nature of this issue? Something like flicker in full screen?

[huhn]

the GPU usages spikes the sync "resets"/changes and frames are dropped.

could look like flicker.

[Siso]

the GPU usages spikes the sync "resets"/changes and frames are dropped.

could look like flicker.

I had flicker in fullscreen using d3d11 for presentation and 1 frame in advance, changed to d3d9 and it is ok.

[LordX2]

the GPU usages spikes the sync "resets"/changes and frames are dropped.

could look like flicker.

It was definitely more like a glitch/stutter. It was very jarring (especially when my present cue was only at 1).

[Siso]

It was definitely more like a glitch/stutter. It was very jarring (especially when my present cue was only at 1).

Does it happen with d3d9, or only with d3d11?

[LordX2]

Does it happen with d3d9, or only with d3d11?

It seems to differ with individual setups.

If you have no need for the new multi plane overlay - just disable it with the .reg file from nvidia and then never worry about it. I did all the worrying for everyone else on this forum over this issue... :)

https://nvidia.custhelp.com/app/answers/detail/a_id/5157

[ashlar42]

However, enabling the new GPU upscaling resolutions "fixes" it for me.

What's this? "new GPU upscaling resolutions"?

[LordX2]

So, finally sat down just to enjoy a flick after all this last weeks stressing, and had something wackily different happen to me.

After about an hour and 15 minutes of straight watching, I noticed a 'click' in the sound - like a sound glitch. I am bit-streaming through my Denon.

Then, out of the blue, ALL the sound started coming out of just one of my rear speakers. I put the movie back 10 seconds, and bam, all sound normal again.

Could maybe just be the encode I was watching - but does this scream anything else to anyone? Never experienced anything like it before, but haven't really gotten to sit down and watch something more than 20 mins since getting this all straightened out.

[Ultimathor]

Hi LordX2,

Thanks so much for your reply. We're definitely moving in the right direction :-).

I removed the 1080p 23/24/30/60 entries from the display modes for profile 1080p23 and now the scaling works. That's great.

I have unchecked the "report BT.2020 to display" on 2160p 23/60. However, it seems like the projector understands everything coming from madVR as HDR BT.2020 and shifts into HDR mode with high lamp, BT2020 and enables the JVC Frame Adapt on top of madVR. I'd been hoping for DCI-P3 where I should then select high lamp through User 2 rather than Cinema.

The projector shows HDR BT.2020 for 2160p23 HDR material, 2160p23 SDR-material and 1080p (upscaled to 2160p) material. I've attached screen shots for madVR OSD and the JVC N5 info that shows what the projector receives for a 2160p23 HDR movie (Blade Runner 2049) and a 1080p23 movie (About Endlessness).

I've also attached my updated settings.bin file.

I really appreciate that you take the time to assist with this. I would not have been able to figure it out on my own.

I found out part of the problem. It was a setting on the JVC N5 under "Auto Pic. Mode Select" that was set to "Last setting" for SD (2D). So when it had registered BT.2020 and HDR on the last played SDR (2D) movie, it continued to do so. I changed it to "Cinema" and now 1080p movies work great. They are upscaled to 2160p, the gamut is DCI-P3 and the colors are beautiful.

However, there's still a problem with UHD HDR rips. I've set the Primaries/Gamut to DCI-P3 for the 2160p23 and 2160p60 profiles and unticked "Report BT.2020 to dislpay". But the display still interprets the material from madVR as being HDR and then switches to high-lamp and HDR Frame Adapt and BT.2020. In the the madVR OSD it says BT.2020 ->DCI-P3. How come madVR shows one thing and the JVC N5 reports another?

I'm a bit confused as to whether I should use BT.2020 for HDR material
or if I should convert from BT.2020 to DCI-P3 and then just set the lamp to high.

When I play series that are in HDR10+ it works fine. MadVR plays these and the projector recognizes these as DCI-P3.

Any thoughts as to why this is happening?

Thanks for any suggestions.

[LordX2]

I found out part of the problem. It was a setting on the JVC N5 under "Auto Pic. Mode Select" that was set to "Last setting" for SD (2D). So when it had registered BT.2020 and HDR on the last played SDR (2D) movie, it continued to do so. I changed it to "Cinema" and now 1080p movies work great. They are upscaled to 2160p, the gamut is DCI-P3 and the colors are beautiful.

However, there's still a problem with UHD HDR rips. I've set the Primaries/Gamut to DCI-P3 for the 2160p23 and 2160p60 profiles and unticked "Report BT.2020 to dislpay". But the display still interprets the material from madVR as being HDR and then switches to high-lamp and HDR Frame Adapt and BT.2020. In the the madVR OSD it says BT.2020 ->DCI-P3. How come madVR shows one thing and the JVC N5 reports another?

I'm a bit confused as to whether I should use BT.2020 for HDR material
or if I should convert from BT.2020 to DCI-P3 and then just set the lamp to high.

When I play series that are in HDR10+ it works fine. MadVR plays these and the projector recognizes these as DCI-P3.

Any thoughts as to why this is happening?

Thanks for any suggestions.

Under the HDR section of the display in MadVR settings, you can select to use pixel shaders to tone map HDR to SDR. That selection should stop HDR from being sent to your PJ. (IN that selection there may be another box to send hdr that need to be unchecked).

I use the tone mapping, and then I go to calibration and tell MadVR that I am calibrated for BT.2020. I tried the 'report bt.2020 to display' - and on ONE of my projectors, it works, and on my Sony, it doesn't (I have to manually switch the Sony to BT.2020).

With those settings done, you will be outputting SDR BT.2020 (MadVR will still always show BT.2020 -> DCI-P3), and the projector should never switch to HDR.

Alternatively, in your PJ settings, you may be able to just SET the picture mode to SDR (e.g. NOT auto) (or conversely turn HDR off) depending on how your PJ menus work.

[Ultimathor]

why do you even use profiles in the first place?

the black screen has nothing to do with the source.

Not sure if this reply was intended for me?

It is my understanding that I need different profiles but if I don't gain anything from it, I'd be just as happy with just one. I mostly watch movies that are either 1080p23 or 2160p23 (some SDR and some HDR). I also watch some sports games that are 720p60 or 1080p60.

Do you need the different profiles to assign different color gamuts (DCI-P3 and BT.2020?

[brazen1]

@Ultimathor, I use 2 profiles for DCI-P3 (HDR) and BT.709 (SDR). I know the rule of thumb is to use the same for whatever the display is calibrated to but they look better on my display to my eyes and nowhere near as good when simply applying one or the other for everything.

Tbh, I never thought I'd use so many multiple profiles for various things but as I apply them, my diverse collection of titles just keeps looking and performing better and better - automatically with no hands on required due to applying through profiles. Thank you madshi for accommodating every setting and so many keywords, operators, numerical, boolean, and string values to define profiles.

[huhn]

Not sure if this reply was intended for me?

It is my understanding that I need different profiles but if I don't gain anything from it, I'd be just as happy with just one. I mostly watch movies that are either 1080p23 or 2160p23 (some SDR and some HDR). I also watch some sports games that are 720p60 or 1080p60.

Do you need the different profiles to assign different color gamuts (DCI-P3 and BT.2020?

no you don't need profiles to do that.
you are using profile without even knowing how things work in the first place get it working first and then think about profiles

[LordX2]

I noticed some interesting things watching the spears and munsil video a couple of times.

At around 4:30 seconds the shot where the cars are zipping by on a highway in super speed drops and repeats a frame (or 2 each). Every time. Repeatable. Like I can click back 10 seconds and it happens again and again on that scene. I tried three different versions of the video. All the same thing. Render times are not over the 41.7ms mark (or at least not showing they are in the stats). But I don't think it's a render time issue since I backed down the Chroma setting as a test and it STILL happened.

Speaking of rendering times - I am noting large fluctuations (maybe normal???). The videos I am watching with my current HDR settings are averaging right around 31/32ms render times, with normal 5s high spikes up to 34-36ms. However, I am noticing some spikes up to the 39/40ms level. Is it normal to have 10ms rendering jumps like that?

Also, SOME of the spikes went ABOVE the 41.7ms cut off, with NO effect on dropped frames or present cue. How can that be?


UPDATE: This morning I went through a blitz of tests (I have a 2nd hard drive for the HTPC that I installed a fresh copy of Win10 on so I could do driver and lav filter tests without messing up my main HTPC system).

When this dropped/repeat frame happens, there IS a 1 frame lowering of the present cue.

No matter what I did, that scene always drops and repeats frames. I installed older drivers. I installed an older version of MPC-HC which had an older version of LAV Filters. I tried D3D11 Copyback, I tried DXVA Copyback (I regularly use D3D11 Native). I dropped NGU from High all the way to Low...

At this point I feel like I am chasing my tail...

UPDATE: I can't handle not being able to test the old drivers. The 3060 is becoming a nightmare. I just ordered a 3080 - which I should be able to put back to driver version 457.xx - the one I used to use. Let's see if that solves EVERYTHING. If not - I will be back! hah

[mzso]

Hello!

Is there a solution such as a pixel shader script to view VR videos on a monitor normally? (one field only, with correction for the distortion)

[Charky]

Has anyone ever experienced dropped frames and presentation glitches caused by... a perfectly still wireless mouse?

I experienced linked (ie : happening at the same time) dropped frames / presentation glitches every 20 seconds or so. Couldn't solve it no matter what settings I tried.

At one point I just had a hunch and switched off my mouse (Logitech MX Anywhere 2S, there is a on/off switch on it).

Problem solved, but the mystery remains…

[doffen]

I have the same mouse, but can't say I've experienced the same issue.
Do you use Bluetooth or the "unifying reciever" I use the unifying reciever. The firmware of my mouse is 013.000.00003.

[Charky]

Unifying reciever here. Don't know the firmware number but I believe it's up to date.

TBH between OS and drivers quirks, with custom res and DTM, madvr is starting to be more trouble than what it's really worth, especially for a piece of software that's clearly been sidelined...

[doffen]

I do know I’ve updated the firmware of either my mouse or keyboard before. You should check for updates rather than just assume it’s updated.
If you think MadVR is getting troublesome you’re free to look around for alternatives. Depending on what you want they’re out there. If you do find an alternative I’d love to hear about it!

[Charky]

I do know IÂ’ve updated the firmware of either my mouse or keyboard before. You should check for updates rather than just assume itÂ’s updated.
That was a figure of speech. I know it's up to date, I use it on 3 different PCs with Logitech Options installed.

If you think MadVR is getting troublesome youÂ’re free to look around for alternatives. Depending on what you want theyÂ’re out there. If you do find an alternative IÂ’d love to hear about it!
I've been using madvr for 6 or 7 years, and I know there aren't that many software alternatives. But when you get used to launch Disney+ or Netflix or whatever streaming app or your TV/Shield/ATV and press play, you get tired of spending an incredible amount of time tinkering with obscure settings on your HTPC rather than just watching content, and praying the next OS/Driver update won't break HDR, custom timings or whatever this Rube Goldberg machine my HTPC has become.

[claw]

I have madVR configured for tone mapping to SDR BT2020 output.

No issues until I started testing 4K120 game output with RTX 3080 Ti and G-Sync enabled connected to an LG CX OLED for VRR.

With G-Sync enabled in the 3080 Ti, even if I changed resolution back to 4K23, the LG sees the SDR BT2020 input as HDR. My JVC RS500 projector also reports HDR input. If I go back into Nvidia Control panel, change to 4K120, disable G-Sync, and then set resolution to 4K23, the LG no longer sees HDR. My HDfury devices confirm that with G-Sync ON, it receives SDR BT2020 HDR.

So what's the deal with this? Nvidia driver is 471.68.

[LordX2]

It looks like BITSTREAMING the audio is causing these dropped/repeated frames..... finally narrowed it down today.

What are my options here? I love my bitstreamed audio!

Update: I lowered my version of MPC-HC to last year - .74 LAV Filters.... now no more dropped/repeat frames. What is in the newer versions that could cause this?

[LordX2]

So, I finally sat down to watch something - played perfectly. Audio perfect, and just the two normal dropped frames from 23.976 content playing for 2 hours.



To recap for anyone else having stuttering/glitch issues:



1. To fix the glitch after 30 seconds of playback, a fix from Nvidia is available here: https://nvidia.custhelp.com/app/answers/detail/a_id/5157



2. With this fix applied, I was having drop/repeat frames at certain points in video playback. Found out it was my LAV Filters, moved back to a version from a year ago (.74 something). This solved the issue.



I don't know if the issues are connected, or I am just super unlucky.



Thank you to everyone who gave suggestions, tips, fixes - and for putting up with me!

[LordX2]

Is there a way to have the settings menu "exploded"?

I don't have to change enough settings to warrant multiple profiles - but when I want to tweak something, it is a minor annoyance to have to have to click the drop downs next to the section I need to tweak. Having everything exploded all the time would be a nice setting option.

[brazen1]

The madVR GUI size is stretched too far horizontally and not enough vertically for me - layout looks like a letter envelope and would be more functional if the layout was more like a playing card. Is this the same for others and can it be resized somehow - possibly in a registry value?

[SamuriHL]

All those options in the beta versions are not meant to stay. They are there for testing while the tone mapping is tweaked/improved. Madshi has been very clear that UI updates around settings is not a priority for the betas at all. If anything, he's introduced quite a few bugs in that area and hasn't spent any time worrying about them because he wants those options to disappear.

[clsid]

I was having drop/repeat frames at certain points in video playback. Found out it was my LAV Filters, moved back to a version from a year ago (.74 something). This solved the issue.Instead of using old LAV version, you can also try disabling "Auto A/V sync correction" in LAV Splitter settings. Instead of a video glitch you may get an (inaudible) audio glitch.

[LordX2]

Instead of using old LAV version, you can also try disabling "Auto A/V sync correction" in LAV Splitter settings. Instead of a video glitch you may get an (inaudible) audio glitch.

That was one of the first things I tried. Didn't rectify the issue.

Am I missing anything mission critical from using .74 vs .75?

[ryrynz]

Am I missing anything mission critical from using .74 vs .75?Nope.

If you can jump through the nightlies though n figure out the change that caused it though that would be nice.

[LordX2]

I am curious too - I just made the same changes on my dad's HTPC. Also had to drop down. He has a different computer, but exact same 3060 (I bought them together).

The tech in me wants to know which version of LAV makes this happen. The part of me that likes being married knows better. If I go back and start fiddling after declaring 'victory' on this - I may need a place to sleep!

[toki]

alright, so I use colourspace to upload 3dluts to madvr. After updating to windows 11, I cannot upload my lut to the correct monitor. It always uploads to my main monitor which is not the one I want that lut to be put in. Has anyone else run into this issue with windows 11? I've tried multiple things in display setting, and nothing worked. I tried making my 2nd monitor the main monitor and the numbers wouldn't even change. My primary monitor just stayed 1 even though I made the other display my main display.

[LordX2]

I never thought to ask: Does 32 bit or 64 bit make a difference with MPC-HC and MadVR?

I have always been using the 64bit MPC-HC installs.

[ryrynz]

I have always been using the 64bit MPC-HC installs.

As you should. For the core player itself and madVR it's not a big difference AFAIA but for LAV (internal filters for MPC-HC) it makes a big difference when it comes to decoding files.

[flossy_cake]

I have a weird random monitor driver bug that is affecting MadVR.

The problem is that is every now and then on boot, Windows somehow fails to load its generic monitor driver (code 38 error message in Device Manager) and when this happens, Windows assigns the monitor a new device ID that tricks MadVR into thinking I've connected a completely new monitor.

Since MadVR stores its monitor settings separately for each monitor based on the monitor's device ID, this means when this Windows driver bug strikes, I lose all my monitor settings in MadVR, which includes the auto resolution switching stuff among other critical settings.

Therefore to work around this issue I was wondering if it's possible to somehow tell MadVR to use global monitor settings that apply to every new monitor regardless of the monitor's device ID.

I know there's got to be some "default monitor settings" data structure in MadVR that it loads from when it creates a new monitor entry in its devices tab, but I don't know where it's stored or how to modify it.

Basically I want to override the default monitor settings that MadVR uses when it adds a new monitor to its devices tab.

https://i3.lensdump.com/i/gnfEsA.png

[LordX2]

As you should. For the core player itself and madVR it's not a big difference AFAIA but for LAV (internal filters for MPC-HC) it makes a big difference when it comes to decoding files.

So having the 64bit LAV filters makes a big difference?

That was my thought with the 32 bit - see if the 32bit current MPC-HC worked (which I believe comes bundled with the 32bit LAV filters).

But if there is an obvious and noticeable reason to not use 32bit LAV filters, I will stay away from that idea.

[Siso]

Yeah, this is interesting, I've always used LAV filters 32 bit.

[SamuriHL]

If you're on a native 64bit processor, running a 64 bit OS, then using 64 bit LAV is going to matter. The real issue is one of memory. With these larger files, the more memory you can access the better. 64 bit processes allow access to more memory.

[Siso]

If you're on a native 64bit processor, running a 64 bit OS, then using 64 bit LAV is going to matter. The real issue is one of memory. With these larger files, the more memory you can access the better. 64 bit processes allow access to more memory.

Meaning better performance?

[clsid]

I just ran a small performance test (with GraphStudioNext) as illustration, software decoding a small 10-bit hevc sample:

32-bit => 200 fps
64-bit => 324 fps

So 62% faster! This can of course be more or less in other cases.

With hardware decoding, perf difference is minimal, but nonetheless there is absolutely no fucking reason at all to use 32-bit (unless you use crap like reclock). Functionality and stability wise there is no difference at all.