View Full Version : madVR - high quality video renderer (GPU assisted)
I wonder if InSpectre (https://www.grc.com/inspectre.htm) helps with those 1803 performance issues. Maybe also try disabling D3D11.
ashlar42
3rd May 2018, 16:46
Considering the still ongoing GPU price madness, I wonder: is a 6GB GTX1060 useful for madVR or would the 3GB version suffice? I ask because as far as computation power is concerned they don't seem too distant (1060 3GB being clearly more powerful than a 1050Ti) but I wouldn't want to "castrate" the system if video RAM is going to be important in madVR.
nevcairiel
3rd May 2018, 16:49
Prices are actually normalizing, many cards have gone back down to their MSRP and may continue falling. Anyhow personally I would always go with the 6GB variant. 3GB can work if you limit the queue size a bit and whatnot, but it can be a limiting factor.
Ver Greeneyes
3rd May 2018, 17:13
My laptop has a GTX1060 with 3GB of memory and nevcairiel is right: It's pretty powerful, but I have to lower the queue sizes or it chugs at random intervals. I'd get the 6GB version if you have the option.
leeperry
3rd May 2018, 17:33
That's there, under 'deblocking - toggle'
OK thanks, that wasn't self-explanatory at all and I never used the ShowRenderSteps thingie.
So it implies that RCA is a deblocker? I figured it was some neuro psychic guessing crazy algorithm, I guess that'd explain why it doesn't like grain then.
With Win 10 1803 Radeon 18.4.1 even if I have 10bit enabled in Windows, madVR reports D3D11 fullscreen windowed 8bit!?
Warner306
4th May 2018, 00:35
With Win 10 1803 Radeon 18.4.1 even if I have 10bit enabled in Windows, madVR reports D3D11 fullscreen windowed 8bit!?
This is normal. You need to use fullscreen exclusive mode to output at 10-bits with Nvidia when doing HDR passthrough. SDR playback in unaffected. This is due to a driver bug.
Crimson Wolf
4th May 2018, 02:45
This is normal. You need to use fullscreen exclusive mode to output at 10-bits with Nvidia when doing HDR passthrough. SDR playback in unaffected. This is due to a driver bug.
Am I mistaken? I thought the Windowed Fullscreen 8-bit was a bug in the latest version of madvr (92.14) because it still works with 92.12 which I'm still using.
Asmodian
4th May 2018, 03:04
It is a bug in a feature that was implemented in 92.13 to prevent sending 10 bit HDR video to Nvidia's drivers, madVR only outputs 8 bit with both SDR and HDR but the issue with 10 bit banding only happens when using fullscreen windowed with Nvidia's HDR mode.
khanmein
4th May 2018, 05:58
FSE mode is working with 397.55 again so it might or not related to Windows.
My laptop has a GTX1060 with 3GB of memory and nevcairiel is right: It's pretty powerful, but I have to lower the queue sizes or it chugs at random intervals. I'd get the 6GB version if you have the option.
When you lower the queue sizes, does it still chug or what happens ? I only have the option gtx1050ti or 1060 3gb.
Asmodian
4th May 2018, 06:11
No, with lower queue sizes it is fine. I suggest you think about the 4GB 1050Ti over the 3GB 1060 if you plan on 4K content and/or 4K output.
Magik Mark
4th May 2018, 06:29
FSE mode is working with 397.55 again so it might or not related to Windows.
How about custom refresh rate?
Sent from my iPhone using Tapatalk
khanmein
4th May 2018, 06:48
How about custom refresh rate?
Sent from my iPhone using Tapatalk
I didn't use any custom refresh rate. You can try it. I will try to test again 379.31 with the latest DDU.
Conclusion, latest DDU + 379.31 + FSE = freeze
This is normal. You need to use fullscreen exclusive mode to output at 10-bits with Nvidia when doing HDR passthrough. SDR playback in unaffected. This is due to a driver bug.
But as stated in my post, I'm using a Radeon Card.
Also, using FSE made no difference. SDR/HDR - it all reports running in 8bit, even when Radeon Control Panel clearly states 10bit.
It is a bug in a feature that was implemented in 92.13 to prevent sending 10 bit HDR video to Nvidia's drivers, madVR only outputs 8 bit with both SDR and HDR but the issue with 10 bit banding only happens when using fullscreen windowed with Nvidia's HDR mode.
Thanks for this, seems like the bug/feature also prevents sending 10bit to Radeon.
It would be great if madshi could elaborate a bit more in the changelog - this thread is a beast and hard to find these issues without reading pages upon pages.
No, with lower queue sizes it is fine. I suggest you think about the 4GB 1050Ti over the 3GB 1060 if you plan on 4K content and/or 4K output.
Thanks, but the 3GB 1060 is 1.5x more powerful than the 1050ti, which may be helpful in madVR settings. That's why I am still not decided.
ryrynz
4th May 2018, 09:40
Is there any hard data for suggesting a 4GB card over a 3GB one for 4K?
Ver Greeneyes
4th May 2018, 10:22
I've successfully upscaled to 4K using my laptop's 3G GTX1060, but I think it did require reduced queue sizes, and I only got it to run smoothly if I set the 4K monitor as the only monitor. Whether a 4GB card would fix those issues is another question of course.
jkauff
4th May 2018, 11:02
Thanks, but the 3GB 1060 is 1.5x more powerful than the 1050ti, which may be helpful in madVR settings. That's why I am still not decided.
I think the suggestion was based on the fact that the 1050ti has an on-board hi-res decoder, while the 1060 does not.
the difference is a VP9 profile 2 decoder.
3 GB will work for sure if NGU is not used. it should work with NGU and well you may need tweaking.
oldpainlesskodi
4th May 2018, 11:39
Whilst not strictly related to MadVR, one last thing to share for those with a Samsung SUHD set with MadVR - set your display to Games Console and set picture mode to Game for SDR and HDR material (Colour Space set to Native for SDR and Auto for HDR) - this disables virtually all image destroying features, leaving you to enjoy MadVR in all it's glory.
nevcairiel
4th May 2018, 11:41
That rule pretty much applies to most TVs - in Game Mode or PC Mode, you basically get a "dumb" screen that just displays what its given.
Ver Greeneyes
4th May 2018, 12:05
Hmm, my present queue isn't filling up anymore, it stays at 0-2/15 and I'm dropping frames all over the place. I probably should have noticed this before but I haven't watched a lot of videos using MPC-HC in the past few days. I just went back to the previous GeForce drivers (391.35) so I think it must be the Windows 10 April 2018 update causing it. FSE freezes for me, too. Is this what others have been seeing? I don't have the game bar or any other overlays enabled.
Edit: Going to try the hotfix driver (397.55) (http://nvidia.custhelp.com/app/answers/detail/a_id/4661), saw some people reporting it fixes FSE mode.
Edit2: FSE mode seems to be working (and queues fill up in FSE mode), though there's a big delay so I'm wondering if I just didn't wait long enough before. Windowed mode is still busted. I noticed that FSE mode also switches my display mode back from 60Hz to 59.95Hz, annoyingly.
Edit3: Okay, I got it to use 60Hz by explicitly adding 2560x1440p60 to the list of modes it's allowed to switch to.
oldpainlesskodi
4th May 2018, 12:06
That rule pretty much applies to most TVs - in Game Mode or PC Mode, you basically get a "dumb" screen that just displays what its given.
Yeah, that's what I thought, but with the Samsung SUHD's, PC mode activates crap that Games Console set at Game Mode deactivates.
only Pc modes stops downsampling on Samsung screens and it is often only available at 30 and 60 hz.
so GL with gaming mode and full glory madVR on Samsung screens.
if chroma subsampling is not image destroying feature than what is one?
oldpainlesskodi
4th May 2018, 12:49
only Pc modes stops downsampling on Samsung screens and it is often only available at 30 and 60 hz.
so GL with gaming mode and full glory madVR on Samsung screens.
if chroma subsampling is not image destroying feature than what is one?
I don't do gaming, so my rig is exclusively set as a HTPC, and 99.999% of all content I watch is 23.976.
Anyway, sorry for being off topic, was only sharing my findings that may help other Samsung SUHD owners who use MadVR.
Whilst not strictly related to MadVR, one last thing to share for those with a Samsung SUHD set with MadVR - set your display to Games Console and set picture mode to Game for SDR and HDR material (Colour Space set to Native for SDR and Auto for HDR) - this disables virtually all image destroying features, leaving you to enjoy MadVR in all it's glory.
What about the LG OLED TV's ? B6 , C6
for HDR you need to choose Game Console/HDMI instead PC Input , And choose HDR Standard Picture mode
what is GL ?
jmonier
4th May 2018, 14:24
Is there any hard data for suggesting a 4GB card over a 3GB one for 4K?
Yes. I and others have reported that 4k uses about 3.5 GB.
it is possible to make 3 GB work(i can even make 2GB work) but i stay at my Vram statement get a 4 Gb card for UHD.
oldpainlesskodi
4th May 2018, 14:55
What about the LG OLED TV's ? B6 , C6
for HDR you need to choose Game Console/HDMI instead PC Input , And choose HDR Standard Picture mode
what is GL ?
Sorry I don't have an LG.
I have no idea what GL means.
So which mode should I use ?
Windows HDR Enabled + Madvr 10bit + HDR Passthrough + TV GameConsole/HDMI Input + Full Windowed or FSE ?
Windows HDR Disable + " + " " + " " + Full Windowed or FSE ?
Because Windows HDR gives 8 bit + Dithering in Windowed and maybe FSE I think, and MadVR gives 8 bit when Full Windowed mode.
So which is the best choice ?
Would I notice any quality differences between 8bit Windows HDR and Madvr 8 bit Nvidia ? and also differences in MadvR 10 bit FSE ?
Warner306
4th May 2018, 16:30
So which mode should I use ?
Windows HDR Enabled + Madvr 10bit + HDR Passthrough + TV GameConsole/HDMI Input + Full Windowed or FSE ?
Windows HDR Disable + " + " " + " " + Full Windowed or FSE ?
Because Windows HDR gives 8 bit + Dithering in Windowed and maybe FSE I think, and MadVR gives 8 bit when Full Windowed mode.
So which is the best choice ?
Would I notice any quality differences between 8bit Windows HDR and Madvr 8 bit Nvidia ? and also differences in MadvR 10 bit FSE ?
It is unknown what Windows does to the image, but the images should be identical between the two.
The best set up is to use the Nvidia private API (passthrough - send metadata), so you don't have to toggle HDR on and off. This is clearly most convenient.
To get 10-bit passthrough, you must enable fullscreen exclusive mode until there is a fix a the driver level for banding with 10-bit HDR passthrough when set to windowed mode. SDR playback is unaffected by this bug.
oldpainlesskodi
4th May 2018, 16:31
So which mode should I use ?
Windows HDR Enabled + Madvr 10bit + HDR Passthrough + TV GameConsole/HDMI Input + Full Windowed or FSE ?
Windows HDR Disable + " + " " + " " + Full Windowed or FSE ?
Because Windows HDR gives 8 bit + Dithering in Windowed and maybe FSE I think, and MadVR gives 8 bit when Full Windowed mode.
So which is the best choice ?
Would I notice any quality differences between 8bit Windows HDR and Madvr 8 bit Nvidia ? and also differences in MadvR 10 bit FSE ?
Windows HDR Disable + " + " " + " " + FSE
Edit - looks like Warner306 and I commented at the same time
It is unknown what Windows does to the image, but the images should be identical between the two.
The best set up is to use the Nvidia private API (passthrough - send metadata), so you don't have to toggle HDR on and off. This is clearly most convenient.
To get 10-bit passthrough, you must enable fullscreen exclusive mode until there is a fix a the driver level for banding with 10-bit HDR passthrough when set to windowed mode. SDR playback is unaffected by this bug.
Windows HDR Disable + " + " " + " " + FSE
Edit - looks like Warner306 and I commented at the same time
Ok thanks . FSE is so annoying, takes ages until the images start to play when going in FSE. out is ok
truexfan81
4th May 2018, 17:54
evga 1050ti fw latest nvidia driver, windows 10 1803 madvr 0.92.10
any idea whats going on here?
https://i.imgur.com/m1Qbgi8.jpg
thanks
Asmodian
4th May 2018, 17:55
Try small buffers, I like 6 for GPU buffers and 4 fames presented in advance. I have noticed that smaller buffers perform better than giant ones.
Also, it looks like you are not using the default flush and wait options? Put those back to the defaults.
FSE is so annoying, takes ages until the images start to play when going in FSE.
Can you actually see any difference with 10 bit compared to 8 bit? I simply use 8 bit all the time, 10 bit is very unimportant for madVR's video out. Dithering FTW.
truexfan81
4th May 2018, 18:04
Try small buffers, I like 6 for GPU buffers and 4 fames presented in advance. I have noticed that smaller buffers perform better than giant ones.
Also, it looks like you are not using the default flush and wait options? Put those back to the defaults.
Can you actually see any difference with 10 bit compared to 8 bit? I simply use 8 bit all the time, 10 bit is very unimportant for madVR's video out. Dithering FTW.
edit: I got it, had to add another profile for my image enhancements to turn them off for 50/60fps videos.
Asmodian
4th May 2018, 18:31
The reason this wasn't immediately obvious when looking at the OSD was because you turned off all the "wait" options in the "when and how shall the GPU be flushed:" section of windowed mode, "after the last render step" should be one of the wait options so madVR can report rendering times.
Ver Greeneyes
4th May 2018, 20:45
evga 1050ti fw latest nvidia driver, windows 10 1803 madvr 0.92.10
any idea whats going on here?
I'm having the same issue, I think Windows 10 1803 changed something that broke windowed mode. Using FSE mode is the only workaround I've found.
iakoboss7
4th May 2018, 22:00
hello, anyone noticed reduced average rendering time with the new windows 10 update?
in files where i got ~10ms now i get ~5ms. playback is perfect as always.
am i the only one? i didnt find any mention in the last 10 pages.
rx 480 with latest drivers.
also about the low (0-1) queues many have (alongside dropped frames), the culprit is freesync.
when i disable it everything is fine. its not windows fault. this started with the last madvr versions.
also reclock doesnt work that well at the same time...
Betroz
4th May 2018, 22:48
also about the low (0-1) queues many have (alongside dropped frames), the culprit is freesync.
when i disable it everything is fine. its not windows fault. this started with the last madvr versions.
also reclock doesnt work that well at the same time...
Not for me. I have this problem, and it's not that. I use an old plasma TV from Panasonic, so no freesync there ;)
Also the queues fill up nicely with an older version av MadVr with NNEDI3 128 settings. Even with queue size of 24.
cyberscott
4th May 2018, 22:54
What about the LG OLED TV's ? B6 , C6
for HDR you need to choose Game Console/HDMI instead PC Input , And choose HDR Standard Picture mode
what is GL ?
I own a LG C6. I can play HDR videos perfectly fine with the C6 set to PC Input. I can also play HDR compatible PC games in the same mode.
I mainly use my C6 as a big monitor.
FDisk80
4th May 2018, 23:05
How about custom refresh rate?
Sent from my iPhone using Tapatalk
Nope, still busted with 397.55.
madVR gives this error when trying to apply custom timings.
https://i.imgur.com/DQyqn7D.png
Nope, still busted with 397.55.
madVR gives this error when trying to apply custom timings.
Is this still with 1080p?
Do you also get this error if you select EDID/CTA? That's the only option that works for me with my JVC PJ, and it gives me 1+ hour of drop free playback (with 4K/UHD though, I haven't tested 1080p). I haven't tried the latest driver, but it worked with all the former ones (which you reported as not working as well).
Ver Greeneyes
4th May 2018, 23:25
Also the queues fill up nicely with an older version av MadVr with NNEDI3 128 settings. Even with queue size of 24.
Hmm, good point. I checked the repository of old versions (https://www.videohelp.com/software/madVR/old-versions#download) and the last version in which the queues fill is v0.91.5. In v0.91.6 and newer the queues no longer fill.
However, even in v0.91.5 the queues only fill up to 5-7/15 for me. I'm also fairly sure the regression itself is caused by the update to Windows 10, even if older versions of madVR managed to avoid it.
Edit: Aha, NGU seems to be the culprit somehow. v0.91.6 introduced NGU Anti-Alias (https://forum.doom9.org/showthread.php?p=1799592#post1799592), which I was using for chroma upscaling. If I enable NGU for chroma upscaling in v0.91.5 the queues stop filling, even if I select the "low" quality option which gives me an average rendering time of 4.5ms.
Edit2: Yes, going back to v0.92.14 if I set chroma upscaling to Bicubic60 I get 5-7/15 like in v0.91.5. If I use super-xbr I get 2-4/15 (even though the rendering time is practically unchanged at 3.5ms) and if I select NGU I get 0-2/15 and it starts dropping frames. Is it running into some sort of windowed mode GPU memory usage limit or something??
Asmodian
5th May 2018, 00:24
I own a LG C6. I can play HDR videos perfectly fine with the C6 set to PC Input. I can also play HDR compatible PC games in the same mode.
I mainly use my C6 as a big monitor.
You can use HDR in PC mode but, on the C7 at least, the gamut coverage is much worse. Home theater or similar offers better HDR rendering but also uses 4:2:2 color subsampling. :(
mlauzon
5th May 2018, 00:29
I keep hearing about MadVR, but have no idea how to use it, can someone ELI5 please & thank you..?!
FDisk80
5th May 2018, 00:34
Is this still with 1080p?
Do you also get this error if you select EDID/CTA? That's the only option that works for me with my JVC PJ, and it gives me 1+ hour of drop free playback (with 4K/UHD though, I haven't tested 1080p). I haven't tried the latest driver, but it worked with all the former ones (which you reported as not working as well).
Yes, this is a 1080P HDTV.
I can't even apply EDID/CTA, the test button is grayed out because those are already the timing that are being used by default when switching to 1080P@23hz mode.
https://i.imgur.com/lAnxdG8.png
But it's not optimal. Those timings result in 23.977hz and there is a frame repeat every 2 or 3 minutes.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.