View Full Version : madVR - high quality video renderer (GPU assisted)
QBhd
7th November 2018, 07:31
Upscale with NGU then downscale with SSIM, NGU is only an upscaler, SSIM is only a downscaler.
I prefer this as my primary sharpening process.
I totally agree with this as well... I don't use any other upscaling refinement or image enhancements.
QB
70MM
7th November 2018, 07:38
Upscale with NGU then downscale with SSIM, NGU is only an upscaler, SSIM is only a downscaler.
I prefer this as my primary sharpening process.
Do you use a 4K display?
Anima123
7th November 2018, 08:28
I like NGU AA over NGU soft for content that needs a more natural looking upscale. 720 -> 1080 is a pretty small upscale so differences are more subtle but you don't like NGU AA for that?
No, I prefer NGU Soft more, since not only the picture, but also the hardcoded subtitle looks more natural with NGU Soft, comparing with NGU AA.
Betroz
7th November 2018, 09:14
I don't think NGU Sharp is too sharp when you upscale 1080p to 2160p. Any reason why NGU AA would be better here?
madjock
7th November 2018, 10:41
I don't think NGU Sharp is too sharp when you upscale 1080p to 2160p. Any reason why NGU AA would be better here?
There is no right or wrong, the majority is down to personal taste. It is the same with people asking for settings for a certain video card, there is no point. Some like a sharper picture, some say that in itself creates issues, so whatever you like is what matters.
HDR
7th November 2018, 11:21
Do you use a 4K display?
He already stated he can't afford one.
ryrynz
7th November 2018, 12:39
LOL, got more than enough in the bank to buy the best TV on the shop floor, thank you very much. Any mods around?
Warner306
7th November 2018, 14:51
He already stated he can't afford one.
If you are rolling in money, why don't you just upgrade your GPU? The GTX 960 is getting old. I don't understand the argument that an OLED will improve image quality but a GTX 1060 - 1080 won't. You aren't using the maximum settings. They aren't meant to be a placebo.
Also, there are still no 4K displays with HDMI 2.1 or any that can display an HDR image up to 4,000 nits without tone mapping with an infinite contrast ratio. 4K HDR is still in the early adopter phase.
mclingo
7th November 2018, 17:35
a lot of this is getting into general territory and spamming the thread a bit, if people genuinely want to thrash this out why dont you go to the general thread.
- remember MADSHI has to read through all this, its just a waste of his precious coding time :)
https://forum.doom9.org/showthread.php?t=175769
DoXer
7th November 2018, 17:39
Some time ago madshi posted this (https://forum.doom9.org/showthread.php?p=1810891#post1810891)
Is it still up to date to prefer Windows 8.1 and NVIDIA?
For the moment I'm testing with AMD RX560 and Windows 10 1809 Enterprise and KODI DS 17.6, but sometimes the screen gets no signal after a movie finished and I must reset the PC.
mclingo
7th November 2018, 17:53
Some time ago madshi posted this (https://forum.doom9.org/showthread.php?p=1810891#post1810891)
Is it still up to date to prefer Windows 8.1 and NVIDIA?
For the moment I'm testing with AMD RX560 and Windows 10 1809 Enterprise and KODI DS 17.6, but sometimes the screen gets no signal after a movie finished and I must reset the PC.
ive had that myself and still get it with 3D movies. (no longer crashes PC though)
As a test - Do you have Full screen exclusive mode ticked, try that. Also remove any 1080p display modes from MADVR if you are upscaling everything to 4K, or use refresh rate switching on you video player instead
Are you sure its crashing the PC, try RDP on to check its not just lost HDMI link.
DoXer
7th November 2018, 18:17
As a test - Do you have Full screen exclusive mode ticked, try that.
I have no success to enable FSE. It's enabled in madVR und Kodi.
Also remove any 1080p display modes from MADVR if you are upscaling everything to 4K, or use refresh rate switching on you video player instead
I only have 2160pXX-modes inserted.
Are you sure its crashing the PC, try RDP on to check its not just lost HDMI link.
Indeed, it's no crash, only lost HDMI-link.
mclingo
7th November 2018, 18:26
ok then, turn off refresh rate swithing in MADVR and turn it on in KODI, see what happens. Make sure you've also got FULL SCREEN WINDOWED enabled in KODI DS as well.
mclingo
7th November 2018, 18:29
one other thing that might help, create a batch file you can run from a key press or remote, put this in it, run this when you lose HDMI, it should come back but in 23hz mode, then create another batch file for 2160p 60hz, you could try going straight to 46k 60hz but this doesnt work for me, seems to be a bug in driver or MADVR.
cd\
c:
SETRES h3840 v2160 b32 f23
Ampallang
7th November 2018, 23:52
So its me again I have now to ask for tomorroe cube measurement for 3d lut creation. I have a 3d lut for sdr with 100nite gama 2.4.
I will create tomorrow a lut for bt2020 sdr. Maximum nits 310 I can get without hdr flag. So 310 are my max nits on TV b7 with an apl25 window. Will this two LUTs work for doing the tonemapping hdr to sdr with madvr? Htpc control will be meassure then Friday my files so I can enjoy testing between hdr pass-through and hdr > sdr by madvr.
chros
8th November 2018, 10:08
Just a quick poll for you guys:
- What nvidia driver version do you use on Windows 8.1 and with which card? (you can see mine in the signature)
I'm mostly interested in pascal cards but others also can be interesting.
(I'm not interested in Win10 users :) , we already know a lot about it.)
Thanks!
nevcairiel
8th November 2018, 11:12
On my 8.1 HTPC I always just use the latest from whenever I updated it last. They don't usually break 8.1 drivers regularly, the repeated breakage is only on 10 since MS keeps changing things and NVIDIA is catching up.
chros
8th November 2018, 13:39
On my 8.1 HTPC I always just use the latest from whenever I updated it last. They don't usually break 8.1 drivers regularly, the repeated breakage is only on 10 since MS keeps changing things and NVIDIA is catching up.
Cheers, that's what I used to do as well, until: I noticed (by accident) that they changed how the different power states and their corresponding voltage work for my card with > v36x drivers. Hence I got back to v355.98 and never wanted to upgrade it again.
giulianoprs
8th November 2018, 15:31
hello to everyone, return after months to ask for a review and advice, and if I can improve the quality of vision, as a test bench I always take the tv series "the walking dead" because it contains video noise, the file is 1080p, my settings are:
artifact removal-reduce banding artifacy (active)
default debanding strength (low)
strength uring fade in / out (high)
reduce compression artifacts -2-quality MEDIUM
all the other in default.
chroma upscaling: NGU -sharp, medium quality - everything else in default.
image upscaling: NGU standard-algorithm quality medium- everything else is "let madVR decode".
upscaling refinement - all in default (here I do not understand the functions)
I must say that with these settings of mpc + madvr have improved compared to vlc or kodi17.6, a little better there is, but no more, you can still improve? any suggestions / advice?
Warner306
8th November 2018, 16:36
So its me again I have now to ask for tomorroe cube measurement for 3d lut creation. I have a 3d lut for sdr with 100nite gama 2.4.
I will create tomorrow a lut for bt2020 sdr. Maximum nits 310 I can get without hdr flag. So 310 are my max nits on TV b7 with an apl25 window. Will this two LUTs work for doing the tonemapping hdr to sdr with madvr? Htpc control will be meassure then Friday my files so I can enjoy testing between hdr pass-through and hdr > sdr by madvr.
310 nits can work for HDR -> SDR, but the image will be too dim.
Your B7 can reach 768 cd/mē with HDR output. You are probably giving up too much brightness. You want to avoid tone mapping the SDR range (0 to 100 nits), and you usually need around 500 nits peak to do this. The HDR -> SDR image will be dark and flat when it doesn't need to be.
njfoses
8th November 2018, 16:37
New Nvidia driver 416.81
mytbyte
8th November 2018, 16:49
310 nits can work for HDR -> SDR, but the image will be too dim.
Your B7 can reach 768 cd/mē with HDR output. You are probably giving up too much brightness. You want to avoid tone mapping the SDR range (0 to 100 nits), and you usually need around 500 nits peak to do this. The HDR -> SDR image will be dark and flat when it doesn't need to be.
Hmm, not sure, it certainly doesn't look flat here on a plasma with 200-ish nits peak brightness on 10% window.
But yeah it's beyond me why someone would sacrifice half the potential brightness...you profile the TV in HDR mode and make the LUT.
Warner306
8th November 2018, 17:01
Hmm, not sure, it certainly doesn't look flat here on a plasma with 200-ish nits peak brightness on 10% window.
Compared relative to not compressing the first 100 nits. But it wouldn't look offensive when tone mapped that way.
mytbyte
8th November 2018, 17:35
Compared relative to not compressing the first 100 nits. But it wouldn't look offensive when tone mapped that way.
Very dim or dark room are the key, the pop is there with those deep blacks, not at all dim in perception...
Ampallang
8th November 2018, 19:42
But yeah it's beyond me why someone would sacrifice half the potential brightness...you profile the TV in HDR mode and make the LUT.
Because you can't vibrate hdr really especially not on TV. Panel drift blue subpixel at 400 nits nothing color accurate and we don't want to write about tonemapping. I calibrate the TV profiles all but a lut isn't. Possible for hdr. If you didn't belive check you calibration with a volumic measurement and not only looking into de values without luminance.
Thats way I was thinking on the madvr attempt. No tonemapping of TV no blue subpixel on oled and no panel drift. And 310 nits aren't that low of course witu hdr I reached more than 750nits calibrate. I want to compare and I could belive that the madvr way could have some interesting look. If I didn't see any positiv pq improvements I can easily forget about and keep my hdr profile on TV.
But if you had an idea how you get correct hdr calibration and I mean verified by volume I am open to test this way also.
stiffwin
8th November 2018, 21:53
Hi - Kodi 17.6 with Dsplayer - if I launch channels from the Channels list, Madvr is activated and works as it should. But if I launch the same channel from a 'Favorite' or 'Recently played channel', Madvr is not used. Also, in System settings I select Fullscreen and Windowed, but Kodi keeps reverting to Windowed. Are there any fixes or workarounds for these behaviours?
Ampallang
8th November 2018, 22:38
Is there a LightSpace user who can explain short the settings for hdr to sdr lut creation before I start and set something wrong.
My understanding is measuring bt2020 with target 709, same for dci p3 and bt709 wide. A picture will be appreciate because measurement will take whole night and didn't want to redo this.
sat4all
9th November 2018, 09:04
You don't have to remeasure if you have already an SDR profile of your display, it's valid to generate a lut for PQ > SDR using either UHD Rec2020 or DCI P3 D65 lightspace preset, the later one give better results for me since my 2015 oled tv covers only 64% Rec2020 and 86% DCI P3.
Ampallang
9th November 2018, 16:45
Sat4all many thanks problem is the lut won't fit so maybe I used a wrong preset. Yes one of the strange of LightSpace you didn't need to remasure everything again. And with measure I mean widest gamut and then create only target LUTs on this Profil.
Warner306
9th November 2018, 18:29
Hi - Kodi 17.6 with Dsplayer - if I launch channels from the Channels list, Madvr is activated and works as it should. But if I launch the same channel from a 'Favorite' or 'Recently played channel', Madvr is not used. Also, in System settings I select Fullscreen and Windowed, but Kodi keeps reverting to Windowed. Are there any fixes or workarounds for these behaviours?
You would have to move your discussion to the DSPlayer forum because the issues are not related to madVR:
https://forum.kodi.tv/showthread.php?tid=223175
Betroz
9th November 2018, 22:06
Anybody here knows how a RX Vega 64 performs for MadVr use compared to a GTX 1080 card?
Ampallang
9th November 2018, 22:20
As far as I heard they are both equal. only nvidia can't do 10bit output and the vega needs more power.
sat4all
10th November 2018, 12:53
@madshi
I know you are busy with the HDR tone mapping algo work, but would you please consider moving GPU hard coded bars detection a little up in your to do list. Copy-back is really inefficient with UHD let alone when we add the tone mapping algos.
Thanks & Kind Regards
Ampallang
10th November 2018, 15:21
Great picture looks nice with the 3d luts.but the picture had more punch in highlights with the tonemapping shader math so far. But the colors Looks amazing. Have to test further.
mytbyte
10th November 2018, 17:25
@ampallang: did you try tweaking EOTF Nits settings in Lightspace's Convert color space dialog? I'm testing Lightspace with DPS licence but don't seem to be able to export the LUT for MadVR so can't give you any more ideas.
austinminton
11th November 2018, 07:04
I have a problem with my new rtx 2080 ti and madVR that I use with kodi and mpc-be player with lav filters 73.1 When I play primarily 4k movies, I get stuttering when using d3d11 native or copyback but much less stuttering with dxva native or
dxva copyback but still stuttering, have any others with the new 2080 card experienced the same? with my old gtx 1080 i didn't have any stuttering at all no matter if i used d3d11 or dxva and my sttings in madVR are the same, surely the new 2080 schould be able to use the same settings in madVR
Just got my asus strix 2080 ti and I am experiencing the same stuttering issues. Games are working fine. Looking at gpu clocks the gpu is not stressed at all while playing madvr. Power is set to adaptive. I have even tried default madvr settings with no image upscaling but still the same issue. Latest drivers. Any suggestions please?
Everything was fine with the 1080 that I swapped out.
Edit: No issues with evr.
Ampallang
11th November 2018, 11:10
@ampallang: did you try tweaking EOTF Nits settings in Lightspace's Convert color space dialog? I'm testing Lightspace with DPS licence but don't seem to be able to export the LUT for MadVR so can't give you any more ideas.
Not jet but will do this soon. Just verify compare the results BTW. The 3 methods 3d lut, pixelshader with and without hdr flag and normal hdr via tone mapping done by tv. Alot of tweaking can still be done I think but nice to know what will be possible and which content works on Lg oled and what didn't looks so great in my eyes.
DoXer
11th November 2018, 13:18
Hi,
after some tests with AMD RX560 now I'm testing with Nvidia 2070.
I follow a guide from hifi-forum.de. http://www.partyfotos.de/madvr/settings/
In this guide is a screenshot from madVR 0.92.11. I' have installed madVR 0.92.17.
In the HDR-settings of madVR 0.92.17 for my device I have no "Convert HDR to SDR by using pixel shader math" and "Convert HDR to SDR by using pixel 3DLUT" .
is this correct? Are these options dropped from the newest version?
http://www.partyfotos.de/madvr/settings/MadVR_Settings_009.png
Warner306
11th November 2018, 15:48
Yes, it is all different, but simplified greatly.
austinminton
11th November 2018, 16:07
Just got my asus strix 2080 ti and I am experiencing the same stuttering issues. Games are working fine. Looking at gpu clocks the gpu is not stressed at all while playing madvr. Power is set to adaptive. I have even tried default madvr settings with no image upscaling but still the same issue. Latest drivers. Any suggestions please?
Everything was fine with the 1080 that I swapped out.
Edit: No issues with evr.
After spending about 8 hours trying to debug this I have finally figured out the problem. While playing a video on my TV (connected via HDMI), I get a lot of CPU usage with no load on the GPU. LAV video shows <none> in the active hardware decoder. If I play the video on my PC monitor I get RTX 2080 ti as the video decoder and very little load on the CPU. I have tried DDU + reinstall drivers with no success. Any suggestions would be greatly appreciated as I am practically at my wits end trying to figure this out. Thanks in advance.
el Filou
11th November 2018, 16:19
Is your TV connected to the iGPU and the monitor to the discrete NVIDIA?
austinminton
11th November 2018, 16:28
Both connected to the NVIDIA.
el Filou
11th November 2018, 19:04
Did you try switching between the various DXVA/D3D11 options and see if some of them give a different result?
Is the monitor set as the first screen in the dual display setup?
ryrynz
11th November 2018, 21:15
Why not just disable the iGPU in the BIOS?
austinminton
12th November 2018, 02:07
I went for the nuclear option of installing a fresh copy of windows on a new partition. Now I have hardware acceleration on both my PC monitor and TV. The GPU gets load when madvr is running on the TV as well. But the stuttering issue still persists. I have tried making the TV my main monitor. I have also removed my PC screen with my TV as the only monitor. Rendering times are well within limits at about 20ms with NGU high for scaling and chroma. On windows 1803 with latest nvidia drivers 416.81 and Lav on 0.73.1. madvr on 0.92.17. This stuttering is very similar to what another user mentioned earlier which I quoted above.
Edit: If I use FSE my stuttering issue is solved too. Thanks everyone who took the time to reply to my issues.
Warner306
12th November 2018, 16:31
Does the problem go away when using lower values of NGU or something like Jinc or super-xbr?
Grahlwur
12th November 2018, 20:30
Is it possible to select which angle/eye is viewed when watching a 3D-bluray in 2D? It seems to default to the "first" eye, but I can't find a way to change to the "second" eye.
I tried playing around a bit in madVR settings under devices -> <device> -> properties and rendering -> stereo 3d, but I can't seem to find a way to accomplish this.
No matter which settings I use in madVR, LAV Video Decoder says "Active Decover: msdk mvc", which makes me think it's possible to write a function to for example enable the "swap left / right eye"-checkbox for "3D format: none" to accomplish this?
When watching 3D encoded as SBS, I can select eye pretty easily by using Pan & Scan in MPC-HC to zoom in/crop to see only the eye I want. However, this does not work with a proper 3D-bluray since the Pan & Scan is happening before madVR does its magic. Meaning I just end up with SBS with zoomed in picture on both sides.
I realise this is a kinda odd question. What I'm trying to accomplish in the end is to analyse fullscreen screenshots of both left and right eye from 3D bluray both with themselves and the same frame from 2D bluray.
1) Is it already possible to select eye in madVR and I just haven't figured out how to do it?
If no:
2) Is it a feature that can be added without too much hassle?
3) Anyone happen to know if this is possible somehow in MPC-HC itself with LAV and madVR?
Also, thanks for an awesome renderer! :)
Regards
wnholt01
13th November 2018, 03:40
Just got my asus strix 2080 ti and I am experiencing the same stuttering issues. Games are working fine. Looking at gpu clocks the gpu is not stressed at all while playing madvr. Power is set to adaptive. I have even tried default madvr settings with no image upscaling but still the same issue. Latest drivers. Any suggestions please?
Everything was fine with the 1080 that I swapped out.
Edit: No issues with evr.
Yes, I am using 2080 and get stuttering also even through CPU/GPU utilization is low and rendering time is low. I was getting no stuttering with 1060. Only thing that prevents stuttering for me is enabling full screen exclusive mode.
austinminton
13th November 2018, 10:32
Does the problem go away when using lower values of NGU or something like Jinc or super-xbr?
No, I get this problem on my 2080 ti even if I match the resolution (for no upscaling). The rendering times are very very low but the problem persists.
The only way to avoid stuttering is to enable FSE.
This was not a problem on my 1080 which was the exact same vendor and model (asus strix).
Betroz
13th November 2018, 12:36
The only way to avoid stuttering is to enable FSE.
This was not a problem on my 1080 which was the exact same vendor and model (asus strix).
It could be that drivers for the RTX cards are still buggy.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.