madVR - high quality video renderer (GPU assisted)

[MS-DOS]

madshi,

Zoom control doesn't work for me with native DXVA decoding. Is that intended or I should make a bug report ?

[tFWo]

Subtitles position (edit: and size, they become smaller) is wrong when upscaling with latest madVR and MPC-HC(internal subtitle renderer).

http://i.imgur.com/p85kDJ7.jpg

[kasper93]

@tFWo: Yeah, it is broken with v0.89.5. You need to wait for next version.

[videonerd]

Hi madshi,

DontRenderAfterStop does eliminates blank frame during playrate change but still introduces some lag during playrate changes (both increase and decrease). The lag duration seems to depend on the bitrate of the file. The behaviour of the renderer seems to still be different from pre 88.16.

I also notice the following - when playrate changes, the renderer temporarily displays a future frame (presumably the last frame in the buffer) before reverting to the earlier frame (with DontRenderAfterStop).

Let me know if you need further information.

[XRyche]

Subtitles position (edit: and size, they become smaller) is wrong when upscaling with latest madVR and MPC-HC(internal subtitle renderer).

http://i.imgur.com/p85kDJ7.jpg

Actually there is a way around this until Madshi or MPC-HC can get around to looking at it. The problem is you have to use "Default Style" and make sure the selection box for "position subtitles relative to video frame" is only partially filled in the Options menu under Subtitles and then Default style . The check box has three different states; filled, partially filled and empty. It will tell you exactly what it does if you mouse over the check box.

The down side is no stylized subtitles but the subtitles won't be small or in the middle of the screen when you upscale in Full Screen.

It's by no means a perfect solution but a quick fix-it until it can be addressed.

[kasper93]

...or MPC-HC can get around to looking at it.

I already have looked at it and it will not work with latest version, because madVR pass wrong video rect. I said few post before, please use older madVR build. Or like you already noticed you can use subtitle positioning independent of video rect.

[XRyche]

I already have looked at it and it will not work with latest version, because madVR pass wrong video rect. I said few post before, please use older madVR build. Or like you already noticed you can use subtitle positioning independent of video rect.

I actually saw your post. I was just offering an alternative until the issue got resolved. I suppose I didn't make myself clear on that point. :o

[mindz]

I ran in to a problem with a 1920x1080 resolution tv serie, this doesnt honor the DXVA scaling, since there is no scaling needed, but chroma still needs to be scaled. So it 'falls back' to my choice in the chroma scaling option and therefor gets bad render times (im using Intel), instead of using DXVA for chroma scaling.

[Marnes]

I'm getting a strange problem in potplayer. My video looks like this (sometimes immediately, sometimes after some time playing): https://dropfile.to/M2hih

I've tried a lot of settings and simply nothing helps. I don't know what it's related to or what it's called either so I can't figure it out.

Smooth motion is on (off doesn't help), scaling is basic (I'm not even seeing any resource usage but the sharpening filters work so I guess my settings are kinda light), the rest is all just set to nothing special... I'm clueless.

Any help, please?

[aufkrawall]

Are you using D3D11? If yes, switch to D3D9.

[Marnes]

Are you using D3D11? If yes, switch to D3D9.

Disabling d3d11 did fix the frame glitching, thanks. :) But could it be it also brought down the performance notably? I can't run adaptivesharp now without getting what seems to be underperformance. Gpu-z stopped reading sensors again so I have to look into it a little closer in a while...

[aufkrawall]

I could never notice a real performance advantage of one render path over the other, what was too much with D3D9 was also the case with 11 and vice versa.
But that doesn't have to mean that there wouldn't be such cases.
Could you double-check?
What is your GPU?

[Marnes]

Ugh, I just noticed the stupid intel integrated took over from my geforce again. God I wish I could just disable that crap, but my monitor's hooked right to it. I'll work around that first.

[Marnes]

I had d3d11 enabled because with d3d9 I get this weird flashing black bar that moves around vertically even while the video's paused. What's up with that?

Geforce 740M btw.

[aufkrawall]

I don't know, never heard of it. Maybe an Optimus problem? Tried renaming your media player exe?

[Marnes]

I don't know, never heard of it. Maybe an Optimus problem? Tried renaming your media player exe?

I don't even have optimus or anything. This thing is as big a ripoff as it gets and supports nothing fancy whatsoever. I don't even understand nvidia and their products, it's all just one big pile of numbers that don't line up and features that go unexplained and unmarked.

[Marnes]

FYI disabling windowed overlay fixed the scrolling black bar, whatever it was.

[rbej]

I found strange bug.

When i playing any 1080p 60fps movie in window - madVR show "image < DXVA". Playback is very smooth, without drops and skips. When i switch to full screen "image < DXVA" disappear and playback is poor with drops and skips. Why??. On EVR everything is ok.

I have NUC5PPYH (Braswell CPU), Windows 10 Home, last version MPC-HC, Lav filters and madVR.

madVR all scaling option set to DXVA2.

[Asmodian]

I found strange bug.

When i playing any 1080p 60fps movie in window - madVR show "image < DXVA". Playback is very smooth, without drops and skips. When i switch to full screen "image < DXVA" disappear and playback is poor with drops and skips. Why??. On EVR everything is ok.

I have NUC5PPYH (Braswell CPU), Windows 10 Home, last version MPC-HC, Lav filters and madVR.

madVR all scaling option set to DXVA2.

What resolution is your display? What mode are you using, i.e. dx9, overlay, dx11, new or old path?

[rbej]

1080p. Dx9 old path. Dx11 not work properly. Window mode.

On exclusive mode is this same. No dxva image and poor playback.

[clsid]

"image < DXVA" means image downscaled using DXVA. It does not show that in fullscreen because then no scaling is needed (if you have 1920px screen width).

[YGPMOLE]

Do you have the madVR display mode changer active? If so, which settings are you using? If not, then Direct3D itself decides which refresh rate to use in fullscreen exclusive mode.


The changer is not active, D3D9 is used (D3D11 not checket). With the previous version of madVR I never got problems, now with Windows 10 and the new build I got this issue.

Maybe important to say that the 23.976 fps (doubled with Avisynth in FFDShow to 47.952) remains stable and on the same memory bank even in fullscreen exclusive mode: it changes only with the 25fps (doubled to 50fps in the same way) to the 60Hz memory bank.

And now I discovered another little issue: some subtitle from .MKV tv series are displayed in the center of the screen (in the middle of the image, to be clear), when with the 89.2 build were correctly displayed at the bottom of it. It doesen't happend with the DVD or BD subtitles (it may depend from the type of subtitle used in the .MKV? But I got no problem with them before this "subtitles manager version"...).

Could this be helpful to find a solution?

[XMonarchY]

Damn, the stutter-after-pause is still not fixed and occurs no matter what I try. Its quite annoying having to:
- close the video file
- experience screen-flash refresh rate change from 23Hz to 60Hz (Desktop is @ 60Hz and video files are @ 23Hz)
- open the file again
- experience another screen-flash refresh rate from 60Hz to 23Hz
- find the right spot to continue watching your video file (although I learned to remember the time at which I closed the video file to get back to watching quicker).

Is this bug on the list of "To-be-fixed soon" list?


Also, will Chroma Upscaling SuperRes be updated to the same version as Upscaling Refinement SuperRes?

[DragonQ]

Haven't got any logs but MadVR 0.89.5 is pretty unstable for me. About half of the time, MPC-HC doesn't exit properly when I close it, plus sometimes I'll open a video and the audio will play with no video. If I switch to EVR it plays fine. Hopefully I'm not the only one.

[baii]

Damn, the stutter-after-pause is still not fixed and occurs no matter what I try. Its quite annoying having to:
- close the video file
- experience screen-flash refresh rate change from 23Hz to 60Hz (Desktop is @ 60Hz and video files are @ 23Hz)
- open the file again
- experience another screen-flash refresh rate from 60Hz to 23Hz
- find the right spot to continue watching your video file (although I learned to remember the time at which I closed the video file to get back to watching quicker).

Is this bug on the list of "To-be-fixed soon" list?
Players have a option to remember playback location. I think some earlier build(like 8816ish) seems to don't have this problem(if what you describing is same as what I experiencing).

The problem I think it doesn't always happen 100% after pause, for me it happen more often in windows mode and only seem to occur if I pause it long enough.
Sent from my SM-T700 using Tapatalk

[dansrfe]

Just to be safe: So you agree that playback should be alright as long as you play the movie from start to finish?

Yes, I agree.


Interesting. You don't have "notify media player about cropped black bars" activated, do you? If not, then I'm not sure where such a problem could come from. madVR does have to reconfigure the rendering algorithms if you use "crop black bars" when an AR change is detected, but that should not be visible, at least not if your queues are decently filled. If you get a chance to film this with a digicam, or some other way, I'd love to look into that.

Chroma upscaling is set to super-xbr and Image upscaling is set to Jinc3 AR; no profiles on either. The visual anomaly happens due to a large queue drop from the frame Cinemascope -> IMAX changes. Maybe the GPU can't adapt fast enough. The queue fills up about a second after the transition.

Would it be prudent to have a setting that alters the crop a handful of frames before having a relatively large increase in the resolution in the next scene? I increased the GPU/present queue sizes however it doesn't seem to make a difference in this case.

[chros]

I could never notice a real performance advantage of one render path over the other, what was too much with D3D9 was also the case with 11 and vice versa.
There IS 1 exception: D3D9 old path (when you switch off the present frames in advance box) !! (I'm using it in FSE). It's about 40% faster then the rest!!! (I couldn't try overlay mode at all since it doesn't want to work for me).
Drawbacks (as madshi told us): no overlay mode and no NNEDI3 interop in this mode.

[aufkrawall]

Maybe according to reported render times. But that doesn't mean playback would be stable under extreme conditions while it wouldn't be with new path.
They both give very much the same GPU load reported by driver and it's never good to come in regions where you have almost no reserves left.

[chros]

Maybe according to reported render times. But that doesn't mean playback would be stable under extreme conditions while it wouldn't be with new path.
They both give very much the same GPU load reported by driver and it's never good to come in regions where you have almost no reserves left.
No, it's based on the gpu load! And the gap can be more than 100% as well!!! (It also applies to intel igpu!)
I'll give you exact numbers later, until then you can try it out for yourself :)

[aufkrawall]

There's no difference for me. On the right side, there is new windowed path and on the left side, it's old FSE mode:
http://abload.de/thumb/windowednewbrj8n.png (http://abload.de/image.php?img=windowednewbrj8n.png)
It's the same with old windowed path.
My test case was 1080p60 -> WQHD with Jinc3 + SuperRes 2 passes + Adaptive Sharpen.

[Marnes]

Is there anything in madvr about tearing that I'm possibly missing (which is to say I don't see anything in madvr's settings about vsync)? My config or something else apparently still isn't good because now I constantly get random tearing all the time despite every setting everywhere being set to use vsync. Potplayer is set to vsync, intel and nvidia (which sadly doesn't get used because yay laptop monitor wiring...) are set to vsync, etc. I used madvr a while ago on 7 and 8 and everything just worked, now on 10 with the latest madvr nothing at all just works...

[Marnes]

Is there anything in madvr about tearing that I'm possibly missing (which is to say I don't see anything in madvr's settings about vsync)? My config or something else apparently still isn't good because now I constantly get random tearing all the time despite every setting everywhere being set to use vsync. Potplayer is set to vsync, intel and nvidia (which sadly doesn't get used because yay laptop monitor wiring...) are set to vsync, etc. I used madvr a while ago on 7 and 8 and everything just worked, now on 10 with the latest madvr nothing at all just works...

Why the heck does turning off "delay playback until render queue is full" seem to fix tearing... The way the option is described suggests it's a kind of render buffer exactly to prevent such things...

[aufkrawall]

When you have tearing problems, it's likely not the fault of madVR.
Since Windows Vista, tearing shouldn't even be possible with GPU desktop composition, which can't be turned off anymore since Windows 8. So it's very likely a weird driver or configuration problem.
Maybe you have to use FSE.

[ShadyCrab]

Just want to report spontaneous tearing issues as well. Win 10, GTX 960, newest NVidia driver. DX11 presentation (present every V-Sync ticked), only occurs in Fullscreen Windowed. Also newest MPC-HC nightly build. Its always fixed by simply changing the window size. It can occur less often in the middle of playback, more often when resuming playback.

This might somehow be related to having a multi-monitor setup, both by HDMI at 1080p. There doesn't seem to be anything I can do to 100% prevent tearing except for Fullscreen Exclusive. This isn't something I remember occurring before the time of, say the Win 10 RTM launch.

[aufkrawall]

Yes, this is already known. Use FSE with D3D11 or use D3D9 instead (not a disadvantage at all without FSE).
It's most likely an NV driver bug with Windows 10.

[panetesan2k6]

I was giving a try to a 64bit setup of MPC-HC+MadVR+LAV filters. I have a 64bit OS, of course.

I downloaded and installed the 64bit version of MPC-HC and LAV filters (32bit version is installed too), and MadVR was already installed in the system.

Neither MadVR nor LAV filters show any distinctive info about being 32 or 64 bit during playback. I would think that 64bit MPC-HC will load 64 bit components, but... anyway to check this?

[Telion]

No need to check, 64bit player just can't use 32bit filters and vice versa.

[Kranium]

I upgraded to 89.5 and 0.66 LAV last night and was playing around with some options.

In animated content, I notice that if I use the SuperRes filter in Chroma Upscaling and use SuperRes in upscaling refinement; I get a bit of ringing and lines that are not smooth and are over sharpened. It doesn't get all that much better when I reduce the strength or increase the number of passes. Does this seem like normal behavior? I eventually settled on SuperRes in upscaling refinement and adaptive sharpen in the image enhancements section. Without adaptive sharpen, the lines seemed to fade in 480p > 1080p scaling. It gave me the best results to my eyes at least. All of this with NNEDI64 scaling and doubling.

I know there are a lot of other factors here, I was more curious if one SuperRes option is more useful than the other and if others here have experienced what I did when using both at the same time.

[panetesan2k6]

No need to check, 64bit player just can't use 32bit filters and vice versa.

Thanks :)

[6ari8]

When playing some files the OSD shows this:
http://s1.postimg.org/6egqvkeh7/Untitled.jpg (http://postimg.org/image/6egqvkeh7/)

When most of the time it shows:
Chroma>xxx
Image>xxx

Can some one explain why this happens?

[seiyafan]

I was out of the loop with all the fancy new upscaling algos, has there been any noticeable improvement for 1080 to 1440? Last time when I compared Jinc with NNEDI3 I could hardly tell a difference.

[aufkrawall]

When playing some files the OSD shows this:
http://s1.postimg.org/6egqvkeh7/Untitled.jpg (http://postimg.org/image/6egqvkeh7/)

When most of the time it shows:
Chroma>xxx
Image>xxx

Can some one explain why this happens?
Well, it doesn't show super-xbr in the latter example, does it?
If it doesn't, it's normal. When super-xbr is used for luma, it is always also used for scaling up chroma together.

I was out of the loop with all the fancy new upscaling algos, has there been any noticeable improvement for 1080 to 1440? Last time when I compared Jinc with NNEDI3 I could hardly tell a difference.
Because there hardly is a difference with this scaling factor.
You can try SuperRes (e.g. strength of 2) + Adaptive Sharpen (after SuperRes, e.g. strength of 0.2).
However, AS will make some images noticeably brighter, even with strength of 0.2.
For this reason, I'd appreciate if madshi implemented also Shiandow's sharper SuperRes configuration, e.g. replace the radius checkbox with it.

[6ari8]

Well, it doesn't show super-xbr in the latter example, does it?
If it doesn't, it's normal. When super-xbr is used for luma, it is always also used for scaling up chroma together.


Sorry I just found out that something changed with 89.05's OSD so that anything that has image doubling active seperates image to Luma and Chroma for some reason. It used to be like this before:
http://s16.postimg.org/ic7mqcqrl/Untitled.jpg (http://postimg.org/image/ic7mqcqrl/)

I'm still not sure If I'm understanding it correctly so I need some help with those lines. Given that this video is 712x480 those lines do the following:
1) Double the chroma from 356x240 to 712x480.
2) Double the Luma from 712x480 to 1424x960 then double again to 2848x1920 then downscale with Catmull-Rom AR to 1920x1080.
3) Double the chroma from 712x480 to 1424x960 then double again to 2848x1920.

Is this correct? Doesn't this mean that the end result has different chroma and luma resolutions?

[panetesan2k6]

Just a suggestion for Madshi.

Would it be possible to add OSD On/off to the pop-up menu from the system tray icon?

[XRyche]

Sorry I just found out that something changed with 89.05's OSD so that anything that has image doubling active seperates image to Luma and Chroma for some reason. It used to be like this before:
http://s16.postimg.org/ic7mqcqrl/Untitled.jpg (http://postimg.org/image/ic7mqcqrl/)

I'm still not sure If I'm understanding it correctly so I need some help with those lines. Given that this video is 712x480 those lines do the following:
1) Double the chroma from 356x240 to 712x480.
2) Double the Luma from 712x480 to 1424x960 then double again to 2848x1920 then downscale with Catmull-Rom AR to 1920x1080.
3) Double the chroma from 712x480 to 1424x960 then double again to 2848x1920.

Is this correct? Doesn't this mean that the end result has different chroma and luma resolutions?

The first chroma entry is for chroma upsampling from 4:2:0 to 4:4:4. The second chroma entry is for chroma upscaling for matching the chroma to the luma upscaled resolution. I believe that's correct but if not fell free to correct me anyone.

[ryrynz]

The first chroma entry is for chroma upsampling from 4:2:0 to 4:4:4. The second chroma entry is for chroma upscaling for matching the chroma to the luma upscaled resolution. I believe that's correct but if not fell free to correct me anyone.

That would be right, but you've linked the wrong post to reply to. The previous post from him shows the double chroma OSD lines.


I'm still not sure If I'm understanding it correctly

That's because madVR isn't displaying the quad superxbr scaling that happens automatically alongside the luma scaling.

Doesn't this mean that the end result has different chroma and luma resolutions?

It has to match before it gets displayed.

[rbej]

"image < DXVA" means image downscaled using DXVA. It does not show that in fullscreen because then no scaling is needed (if you have 1920px screen width).

Of course, but why without DXVA downscaling playback is poor like hell??. Downscaling is process who use % CPU and GPU. Without downscaling playback should be more smooth.

[huhn]

what GPU are you using?

there is a small chance that dithering is to hard.

CPU is not used for this what so ever.

[nevcairiel]

I'm still not sure If I'm understanding it correctly so I need some help with those lines. Given that this video is 712x480 those lines do the following:
1) Double the chroma from 356x240 to 712x480.
2) Double the Luma from 712x480 to 1424x960 then double again to 2848x1920 then downscale with Catmull-Rom AR to 1920x1080.
3) Double the chroma from 712x480 to 1424x960 then double again to 2848x1920.

Is this correct? Doesn't this mean that the end result has different chroma and luma resolutions?

If it says "Image" in the OSD, it refers to scaling both Luma and Chroma at the same time (otherwise it would say Luma)
So what it really does is only 2 steps

1) Double Chroma to 712x480, now matches Luma
2) Double the entire image twice (both Luma and Chroma) to 2848x1920, then downscale both components to 1920x1080

[rbej]

what GPU are you using?

there is a small chance that dithering is to hard.

CPU is not used for this what so ever.

Pentium N3700 Braswell (hevc hardware decoding). When i use EVR everything is ok and playback (1080p 60fps files) is very smooth on full screen (1080p monitor). madVR - DXVA Scaling On (window) = perfect smooth playback. DXVA Scaling Off (full screen) = poor playback.