Log in

View Full Version : madVR, Nvidia Optimus and Maxwell (850M)


Pages : 1 [2]

Ceremony
2nd January 2015, 20:45
i dunno, but i get black screen only sometimes when resizing or going fullscreen/windowed.

@zachs, ill take a look

EDIT1:
880M is NOT a maxwell card btw, so replicating it will be difficult due to obvious reasons (maxwell+optimus+madVR has lots of issues. read this thread for more info)

EDIT2:
I haven't tested it yet, but I do suspect that the gpu is either overheating, battery is low or that some other auto power state change... either way, something that throttles. I somewhat doubt that its caused by your application, as for one, it would probably happen on more systems than just his laptop

nekromantik
2nd January 2015, 21:36
Mine is Keplar 860m not the maxwell variant. But I still have that issue.

Zachs
3rd January 2015, 01:48
@nekromantik

Which issue? Render time increasing with MPDN?

nekromantik
3rd January 2015, 12:18
No black screen when using madvr.

Haxton Fale
23rd February 2015, 13:35
Not that it's very constructive, but I too have the same issue - namely madVR giving me a black screen and crashing the players (MPC-HC, MPC-BE) whenever I try to run it with my GTX860M (Maxwell, I believe? that's what I found for Lenovo Y50-70). Is anyone still looking into it? It's not a constant issue, but every once in a while I do have trouble with playing stuff on the Intel GPU. MPDN does the trick, but only if I don't have subs in a separate file, and even then it tends to be not particularly stable (plus lacking support for my remote :P ).

hashanga
23rd February 2015, 18:38
MPDN is so far the only method that worked. It does almost all of the things I wanted from MadVR (+with GPU acceleration). Even NNEDI is there. Anyway SVP, if you're using, suffers from a noticeable video jitter, almost unusable with recent versions.

MPDN does the trick, but only if I don't have subs in a separate file

I don't really get what you meant with the subtitle problem. I use ffdshow (via ffdshow raw video filter in MPDN) to apply subtitles, post processing and SVP. The subtitles will be of the resolution of the source video (so not always as crispy as in mpc-hc). I use a software called "dsrt" when subtitles are muxed into the video file(when there isn't a separate subtitle file). ffdshow can load external subtitles. What method are you using for subtitles?

PS: Welcome to doom9 :)

Asmodian
23rd February 2015, 20:17
Not that it's very constructive, but I too have the same issue - namely madVR giving me a black screen and crashing the players (MPC-HC, MPC-BE) whenever I try to run it with my GTX860M (Maxwell, I believe? that's what I found for Lenovo Y50-70). Is anyone still looking into it? It's not a constant issue, but every once in a while I do have trouble with playing stuff on the Intel GPU. MPDN does the trick, but only if I don't have subs in a separate file, and even then it tends to be not particularly stable (plus lacking support for my remote :P ).

I understand this was determined to be driver issues that would take a lot of changes in madVR to workaround. I would not expect a change from madVR to fix it (anytime soon at least) but maybe Nvidia will improve the drivers.

MPDN is so far the only method that worked. It does almost all of the things I wanted from MadVR (+with GPU acceleration). Even NNEDI is there. Anyway SVP, if you're using, suffers from a noticeable video jitter, almost unusable with recent versions.

NEDI is not NNEDI3, they work very differently; NEDI does not use a neural net. NNEDI3 is better IMO (and slower).

hashanga
23rd February 2015, 20:27
NEDI is not NNEDI3, they work very differently; NEDI does not use a neural net. NNEDI3 is better IMO (and slower).

Very true. But I omitted that fact as NEDI+SuperRes looks almost as good as NNEDI3 or maybe better. For me, I don't see any difference(someone might, but still better than nothing) . On the plus side, MPDNs (GPU assisted?) NEDI implementation of MPDN runs much faster than NNEDI3 of MadVR with close-enough quality. Also, SVP is nearly impossible in my system with NNEDI3.

And thanks for mentioning the fact that NEDI doesn't use a neural net. Somewhere after I started using MPDN, I totally forgot that fact!

EDIT: @Asmodian thanks for pointing out that NEDI is the correct term (not NNEDI)

Asmodian
23rd February 2015, 23:07
It is simply NEDI, no double "N". Helps reduce confusion. ;)

Haxton Fale
24th February 2015, 10:31
I understand this was determined to be driver issues that would take a lot of changes in madVR to workaround. I would not expect a change from madVR to fix it (anytime soon at least) but maybe Nvidia will improve the drivers.


Alright, guess I'll have to simply wait.

I don't really get what you meant with the subtitle problem. I use ffdshow (via ffdshow raw video filter in MPDN) to apply subtitles, post processing and SVP. The subtitles will be of the resolution of the source video (so not always as crispy as in mpc-hc). I use a software called "dsrt" when subtitles are muxed into the video file(when there isn't a separate subtitle file). ffdshow can load external subtitles. What method are you using for subtitles?

I guess I did not expect to have to go to filter options to simply load subtitles. The subs in question are in plain SRT and usually they load by default and/or get a separate but universal option under File. I'm using XySubFilter and it seems to open the stuff just fine if I load a film, go to filter options, and load the file.

PS: Welcome to doom9 :)

Thanks :)

Kevin Gilmore
18th November 2015, 05:14
Just wanted to say optimus driver fixes by Ceremony (I presume for all Mobile Maxwell Architecture/ say 980M too) work ENTIRELY

Makes me very happy. The super-xbr filters by Hyllian are particularly excellent for the laptops! (I'm on a 4kIGZO+Quantum-dot) 15.6 display, so really appreciate the ability to get some real-world, ocassional very practical use from these renders (definitely for say 1080p files, so far). XBR is so low power consumption that the fan-speeds are basically negligible (relative to bog-standard rendering).
I like it

Thanks to all affiliated with making the numerous renders out there happen. This turned out well! People shouldn't be so hard on laptop hw: apparently, through this frankly easy/forthright fix, it works.
Special-thanks to Ceremony.

Will cross-examine/reference the stats with others findings and the Intel hd4600 -to see if the delays/some sort of incompatibility still seems to exist in the NV/Optimus driver), driver; So far seems good though.
This type of fix may be useful for Arctic-Islands or Pascal mobile in the future!

Ironclad
23rd June 2016, 11:05
You guys are life savers. I was going through hell getting my HP Omen configured with it's 860M. Still choosing between SVP and madVR is disappointing. I figured with an i7 quadcore, hyperthreading, SVP would be no trouble but as usually it just doesn't agree with madVR. I really hope Vapoursynth integration comes soon to madVR. I'll try with Interframe+madVR next.

jerryleungwh
12th July 2016, 16:01
Guys I'm an optimus user too and the problems I've encounter are that I've used the copy-rename method to enable MPC-HC to use the nvidia GPU(gtx 960M) with madVR but I can only play a video in D3D11 windowed mode. I wish to use the D3D11 fullscreen exclusive mode for 10bit output but when I do that it says "exclusive mode failed". How can I fix this problem?

CarlosCaco
7th August 2016, 15:50
Guys I'm an optimus user too and the problems I've encounter are that I've used the copy-rename method to enable MPC-HC to use the nvidia GPU(gtx 960M) with madVR but I can only play a video in D3D11 windowed mode. I wish to use the D3D11 fullscreen exclusive mode for 10bit output but when I do that it says "exclusive mode failed". How can I fix this problem?

Try remove the driver and do a clean reinstall... I recomend DDU tão remove the driver... Also you can reset madvr settings even redownload and reinstall madvr

Asmodian
12th April 2018, 03:42
UHD bluray is 10 bit HEVC, the i7-4700HQ does not have hardware decoding for 10 bit HEVC and it is too slow to decode it in software. Sorry. :(