View Full Version : madVR - high quality video renderer (GPU assisted)
ryrynz
23rd March 2019, 02:41
Jonny, check your GPU usage and madvr queues. Post your OSD?
JonnyRedHed
23rd March 2019, 03:20
Jonny, check your GPU usage and madvr queues. Post your OSD?
Thanks for the prompt reply,
Screenshot fullscreen zoomplayer madvr
http://i63.tinypic.com/20uri1w.png
GPU usage varies but never over 90%. With this 1080p video file no more than 40-50%. Some SD content can reach 85% usage, as can 720p.
ryrynz
23rd March 2019, 03:51
Your present queue is awfully low. Either your card is having issues performance wise or something is interfering with it. Focus Assist enabled?
huhn
23rd March 2019, 05:13
this screenshoot is nearly for sure not from playback but while playback is paused making it not really useful.
make one while playback isn't stopped and best after or when he problem happens.
ryrynz
23rd March 2019, 07:15
True completely forgot about that.. It would be 1-8/8 if it wasn't paused.
Jonny, what's your CPU utilization like? Does the OSD show anything different when these lags happen?
JonnyRedHed
23rd March 2019, 11:36
True completely forgot about that.. It would be 1-8/8 if it wasn't paused.
Jonny, what's your CPU utilization like? Does the OSD show anything different when these lags happen?
Yes your correct screenshot after pause, I apologise.
Whats the best way to present screen grabs to you here, like below or some other way so they display here without you needing to click off-site.
x264 1080p file - playing for 10 secs and then for 5 minutes
'automatically detect hard coded black bars' disabled
http://i63.tinypic.com/651t3k.png
http://i68.tinypic.com/34in7mf.png
screen grab of afterburner and openhardwaremonitor stats
red ring indicates period of stable playback,
'automatically detect hard coded black bars' disabled.
http://i63.tinypic.com/2egb8np.png
x265 file 1080p - same fullscreen playing
'automatically detect hard coded black bars' disabled.
http://i65.tinypic.com/28849i9.png
stats
http://i67.tinypic.com/281rc4y.png
x264 1080p fullscreen playback with 'automatically detect hard coded black bars' enabled
stutter/glitch - highlighted in red
http://i67.tinypic.com/2l8ufx1.png
Madvr OSD does not show anything odd at moment of video freeze and catch up.
This has been happening across a few or more madvr releases and NV drivers and Zoomplayer versions. Maybe 6 months or so.
Computer:
Win7x64
i5 2500k @4.5Ghz
16Gb 2133Mhz Ram
GPU MSI GTX 670 OC (can boost to stable 1306 Mhz)
TV 50inch LG Plasma via HDMI (TV in PC mode)
actarusfleed
23rd March 2019, 11:45
Hi guys,
look at this picture ...
http://audioquality.it/cloud/forum/comprate.jpg
On my htpc I've installed MPC HC and Kodi DSPlayer + MadVR lastest official version + latest LAV filters.
My GPU is an NVIDIA 2080.
Like you can see if I reproduce a file with MPC HC appears "composition rate 60Hz".
It not happens in DSplayer.
Why? is it normal?
If I deactivate FSE the "composition rate" voice disappear.
Another question:
Why I see two different scaling voices?
> chroma > NGU sharp (high)
> chroma > Bicubic60 AR
Why two settings for the same chroma upscaling function?
Thank you so much
ryrynz
23rd March 2019, 11:50
That's interesting.. does anyone else experience these GPU load spikes when this is enabled?
Jonny, can you back up and test with default settings (use the default madvr settings batch file) + black bar detection enabled to see if this still occurs?
This happens with all files, yes? I'm not aware of any issues with Zoomplayer but can you quickly test with MPC-HC or BE to confirm it's not related to Zoomplayer in any way? That is is defaults don't fix the issue.
JonnyRedHed
23rd March 2019, 12:07
That's interesting.. does anyone else experience these GPU load spikes when this is enabled?
Jonny, can you back up and test with default settings (use the default madvr settings batch file) + black bar detection enabled to see if this still occurs?
This happens with all files, yes? I'm not aware of any issues with Zoomplayer but can you quickly test with MPC-HC or BE to confirm it's not related to Zoomplayer in any way? That is is defaults don't fix the issue.
I have already backed up my old madvr settings bin (with profiles) and reset a few times over the last few days for a clean start whilst I tried to get to the bottom of the stutters. Using at present no profiles on size fits all whilst testing. Having lived with it for ages now I just ran with 'automatically detect hard coded black bars' disabled up until a few days ago.
All content and file types I have yes. x264, x265, MP4, MKV, SD-1080p.
Rolled back a few versions (4 or 5) of madvr, ZP max (beta and recent stables), lav filters (3 versions), but stuttering glitch is still present. Back now with latest madvr, zp beta, lav filters.
Only wanting to use it for some old SD content to clean up dirty edges on 4:3 content, I turned it back on, but soon found I needed to track down what was going on.
It took a few hours of working up from defaults to isolate the stutter and catch up glitch, until enabling 'automatically detect hard coded black bars'. At first I thought it was one of the sub settings once enabled but soon discovered it wasn't and just checking 'automatically detect hard coded black bars' caused the stutters, with any content type.
With madvr settings reset, and with just 'automatically detect hard coded black bars' enabled, it does still act exactly the same way. Less gpu usage with defaults, but the stutter/catchup/glitch is there exactly as you see here: http://i67.tinypic.com/2l8ufx1.png
I've no other players installed, and have only used ZP for like ever. I'd have to check up on how to use MPC-HC with madvr, and other players, and am not sure what BE is, is this a player.
Klaus1189
23rd March 2019, 12:20
not sure what BE is, is this a player.
Media Player Classic - BE, MPC-BE, it is my favourite player.
https://forum.doom9.org/showthread.php?t=165890
Download latest nightlies here: https://yadi.sk/d/hlf1lfC8mKU58
These are rocksolid.
actarusfleed
23rd March 2019, 12:56
Media Player Classic - BE, MPC-BE, it is my favourite player.
https://forum.doom9.org/showthread.php?t=165890
Download latest nightlies here: https://yadi.sk/d/hlf1lfC8mKU58
These are rocksolid.
Hi Klaus, are you answering to me?
If yes, I already use BE version...
I've tested BE and HC classic version and both reports "composition rate" line ...
Please someone tells me if it's normal to have it with those players ...?
Klaus1189
23rd March 2019, 13:04
I added a quote, so it's clear.
I use MPC-BE, as you already know and I always have composition rate line in OSD stats.
actarusfleed
23rd March 2019, 13:17
I added a quote, so it's clear.
I use MPC-BE, as you already know and I always have composition rate line in OSD stats.
Ok thank you Klaus.
Why composition rate is = 60hz .... and the film content reproduced is 23,97Hz?
Is it normal 60Hz?
My graphic card use a 2160p23,97 hz output resolution.
Klaus1189
23rd March 2019, 13:20
No, not normal, I think it is a bug in Nvidia driver if I remember correctly. Since I don‘t have a Nvidia card, I cannot test but I am collecting information in a dedicated thread:
https://forum.doom9.org/showthread.php?t=176013
Try another version of driver, which one are you using now?
huhn
23rd March 2019, 13:29
that's a composition rate mismatch a classic issue on windows 7 and win 10 has this too with some versions and driver combinations.
you didn't have by any chance a second screen connected?
what so ever a simple work around is windows 7 overlay this mode ignores the composition rate. kodi may run without FSE optimization so the classic more real FSE is used under win 10.
for overlay to work properly you need to disable FSE.
you have 2 lines of chroma because doing NGU on 3 instead of 1 channel would meld most GPUs.
BTW your presentation queue is different between these screens.
tp4tissue
23rd March 2019, 14:55
When the seek bar or menu is visible, the present queue changes numbers.
tp4tissue
23rd March 2019, 14:58
@ actarusfleed
Try a different driver version.
Make sure to run the cleaner in safemode.
test, unplug second monitor
why do you have ngu chroma VH instead of luma VH ?
tp4tissue
23rd March 2019, 18:33
Sooooo.. is Envy going to be a beefed up Android box of sorts ?
nevcairiel
23rd March 2019, 18:43
Sooooo.. is Envy going to be a beefed up Android box of sorts ?
Envy is off-topic here, and there is no new information.
thighhighs
23rd March 2019, 19:00
Is it normal 60Hz?
My graphic card use a 2160p23,97 hz output resolution. Same issue with PotPlayer. Looks like movies playback don't affected at all. Display modes switcher work fine, no dropped frames or glitches and something else. At least I didn't notice anything bad during movies playback. So i think FSE still usable if is needed.
actarusfleed
24th March 2019, 01:12
Try another version of driver, which one are you using now?
I'm using version 419.35. What version you suggest me to test? and where I can find old versions?
you didn't have by any chance a second screen connected?
No, I've only one projector hooked up. no other display.
what so ever a simple work around is windows 7 overlay this mode ignores the composition rate. kodi may run without FSE optimization so the classic more real FSE is used under win 10.
for overlay to work properly you need to disable FSE.
Yes, I disabled FSE and windowed mode works well. Composition rate line vanish.
Try a different driver version.
What version you suggest?
why do you have ngu chroma VH instead of luma VH ?
Sorry but I can undestrand you. Can you explain me better ? thank you
ryrynz
24th March 2019, 06:35
I'd have to check up on how to use MPC-HC with madvr, and other players, and am not sure what BE is, is this a player.
Not much to pick up on, just enable madVR in the renderer section and press play. If it is completely random as you say and MPC does it as well I think the next best step would be to place madVR into debugging mode (activate debug mode.bat) and sending the resulting desktop file to madshi. Note the time these spikes occur (use a stopwatch) so he can find the data at the right time in the rather large file that will result.
What version you suggest?
385.28 is legendary.
Sorry but I can understand you. Can you explain me better ? thank you
You have chroma set to NGU Sharp Very High, this is generally not recommended, especially when it's at the expense of Luma.
Instead you should change down (if required for extra performance) to enable NGU Sharp Very High for luma instead rather than have it set on the High setting you currently have enabled.
Klaus1189
24th March 2019, 11:26
I'm using version 419.35. What version you suggest me to test? and where I can find old versions?
385.28 is legendary.
Agree, but he uses a RTX 2080.
My GPU is an NVIDIA 2080.
But that is the issue here, you need at least: 411.63 GRD 2018-09-19
See here for details:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)
If you want to use HDR passthrough you will be out of luck for now, because newer driver versions output bogus metadata, which will last some time for Nvidia to fix.
Klaus1189
24th March 2019, 11:44
Type in google the driver version you want/need, you'll find the download page from Nvidia.
But even I started the dedicated thread I personally can't recommend a driver version for a RTX 2080, every newer driver version has any issues. I don't have a Nvidia anymore for this reason and I will only get one when Nvidia focuses more on HTPC users.
But to shorten things a bit, what do you want:
1.) Do you need HDR passthrough?
2.) Do you need custom refresh rates, especially for 23p mode
3.) What OS do you use? If Win10, what version like 1809?
mzso
24th March 2019, 12:42
Hello!
I ran into an issue with madVR. Some UT-Video formats (ULH4, UMRG, probably more) won't play when using the offical codecs when madVR is chosen as a renderer . I only get a blackscreen and either no playback (when there's an audio stream) or blackscreen during playback (when there's no audio stream). With all other renderers there's no problem.
Not sure what happens, the splitter is LAV.
If I use LAV decoder the formats that are supported by ffmpeg play normally. However that are not display only a black screen so so there's no way to play them with madVR.
tp4tissue
24th March 2019, 15:05
Hello!
I ran into an issue with madVR. Some UT-Video formats (ULH4, UMRG, probably more) won't play when using the origi madVR is chosen as a renderer . .
Try full screen
Sometimes I had this weird bug on some videos, it will black screen on downscaling, but it works fine with upscaling.
actarusfleed
24th March 2019, 17:25
you have 2 lines of chroma because doing NGU on 3 instead of 1 channel would meld most GPUs.
Please can you explain me better this?
Why the second line is not always NGU? Now it's Bicubic60 AR ....
There is a waay to set better second line? or it's something that Madvr choose automatically?
BTW your presentation queue is different between these screens.
I don't know why it is different .... It's a problem?
You have chroma set to NGU Sharp Very High, this is generally not recommended, especially when it's at the expense of Luma.
Instead you should change down (if required for extra performance) to enable NGU Sharp Very High for luma instead rather than have it set on the High setting you currently have enabled.
Ok now it's much clear thank you ... so Luma is much important than chroma .... the luma settings are those below?
https://audioquality.it/cloud/forum/luma.jpg
I was thinking that those settings regards only Full HD content like old full hd blu rays ... I was thinking that luma component of a UHD blu ray don't need to be scaled if the htpc outs @ 2160p.
My main use of HTPC is to play UHD files (80%) and some other Full HD Blu ray (20%).
So luma scaling is important also with UHD files?
Can you suggest me some luma settings to start?
Agree, but he uses a RTX 2080.
But that is the issue here, you need at least: 411.63 GRD 2018-09-19
See here for details:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)
If you want to use HDR passthrough you will be out of luck for now, because newer driver versions output bogus metadata, which will last some time for Nvidia to fix.
No, I don't need to send metadata. I tone map HDR using pixel shaders in Madvr. My htpc use Win 10 (I'm not able to find what version is ...)
So what is the best driver for me?
Klaus1189
24th March 2019, 17:39
No, I don't need to send metadata. I tone map HDR using pixel shaders in Madvr. My htpc use Win 10 (I'm not able to find what version is ...)
So what is the best driver for me?
Good, there is no driver for RTX 2080 which does it with correct metadata at the moment, Nvidia has to deliver one in future, hope dies last.
Since I don't own a Nvidia and cannot test, just use the newest and report back what feature doesn't work for you.
For example if you want to use custom refresh rates and you are on Win10 1809, the custom refresh artes are not stored after a reboot. But you can use CRU for it. Some use it in this forum, but not me, because I don't need custom refresh rates.
Every refresh rate (out of the box) is at about 7 ... 8 hours till one frame gets dropped/repeated.
Run "winver" to check your OS version
I think the 60Hz composition rate is also different on FSE vs. windowed. Can you test this?
tp4tissue
24th March 2019, 18:03
Hey guyz, why doesn't the custom mode tab show up on my laptop ? It's just not there , missing. 92.17
actarusfleed
24th March 2019, 19:59
Since I don't own a Nvidia and cannot test, just use the newest and report back what feature doesn't work for you.
The problem described in my previous post (FSE > Composition rate = 60hz) is with the newest Nvidia driver (419.35).
For example if you want to use custom refresh rates and you are on Win10 1809, the custom refresh artes are not stored after a reboot.
Custom resolutions are not priority for me now ... but in the future my intent will be to fix also this problem ....
So to have also custom resolutions , with an RTX2080, what combination of Win10 version + Nvidia drivers Do I've to use?
But you can use CRU for it
What is "CRU" ?
Run "winver" to check your OS version
Done, thanks. My actual version is 1809 build SO 17763.379
I think the 60Hz composition rate is also different on FSE vs. windowed. Can you test this?
Yes reported in my previous post ... In windowed mode the composition rate is perfect related to the content reproduced.
In my previous htpc (Win10 + RTX2070) windowed mode was unusable... some glitches during playback.... so I was forced to use FSE. Someone told me that RTX series had this bug.
Now , in this new htpc with RTX 2080, I've no problem using windowed mode.
mzso
24th March 2019, 20:02
Try full screen
Sometimes I had this weird bug on some videos, it will black screen on downscaling, but it works fine with upscaling.
Makes no difference. The UT video dev claims that the error is on madVR's side that "madVR's behavior is strange".
Klaus1189
24th March 2019, 20:40
The problem described in my previous post (FSE > Composition rate = 60hz) is with the newest Nvidia driver (419.35).
Custom resolutions are not priority for me now ... but in the future my intent will be to fix also this problem ....
So to have also custom resolutions , with an RTX2080, what combination of Win10 version + Nvidia drivers Do I've to use?
Please take a look again at my thread:
https://forum.doom9.org/showthread.php?t=176013
slect the seconds last one and try what happens. If it has also bugs, try the third, then the fourth, ...
Just copy and paste version in google and you'll find the Nvidia download page.
What is "CRU" ?
See here
https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU
But I don't use it as I already mentioned in one of my previous posts, so can't help you with it, but for sure others can help.
ryrynz
24th March 2019, 21:07
So luma scaling is important also with UHD files?
Can you suggest me some luma settings to start?
Because you don't have any profiles set up you're only upscaling video that needs to be upscaled. UHD titles will not upscale as they meet the native display resolution of your panel.
I recommend starting with Asmodian's max quality config here (http://www.mediafire.com/file/aq8bevrirokiry2/madVR_MaxQuality.zip/file).
JonnyRedHed
24th March 2019, 21:21
Not much to pick up on, just enable madVR in the renderer section and press play. If it is completely random as you say and MPC does it as well I think the next best step would be to place madVR into debugging mode (activate debug mode.bat) and sending the resulting desktop file to madshi. Note the time these spikes occur (use a stopwatch) so he can find the data at the right time in the rather large file that will result.
Yes, can confirm the stutter glitch occurs exactly the same in MPC-BE with the renderer set to madvr. With 'automatically detect hard coded black bars' enabled.
ryrynz
24th March 2019, 21:23
Maybe given the age and performance of your card you're the first one to notice an issue with this setting.. create the log and pass it to madshi over at http://bugs.madshi.net
actarusfleed
24th March 2019, 23:16
Because you don't have any profiles set up you're only upscaling video that needs to be upscaled. UHD titles will not upscale as they meet the native display resolution of your panel.
I recommend starting with Asmodian's max quality config here (http://www.mediafire.com/file/aq8bevrirokiry2/madVR_MaxQuality.zip/file).Ok, so this section needs to be properly setted for full HD content.
UHD files do not need those functions.
So I was right.
Please how to use the file you sent me?
ryrynz
24th March 2019, 23:42
Copy it into your madvr folder. Overwrite your current settings file. Basic stuff.
huhn
25th March 2019, 00:10
Hello!
I ran into an issue with madVR. Some UT-Video formats (ULH4, UMRG, probably more) won't play when using the origi madVR is chosen as a renderer . I only get a blackscreen and either no playback (when there's an audio stream) or blackscreen during playback (when there's no audio stream). With all other renderers there's no problem.
Not sure what happens, the splitter is LAV.
If I use LAV decoder the formats that are supported by ffmpeg play normally. However that are not display only a black screen so so there's no way to play them with madVR.
can you provide a sample and what decoder is used?
tp4tissue
25th March 2019, 01:24
So, dat Samsung AI upscaling technology..
Here's the hurdle, They've got money, and all the resource in the world.
At some point, advancing this technology requires raw compute resources, to train the algorithms, to be content aware, and to continuously UPDATE.
I think, there's an opportunity here, for Madshi to Leverage ALL of Madvr enthusiast's collective GPU power in such training.
Otherwise, Samsung will just beat us over the head with MONEY..
Perhaps a distributive compute process for training that everyone can download, and help run, like folding @ home?
nussman
25th March 2019, 02:23
Can you stop posting nonsense here?
Oguignant
25th March 2019, 03:29
For madVR v0.92.17 or later:
Max Quality settings.bin
Low Power settings.bin
https://forum.doom9.org/showthread.php?p=1709584
why no more Heater settings?
Asmodian
25th March 2019, 07:46
Feel free to post in that thread, you will get answers there too. :p
Once I got a 2080 Ti, and switched to NGU AA for my default (not related), the heater and "max" settings became the same thing, and so max is a bit more accurate of a name now.
NGU AA does not have direct 4x so I have to use double again. Also, the 2080 Ti still has plenty of room left for RCA and/or sharpening, if needed, even with 2x NGU very high twice for 720p30 to 4K. :)
ashlar42
25th March 2019, 14:54
Can you stop posting nonsense here?What nonsense are you referring to? Are you talking about the idea of distributed picture analysis through neural networks?
I'm totally ignorant about the tech hurdles to overcome but the idea, overall, doesn't seem to me so "nonsense". At the very least it's worth discussing, I guess.
tp4tissue
25th March 2019, 15:17
Guys, I got an old tv that has its own sharpening chip which can't be disabled. What it's doing is creating checker boxes from what looks like -Grain- ?
Are the patches output by Madtpg completely solid without grain (dithered patterns)? It might just be this tv which is itself crazy, but wanted to confirm with y'all.
The problem this is causing is up and down measurements near the frequencies where their sharpening algorithm is trying to detect edges.
So when it distorts a patch with sharpening patterns, it's measured incorrectly as darker.
mzso
25th March 2019, 15:55
can you provide a sample and what decoder is used?
If you insist. Though you can make some of your own if you want with the official codec (https://github.com/umezawatakeshi/utvideo/releases):
https://mega.nz/#F!54QDmCQQ!-2Txj1DmyVR7faTUE6j0NA
(These original files created by the recorder software, so they also have the audio stream.)
el Filou
25th March 2019, 18:30
Those two files work on my system ("mission 08" "mission 22") with LAV 0.74.1 outputting respectively RGB32 and YV24 to madVR.
VBB
25th March 2019, 20:08
Are the patches output by Madtpg completely solid without grain (dithered patterns)?
Completely solid, of course. Old plasma?
Oguignant
25th March 2019, 21:29
Feel free to post in that thread, you will get answers there too. :p
Once I got a 2080 Ti, and switched to NGU AA for my default (not related), the heater and "max" settings became the same thing, and so max is a bit more accurate of a name now.
NGU AA does not have direct 4x so I have to use double again. Also, the 2080 Ti still has plenty of room left for RCA and/or sharpening, if needed, even with 2x NGU very high twice for 720p30 to 4K. :)
Hi Asmodian,
I was using old Heater settings with NGU Sharp but now, I'm using your Max settings with my geforce 1080ti and the result is very, very good.
I use it for 2160p23, 1080p23, 720p23 and Streaming. I do not have dropped frames and the render time is 14 or 19 ms approx.
mzso
25th March 2019, 22:04
Those two files work on my system ("mission 08" "mission 22") with LAV 0.74.1 outputting respectively RGB32 and YV24 to madVR.
I kind of borked the comment, but the problem is with the official codecs, not LAV video.
The RGB (T2) one working is a tad suspicious since ffmpeg/LAV doesn't support it.
nevcairiel
25th March 2019, 22:06
I kind of borked the comment, but the problem is with the official codecs, not LAV video.
The RGB (T2) one working is a tad suspicious since ffmpeg/LAV doesn't support it.
As far as I can tell, FFmpeg/LAV supports those "T2" ones fine, only "Pro" formats are not supported (10-bit).
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.