madVR - high quality video renderer (GPU assisted)

[Khaled1323]

whenever i play something on mpc/madvr it changes my monitors color, can i disable that?

[huhn]

can you be a little bit more precise?
madVR can't change your monitors settings but it >can< unload an icc file for playback.

[Knight77]

Hi,

I've got a GTX1070, Sony 4k TV and Pioneer LX59 AVR capable of Ultra HD Pass-through with HDCP 2.2 (4K/60p/4:4:4/24-bit, 4K/24p/4:4:4/36-bit, 4K/60p/4:2:2/36-bit), using Windows 10 last update.

If in nVidia settings I set the desktop to RGB Full 8bit everything works fine. If I try to set it to ybcr 422 12bpc (or 10) the green on desktop looks really pushed and if I play MPHC+madVR fullscreen the movie looks black white and green, no other colours. If I don't play it in fullscreen it's fine (but shows 8bit).

I read that with my config and content (fullhd and 4k) it would be better to go with YBCR 4:2:2 12bpc but I got this problem and I'd like to solve it even if don't know why. Tried to change HDMI cable, that was already good, and nothing changed.

Any idea?

Hope so....thanks!

[huhn]

nothing wrong with 4:4:4 8 bit RGB and most likely the best anyway for 60 hz.
i can only point you to other GPU driver.

[Knight77]

Originally Posted by huhn

nothing wrong with 4:4:4 8 bit RGB and most likely the best anyway for 60 hz.
i can only point you to other GPU driver.

Thanks, I'll try other drivers, BTW my content it's all 1080p or UHD 23.976 so no 60hz, but maybe it would be better to use the 10/12 bit, no?

[huhn]

yes RGB 12 bit should work just fine and is clearly better than 4:2:2.

[Khaled1323]

Originally Posted by huhn

can you be a little bit more precise?
madVR can't change your monitors settings but it >can< unload an icc file for playback.

I think thats what does. I have my own icc file on windows settings,
but when i play something it changes. Can I stop it from doing it?

[huhn]

by default it shouldn't do that.

you can find the option under device -> "your device name" -> calibration uncheck "disable GPU gamma ramp"

[jkauff]

Originally Posted by nevcairiel

That it works with an old version of madVR does indicate that something triggered the bug in madVR, and possibly madshi could do something about it, though. Its not like FSE doesn't work entirely on FCU, in all the games I tried it also works fine.

I think madshi's indicated in the past that he doesn't want to spend too much time on workarounds for problems in Win 10 because it's a moving target. Each new release seems to break something that worked in the previous release, and he doesn't have a team of developers like Nvidia and AMD do for modifying their drivers (and they're having their own problems keeping up).

I'm sure this bug/issue will be fixed at some point, but it may be low on his priority list. Nevertheless, madVR 1.0 will have to work well on Win 10 because so many people are using it, so we just need to be patient.

[Knight77]

Originally Posted by huhn

yes RGB 12 bit should work just fine and is clearly better than 4:2:2.

RGB 12 can't be done in 4K, so if I want to go 10/12 bit I have to go YBCR but then I have tthe green tone problem

[huhn]

no RGB 12 bit is part of the spec. it can't be done at 50/60 hz but 23-30 hz can do it.

[nevcairiel]

Originally Posted by Knight77

RGB 12 can't be done in 4K, so if I want to go 10/12 bit I have to go YBCR but then I have tthe green tone problem

RGB 12-bit can be done at 24Hz just fine, just not at 60. Additionally, you should always prefer RGB 8-bit over YCbCr 4:2:2 10/12-bit. With proper dithering, chroma is more important for image quality.

[mclingo]

Originally Posted by jkauff

I think madshi's indicated in the past that he doesn't want to spend too much time on workarounds for problems in Win 10 because it's a moving target. Each new release seems to break something that worked in the previous release, and he doesn't have a team of developers like Nvidia and AMD do for modifying their drivers (and they're having their own problems keeping up).

I'm sure this bug/issue will be fixed at some point, but it may be low on his priority list. Nevertheless, madVR 1.0 will have to work well on Win 10 because so many people are using it, so we just need to be patient.

That makes sense, however the creators update is likely to be the last free major update so we could do with getting everything working with that, then we can all just sit on that version, there is too much missing in the way of features on pre 1709 versions, connect to mobile for one is essential for me.

yup, we'll all just have to be patient, in the meantime I think i'll image my curent C drive and dual boot 1703 and 1709 so I can retesting MADVR with each new release whilst having a stable platform to use in the meantime, I can live with some of the issues with creators update but I cant live with frame drops every 40 seconds, I couldnt solve that whatever I did and thats really odd as I get the same problem playing HDR movies on the pre creators update, these issues are connected somehow, hoping the issue will be spotted and fixed soon.

Note however on creators update HDR was fully working for me using exclusive mode, it even triggered HDR on my LG OLED, just couldnt live the frame drops, so close yet so far....

[ashlar42]

Originally Posted by mclingo

That makes sense, however the creators update is likely to be the last free major update

And what makes you think that?

[mclingo]

i read it somewhere, happy to be proven wrong.

[EmuAGR]

Originally Posted by huhn

as madshi said you need to send 10 bit to the GPU driver or passthrough doesn't work with AMD it doesn' t matter if your screen is 8 bit.

I can confirm this did the trick, madVR's display settings need to be set to 10 bit panel. But in fact, exclusive mode is still required, not just fullscreen. Thank you very much, madshi and huhn.

[mclingo]

so to sum up, people on the fall creators update using AMD card have the following problems:

PROBLEMS

(A) - black screen on newer version of MADVR
(B) - frame drops ever 40 seconds regardless of what versions of MADVR, LAV or AMD drivers are used - reclock also does not resolve this.


WORKING

(A) - using 0907 MADVR HDR works and triggers HDR mode on passthrough but has frame drops every 40 seconds
(B) - using 0907 SDR works but with frame drops every 40 seconds
(C) - using 0907 MVC 3D using FSE mode works but with frame drops every 40 seconds.

So if we can find away to fix the 40 second frame drop and then fix in V1.0 what got broke in V0908 onnwards we could be there for AMD users.

[huhn]

Originally Posted by EmuAGR

I can confirm this did the trick, madVR's display settings need to be set to 10 bit panel. But in fact, exclusive mode is still required, not just fullscreen. Thank you very much, madshi and huhn.

w7 doesn't support 10 bit windowed so kind of.

[aufkrawall]

Please don't confuse people with calling borderless = windowed, they are not necessarily treated the same by DWM.

[Soulnight]

Originally Posted by aufkrawall

It doesn't make sense to put the load of decoding on the CPU since D3D11VA decoding without copyback (LAV Filters nightly) doesn't steal any performance from madVR.

Originally Posted by clsid

MadVR uses the GPU to which your monitor is connected. LAV uses that same GPU by default for hardware decoding. If you select DXVA2 Copyback or D3D11 in LAV Video, then you can override which GPU is used for decoding. But that only has effect on LAV.

Thanks guys.
I guess Il will try to convince myself with doing the hardware decoding with my RX560 which has only 55% load by 4K Interpolation. And see if I get any benefit for the GTX1080TI and rendering time in Madvr.

It seems smarter that way to me.

Currently I am doing:
1) Hardare HEVC decoding: GTX1080TI
2) FI 4K24p-->60p: AMD RX560 with bluesky FRC
3) Rendering madvr: GTX1080TI

Maybe if Decoding speaks directly to the Fi on the same card, it would be better.