View Full Version : madVR - high quality video renderer (GPU assisted)
XMonarchY
31st May 2017, 00:07
I've honestly read more people that say it works fine for them then those that complain - which was mostly you. Should probably not project your issues onto everyone else. Creators Update runs just fine for me with madVR. :)
You should just disable game mode and the game bar if you don't want them and think they intefer - if your alternative is to not use CU anyway, you also don't lose out on anything you wouldn't have anyway (not to mention that game mode is largely irrelevant anyway).
Come over and we test it together:
1. Stock Win10 x64 RS1 + run Windows Update + NO TWEAKS + install latest NVidia drivers + install latest MPC-HC x86, LAV, madVR, ReClock = no issues with playback
2. Stock Win10 x64 RS2 + the same as above = severe frame-droppping with exactly the same settings.
I did this comparison several times and you're wrong to say I am the only one. Windows 10 RS2 does bring significant changes to the way it treats video drivers, refresh rates, adds overlays and "Optimizations" to FSE. There is no way to get rid of it. Its integrated into the OS, most likely hard-coded into DWM.EXE. Just because you aren't getting the same problem does not mean it is not there. As I mentioned, I do not have this RS2 frame-dropping problem on all of my displays, just one of them, and the other 2 work the same way with either edition. It just happens that the one display that has issues with RS2 is my TV!
nsnhd
31st May 2017, 03:16
Using newest madvr 0.91.10 causing Potplayer to close really slow and start really slow, I can't click on movie instantly after closing potplayer, I can see potplayer going from 100+ mb of ram to 35mb and then close which takes about 4-5 sec, within this time it doesn't open another movie or the same movie cause I limited it to 1 instance of player. without using Madvr , just any other renderer , potplayer closes fast and opens fast. 0.91.9 worked properly without an issue.
EDIT : Nvm , it still happens with 0.91.9 , I figure it's the new update, he changed something for people who have crashes , might kind of timeout which doesn't close it instant. with version 1.7.1916 it works like it should. Still for some unkonwn reason, potplayer opens when the internet is disabled ! , can anyone figure out why !? it opens the movie instant without internet ( network adapter disabled ) compare to with internet takes like 2-3 sec saying it's opening ...
On my i5 intel iGPU pc, among Potplayer and Mpc-HC/BE, Potplayer gives me the best madVR result by playing 4K/HDR clips, no dropped frames, no glitches, lowest rendering ms and full filled queues. The same madVR setting on Mpc-HC/BE drops lots of frames, means unwatchable. Maybe Potplayer internal decoder is better than the others, I'm not sure.
ryrynz
31st May 2017, 03:37
Madshi, with D3D11 I still get some frames presented from earlier in the video when I jump forward on my HD4000.
To playback what sort of source material? 72Hz is good for 24fps material. 71.928Hz is good for 23.976fps material.
Depending on your screen, you might be better off implementing a custom resolution for 23.976Hz, because the screen might already be working "behind scenes" to multiply it in order to reduce flicker.
Mostly for 23.976 fps material, my monitor can't handle 23.976hz, and madvr acts weird with 71.928hz. 72hz is ok.
SweetLow
31st May 2017, 10:33
Which is the better alternative: 60hz with smooth motion or custom refresh rate 72hz with reclock?
Better is the third alternative - 72 with smooth motion and reclock, of course.
why should you use reclock AND smoothmotion at the same time?
it should work together but still why touch the audio or video if it is clearly not necessary.
ashlar42
31st May 2017, 11:31
Mostly for 23.976 fps material, my monitor can't handle 23.976hz, and madvr acts weird with 71.928hz. 72hz is ok.Use SmoothMotion at 72Hz, then. No Reclock needed (if you need WASAPI you can use Sanear... or Reclock I guess, but no x64 in that case).
Use SmoothMotion at 72Hz, then. No Reclock needed (if you need WASAPI you can use Sanear... or Reclock I guess, but no x64 in that case).
I made 71.928hz custom refresh rate again, to see how things will behave, personally I don't like the blur that smooth motion adds.
The closest to 71.928 hz I could get was 71.931 hz...anyway looks ok for now.
https://9-t.imgbox.com/dYdXQxgc.jpg (http://imgbox.com/dYdXQxgc)
Returning to the issue of oversaturated colors of some videos on wide-gamut displays:
For the sample video, I made the following test: in the video player that was using madVR, switched to interpreting video as full range (via madVR shortcut) and made a screenshot in PNG. Then opened it in Photoshop and analyzed the values in the areas of these artifacts.
Red areas were indeed oversaturated in R channel (highest R was 255), but G and B were less than 252 (and even less that 235 in green area), although R values were 0 (or close to zero) there. So, most of the visible problems are in areas with R not in range 16-235 (or even 1-254).
Here is the captured frame:
Photoshop_-_Color_Lookup_Table.mkv_-_00000.png (https://s19.postimg.org/k7snvtao1/Photoshop_-_Color_Lookup_Table.mkv_-_00000.png?dl=1)
it could be clipped.
there are for sure mathematical ways to ignore 0-16 and 236-255 or they could be mapped to 16/235.
of cause i have no clue how much work that is.
As for the range of the original video - I couldn't understand your answer on whether it's limited or not.
should be limited(a normal video). it is not worth to check it with a histogram and the issue has nothing to do with the range anyway.
It seems that either the video is badly encoded, or it is wrongfully interpreted.
Anyway, does it really has any sense to have values 0 and 255 pass to 3D LUT then?
oddball
1st June 2017, 04:16
Madshi can you please explain why the following does not work '1080p23, 2160p23' If I use that when the display is set to 2160, it cuts off a 1080p video and only shows half of the video on the display to the right and the left half is black. If I set the display to 1080 it shrinks the 2160p video to the top left corner (quarter) of the display and the rest of the display is black. Is there no way to fix this?
It seems that either the video is badly encoded, or it is wrongfully interpreted.
Anyway, does it really has any sense to have values 0 and 255 pass to 3D LUT then?
the video is supposed to be limited range that's all i can say.
removing BTB/WTW before it get's into the 3D LUT cost performance and WTW can be used and is not that rare in sources.
Madshi can you please explain why the following does not work '1080p23, 2160p23' If I use that when the display is set to 2160, it cuts off a 1080p video and only shows half of the video on the display to the right and the left half is black. If I set the display to 1080 it shrinks the 2160p video to the top left corner (quarter) of the display and the rest of the display is black. Is there no way to fix this?
try to disable the windows scaling by setting DPI scaling to 100%.
i don't know why you should use 1080p and 2160p at the same time. resolution changing got quite messy with the newer windows version but not everyone is affected as always.
the video is supposed to be limited range that's all i can say.
removing BTB/WTW before it get's into the 3D LUT cost performance and WTW can be used and is not that rare in sources.
Yes, it should be limited range. But somehow this video is decoded to values of R that are out of scope for limited range. Although it doesn't look like full range video - the level of white color stops at 235.
There are lots of video that show some artifacts in saturated areas that become seen when using 3D LUT.
My question is - does it make sense to consider values 0 and 255 special that shouldn't be mapped by it? I know that they are used for timing information in video standard, but what is the use of having them in the output of 3D LUT?
Should there be any video timing information in madVR output?
Yes, it should be limited range. But somehow this video is decoded to values of R that are out of scope for limited range. Although it doesn't look like full range video - the level of white color stops at 235.
There are lots of video that show some artifacts in saturated areas that become seen when using 3D LUT.
could be anything from a mastering issue to encoding artifacts the list is long.
nothing wrong with decoding anything to full range even if the video is limited range. this is totally ok the issue is the 3D LUT handle nothing else.
My question is - does it make sense to consider values 0 and 255 special that shouldn't be mapped by it? I know that they are used for timing information in video standard, but what is the use of having them in the output of 3D LUT?
the video timing part is even bigger. i'm not sure if they are present in this part there. for 1080p the send "image" has a size of about 2200x1125 with DMT timing.
a 3D LUT shouldn't be mapping it like this but that's really all i have to say. i brought this up to fhoech and i'm not going to force it on him. this is free software done by people in there free time there is a limited.
so that's it nothing more for me to do this topic is over for me.
Should there be any video timing information in madVR output?
i have not written a video renderer but i'm pretty sure there are no timing information that are of any important or most likely any timing information in the image what so ever.
madVR is not the reason for the issue.
nothing wrong with decoding anything to full range even if the video is limited range. this is totally ok the issue is the 3D LUT handle nothing else.
the video timing part is even bigger. i'm not sure if they are present in this part there. for 1080p the send "image" has a size of about 2200x1125 with DMT timing.
a 3D LUT shouldn't be mapping it like this but that's really all i have to say. i brought this up to fhoech and i'm not going to force it on him. this is free software done by people in there free time there is a limited.
so that's it nothing more for me to do this topic is over for me.
The main issue I think is that for some reason 3D LUT file is created so that 0 maps strictly to 0 and 255 - to 255.
But there is no reason to do this, because these special values are not used by the application that is using the LUT file (I am talking about madVR).
oddball
2nd June 2017, 03:16
Is anyone getting over saturated colors in full screen exclusive mode when using DX11? If I disable DX11 the colors are the same with or without FSE.
ryrynz
2nd June 2017, 05:19
What's your graphics card? Should really flesh out your post.
oddball
2nd June 2017, 15:14
What's your graphics card? Should really flesh out your post.
AMD RX 480 with latest drivers (same with older driver though). I managed to fix it I think by setting the Windows color profile to wide gamut.
oddball
2nd June 2017, 15:19
the video is supposed to be limited range that's all i can say.
removing BTB/WTW before it get's into the 3D LUT cost performance and WTW can be used and is not that rare in sources.
try to disable the windows scaling by setting DPI scaling to 100%.
i don't know why you should use 1080p and 2160p at the same time. resolution changing got quite messy with the newer windows version but not everyone is affected as always.
Yeah I already tried that thinking it might be DPi but it made no difference. The reason I wanted switching to 1080p for 1080p content was to lessen the load on the GPU when not needed.
HillieSan
2nd June 2017, 19:29
Madshi can you please explain why the following does not work '1080p23, 2160p23' If I use that when the display is set to 2160, it cuts off a 1080p video and only shows half of the video on the display to the right and the left half is black. If I set the display to 1080 it shrinks the 2160p video to the top left corner (quarter) of the display and the rest of the display is black. Is there no way to fix this?
What happens if you take "1080p32" off the list? I had an issue when both "1080p32 2160p23" are in the list. It was some time ago and I don't remember what the issue was. Anyway, it solved the issue with 1080p for me. I use an AMD RX 480.
ashlar42
3rd June 2017, 11:44
The closest to 71.928 hz I could get was 71.931 hz...anyway looks ok for now.
https://9-t.imgbox.com/dYdXQxgc.jpg (http://imgbox.com/dYdXQxgc)Check here to know what is the refresh rate you want to aim for: https://forum.doom9.org/showthread.php?t=173571
Check here to know what is the refresh rate you want to aim for: https://forum.doom9.org/showthread.php?t=173571
That's a good guide, but it will be good to use examples of 23.976 hz and multiple refresh rates not 50 hz, also I can't use cru cause it doesn't detect my custom refresh rate, I'm on displayport.
Also using pixel clock calculator it doesn't show the exact timings for 71.928 hz...
I used that guide and I did not use CRU. AMD custom refresh rates works perfectly. I also used the guide for setting up my 59.940, 75 AND 71.928 rates... With current temperatures all 3 at "no drops/repeats expected"... So the guide is very useful even if you don't follow it exactly.
QB
why here in this thread and not in the guides thread?
Vincent Vega
3rd June 2017, 20:10
guys sorry for simplest question, others asked before but i cant find answer:
Is there a way to turn off the "Exclusive/Windowed" message at the top left when switching between windowed/fullscreen?
(I do want fullscreen to be in exclusive mode, just dont want to see the message everytime)
Damien147
3rd June 2017, 20:39
Yes,close your eyes.:p
Vincent Vega
3rd June 2017, 21:03
aw come on ..
Damien147
3rd June 2017, 21:30
I don't find it a big deal because it stays there for a second and also informs you what's going on.
Vincent Vega
4th June 2017, 04:57
another question:
i cant use mpc-hc "save image" with madvr (dxva2 copy-back decoding + dxva2 scaling).
the output of save image is discolored mostly white picture with barely visible silhouettes, and the size of mpc-hc window, not the frame size.
will it be fixed? in the meantime, is there a workaround?
ryrynz
4th June 2017, 05:06
(I do want fullscreen to be in exclusive mode, just dont want to see the message everytime)
You're not the first to ask. I think madshi will add an option to prevent these in a future version. For now.. Close your eyes.
sneaker_ger
4th June 2017, 09:27
in the meantime, is there a workaround?
Try without DXVA2 scaling?
What OS, GPU and driver are you using?
fijam
4th June 2017, 14:08
Does madVR receive HDR metadata included in the MKV container (MaxCLL, MaxFALL, MasteringMetadata elements)?
I guess this is also a question for Nevcairiel, if LAVFilters can currently parse that from MKV files and pass it on.
This could be useful for 10b h264 streams that want to retain HDR metadata (the transfer function tag can be set at the bitstream level, but SMPTE2086 data cannot as far as I can tell).
sneaker_ger
4th June 2017, 14:12
LAV + madVR already support MKV HDR metadata. Anything missing?
but SMPTE2086 data cannot as far as I can tell).
Wasn't that added to the specs as well? From what I've seen they've basically copied everything over from HEVC.
/edit:
Ok, I can't find it in H.264 2016/10. 2017/04 exists but not yet public. Maybe it's added there?
fijam
4th June 2017, 15:03
LAV + madVR already support MKV HDR metadata. Anything missing?
Thanks for the reply. How can I tell it's working? I've added mkv smpte metadata with mkvmerge to a test file, and it shows 'HDR, unknown properties' on playback with madvr. Same if nothing is added to the container.
https://ptpimg.me/5jr61g.pnghttps://ptpimg.me/8agk6v.png
sneaker_ger
4th June 2017, 15:22
I cannot reproduce. Latest LAV, madvr? Chain is LAV Splitter -> LAV Video -> madvr? Sample?
fijam
4th June 2017, 15:30
I cannot reproduce. Latest LAV, madvr? Chain is LAV Splitter -> LAV Video -> madvr? Sample?
Apparently I had the older version installed alongside which had the default file associations. Works now, thanks for help.
Xello
4th June 2017, 16:09
Are there any known fixes for this issue? https://forum.redfox.bz/threads/windows-10-creators-update-messed-up-reclock.72475/
Basically the creator's update has resulted in the loss of normal playback using madvr with reclock, with repeated/dropped frames frequently where before it would not be an issue
tingtong5
4th June 2017, 20:41
After using Kodi Dsplayer x86 16.3 for a long time I upgraded to Kodi Dsplayer x86 17.3 today, using exact same settings. Average frame rendering times are higher now then before resulting in dropouts in video playback. I checked and all madvr settings (0.91.10) are still the same as before.
Is this a known issue?
Can you guys help me troubleshoot and solve this?
Thanks a lot!
Ronald
Mangix
4th June 2017, 20:54
Are there any known fixes for this issue? https://forum.redfox.bz/threads/windows-10-creators-update-messed-up-reclock.72475/
Basically the creator's update has resulted in the loss of normal playback using madvr with reclock, with repeated/dropped frames frequently where before it would not be an issue
Upgrade to Windows 8.1.
johnnylaiyee
5th June 2017, 02:11
After upgrading to madVR v0.91.10 I start seeing two chroma upscaling in OSD
One is super-xbr which I selected, one is Bicubic60 which I didn't select.
Is it a bug or a messed up setting?
Georgel
5th June 2017, 02:12
I got a question!
How can we enable screen shots in MPC-HC + madVR?
I tried taking a few while in full screen, but it resulted in screenshots without madVR applied and at a strange resolution of 1916 * 1076, no idea what I'm doing wrong...
johnnylaiyee
5th June 2017, 02:19
I got a question!
How can we enable screen shots in MPC-HC + madVR?
I tried taking a few while in full screen, but it resulted in screenshots without madVR applied and at a strange resolution of 1916 * 1076, no idea what I'm doing wrong...
Are u in FSE mode?
Georgel
5th June 2017, 02:20
Are u in FSE mode?
Not right now, I usually have FSE mode disable to avoid some crashes on the GPU I had before. Does it work only in FSE mode?
Georgel
5th June 2017, 02:24
I just tried taking a screen shots in FSE, no effect.
All screenshots taken when using F5 or AL+I result in no effect, both take a screenshot of the original movie file with no madVR processing (for example, no edge thinning, no chroma upscaling, just the original movie file)
Taking a screenshot with print screen and pasting it in a photo editor works, but I would like something that would work faster...
johnnylaiyee
5th June 2017, 02:26
The reason I asked if you are in FSE mode is telling you not to.
Maybe try Potplayer or Jriver to cap screen?
Georgel
5th June 2017, 02:48
The reason I asked if you are in FSE mode is telling you not to.
Maybe try Potplayer or Jriver to cap screen?
Thank you for your help!
I'll try potplayer and Jriver and see if they solve anything!
cork_OS
5th June 2017, 06:39
How can we enable screen shots in MPC-HC + madVR?
1. Disable FSE for full-screen screenshots
2. Hide MPC-HC GUI controls ("1" key by default) for windowed screenshots
3. Press ALT+Print Scrn for windowed screenshot (Print Scrn for full screen)
4. Paste screenshot in any image editor.
5. Save it manually
Guys I never get ant dropped frames but I get a repeated frames approx every 3 mins. I have the 1080 TI card set to 23fps. and upscale all my ripped BDs to 4k and play in their native fps.
I use JRiver with madvr.
Does this look normal even after playing a film for approx 20mins?
Am I doing something wrong with my settings or is this normal?
When it repetes a frame I can see the image jump, would much prefer it to run smoother... Im also on windows 10.
display 23.97869Hz
compostion rate 23.976Hz
clock deviation -0.01158%
smooth motion off
D3D11 fullscreen windowed (8bit)
movie 23.976fps
1 frame repeate every 3.29mins
movie 1920x1080 16.9
scale 0,0,1920,1080 >0,0,3820,2160
touch window from inside
chroma > NGU sharp (high)
Luma > NGU sharp (high)
chroma > NGU sharp (low)
vsync 41.70ms, frame 41.71ms
matrix BT.709 (best Guess)
deinterlacing off (settings)
decoder queue 15-16/16
subtitle queue 15-16/16
upload queue 7-8/8
render queue 7-8/8
present queue 6-7/8
dropped frames 0
repeated frames 7
delayed frames 0
presentation glitches 0
average stats
rendering 15.22ms
present 0.25ms
max stats (5s)
rendering 16.68ms
present 0.41ms
johnnylaiyee
5th June 2017, 07:16
Guys I never get ant dropped frames but I get a repeated frames approx every 3 mins. I have the 1080 TI card set to 23fps. and upscale all my ripped BDs to 4k and play in their native fps.
I use JRiver with madvr.
Does this look normal even after playing a film for approx 20mins?
Am I doing something wrong with my settings or is this normal?
When it repetes a frame I can see the image jump, would much prefer it to run smoother... Im also on windows 10.
display 23.97869Hz
compostion rate 23.976Hz
clock deviation -0.01158%
smooth motion off
D3D11 fullscreen windowed (8bit)
movie 23.976fps
1 frame repeate every 3.29mins
movie 1920x1080 16.9
scale 0,0,1920,1080 >0,0,3820,2160
touch window from inside
chroma > NGU sharp (high)
Luma > NGU sharp (high)
chroma > NGU sharp (low)
vsync 41.70ms, frame 41.71ms
matrix BT.709 (best Guess)
deinterlacing off (settings)
decoder queue 15-16/16
subtitle queue 15-16/16
upload queue 7-8/8
render queue 7-8/8
present queue 6-7/8
dropped frames 0
repeated frames 7
delayed frames 0
presentation glitches 0
average stats
rendering 15.22ms
present 0.25ms
max stats (5s)
rendering 16.68ms
present 0.41ms
There are two solution for this.
1. use the video clock function in Jriver
2. use a custom refresh rate close to 23.976
Actually, I use both and never repeated any frames with my GTX1050
ashlar42
5th June 2017, 10:34
Guys I never get ant dropped frames but I get a repeated frames approx every 3 mins. I have the 1080 TI card set to 23fps. and upscale all my ripped BDs to 4k and play in their native fps. Have a look here: https://forum.doom9.org/showthread.php?t=173571
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.