madVR - high quality video renderer (GPU assisted)

[Asmodian]

Originally Posted by tp4tissue

bugs for Turing series cards.

I have a Turning, what issues are you referring to?

[Siso]

Originally Posted by Asmodian

I have a Turning, what issues are you referring to?

Indeed, what issues?

[SamuriHL]

They aren't bugs, they're nVidia changes that madvr needs to be updated to handle around HDR.

[Siso]

Originally Posted by SamuriHL

They aren't bugs, they're nVidia changes that madvr needs to be updated to handle around HDR.

It applies to HDR only, right? Not SDR?

[huhn]

the turing "bug" is limited to user that need to lower the present queue to avoid judder.

no one has reported that they couldn't fix this issue in the last i don't know 18 month or so...

[jkauff]

I have a GTX 1660 Super in my desktop (4K monitor) and a GTX 1080 in my HTPC. I use the same madVR settings on both, and they perform pretty much identically.

[Filmgeek47]

Originally Posted by Obveron

So madvr 3d still works well with Nvidia's last official 3d vision driver, 425.31. If you use a newer driver with 3d vision injected it breaks madvr framepacking support. It will kick the output into framepacking just fine, but it renders as side-by-side despite the output being in framepacked. I suspect there's something wrong in how madvr detects the output is in 3d framepacked, it may be as simple as that new nvidia driver versions are wrongly ignored by madvr (maybe an assumption that the new drivers don't support 3d, which they do fine if you inject 3d vision into the driver)

FYI, new nvidia drivers with 3d vision works excellent in 3d games, and 3d framepacked MVC players like Stereoscopic player and PowerDVD also work fine. (but can't compare to madvr quality!)

Just an addendum to this... Madshi has mentioned over at Avsforum that he's got a private beta running that has apparently fixed this issue. No idea when it will be freely available, but it's good to know that there's a solution in the pipeline.

[wolfman2791]

Guys... just take the time to learn MPV and the options, shaders, etc. I've got it looking just as good, and even slightly better, than madvr. It was about a month of learning curve (I didn't have a lot of time to spend on it). Well worth it though. Now I don't have to worry about updates that may or may not happen.

[Greenhorn]

Originally Posted by wolfman2791

Guys... just take the time to learn MPV and the options, shaders, etc. I've got it looking just as good, and even slightly better, than madvr. It was about a month of learning curve (I didn't have a lot of time to spend on it). Well worth it though. Now I don't have to worry about updates that may or may not happen.

I'd say MPV has far less than a month's learning period (maybe a long afternoon's) if you're used to editing config files by hands and reading FOSS documentation for work or pleasure, but possibly more than a month otherwise.

MPV vs MPC/PotPlayer/Zoom(?) is probably a better comparison than MPV vs madVR, and I really don't see an overlap between their target audiences at all. It's a flexible and powerful piece of software, but just absolutely not for someone who only wants to watch their collection in good quality with minimal startup time.

Stax's mpv.net is a good intermediate, but still (self-acknowledged as being) for advanced users.

[wolfman2791]

It's more about doing research about all the 3rd party shaders, possible combos, testing... and then setting up profiles, figuring out how to toggle by editing the input sheet, etc.

I got it running ok after a day or two... but it took me a month of tweaks to get it exactly the way I wanted it.

[chros]

Originally Posted by wolfman2791

It's more about doing research about all the 3rd party shaders, possible combos, testing... and then setting up profiles, figuring out how to toggle by editing the input sheet, etc.

I got it running ok after a day or two... but it took me a month of tweaks to get it exactly the way I wanted it.

Can you share it on the mpv.net thread?
I'm interested in how to set up monitor profiles and how to create/use 3dlut.
Thanks

[dbezerra]

Originally Posted by wolfman2791

Guys... just take the time to learn MPV and the options, shaders, etc. I've got it looking just as good, and even slightly better, than madvr. It was about a month of learning curve (I didn't have a lot of time to spend on it). Well worth it though. Now I don't have to worry about updates that may or may not happen.

But can you achieve the same tone mapping results ? That's the #1 reason I have to stick with MadVR (beta builds from AVSForum)

[chros]

Originally Posted by dbezerra

But can you achieve the same tone mapping results ? That's the #1 reason I have to stick with MadVR (beta builds from AVSForum)

In theory, you can with Win 10 Api (since 1804). The only question for me is the multimonitor profiles, that madvr supports (and 3dlut).

[Rusty100]

Is this thread appropriate for technical questions/problems? If so, does anyone know what would be causing a colour change when fullscreening 8bit sdr content on a 10bit display (samsung g7) with D3D11? When I set MadVR to auto, it doesn't autodetect when it's in 10/HDR. So even in Windows HDR mode, HDR does not passthrough to the display.
If I set native bit depth to 10 myself, HDR content is fine and great, and so is 8bit content outside of Windows' HDR mode, except when I fullscreen it. The colour gets brighter and duller, and it doesn't revert even when the file is closed. It washes out the whole monitor. I have to turn HDR on and then off again for the normal colour vibrancy to return. So far as I can figure only D3D11 does this, and only when native bit depth is set to 10 bit (but when HDR mode is not turned on). I have to manually change MadVR from 10 to 8 or auto when I want to watch SDR content. This also only happens on my new G7 and this does not happen on my X900F.

[dbezerra]

Originally Posted by chros

In theory, you can with Win 10 Api (since 1804). The only question for me is the multimonitor profiles, that madvr supports (and 3dlut).

Do you have a pointer to initial instructions, settings I could try?

[huhn]

can someone that has done CRU and similar or is using it right now install the newest nvidia driver and check the stock refresh rate? i'm on AMD currently.

[Asmodian]

For the standard 23Hz mode over HDMI I see 23.97586 Hz with very good frame drop/repeat numbers. Looks pretty good.
For the same mode over DP (with the CAC-1085 converting to HDMI) I see 23.97995 Hz. Interesting.

2080 Ti, 451.67, Win10 2004

Is this what are you were looking for?

[huhn]

yes madshi got a bug report through with this and they fixed it.

the refreshrate is supposed to be closer now with 1080p23 (for a while now) and now with 2160 23 now too with this driver or up coming ones.

looks like they have to fix this with every signle refreshrate and connector type...

just took them like a decade and it doesn't fix the core issue anyway.

edit: i just test my 1060 i have no frame repeat/drop expected ever with analog audio output so very lucky.
can a couple you guys test digital hdmi/DP over the same card that the only space where nvidia has any way to affect the audio clock?
i tested 451.77 studio.

edit2: can you plz check 119? if you have the time for 1440p and 2160p DP/HDMI if available.
i will try to check 1080p119 my TV doesn't support 1440 for some reason.
edit3: 1080p119 is working too.

[SamuriHL]

That's annoying. Great that they fixed it. But given the problems with HDR and this new branch of drivers, this sucks.

[Asmodian]

Originally Posted by huhn

edit2: can you plz check 119? if you have the time for 1440p and 2160p DP/HDMI if available.

My previous report was actually for 2160p23, I didn't think to try other resolutions.

HDMI
2160p23: 23.97586
1080p23: 23.97751
1080p119: 119.87947


For 1440p I only have a 120 Hz option, nothing else. Not even 60Hz. It runs at 120.000Hz. Having trouble getting DP to display anything right now.

Edit:

Display Port
2160p23: 23.97592
1080p23: 23.97752
1080p119: 119.87953

After some more fiddling and a reboot I am getting 23.97592 Hz from 2160p23 out of the Display Port through the CAC-1085. I don't have a 119 mode to test when using this adapter, only 100 and 120 Hz for above 60. I also saw the ~23.980 Hz from HDMI for a bit, fixed by a reboot, so maybe it can get stuck in the slightly different mode? It is interesting because the composition rate also changes between 23.976 and 23.980 Hz. I haven't been able to get it to do it again though so I am not sure why it changes.

Very cool to have Nvidia finally fix this (at least mostly)... now we just need madVR to update how it uses the HDR API.