[WiP] madVR support in MP1 (16 Viewers)

[rohnfe]

I am on the

• latest Win 10 creators update (Fall Update)
• latest version of MP in first Post
• latest MadVR
• Nvidia drivers last version (have not installed the newest Spectre/Meltdown fixed one)

Let me know if i can be of any help testing something!

The only that does not seem to be working for me is 3D in windowed mode and HDR files do not play correctly any more (starts with a lot of stutter and blackscreen, after a while the video will play but the TV does not switch to HDR )

 

[joecrow]

Lots of testing today in the hope of getting a base fully functional MP on my Desktop (with FCU and latest (17.12.2 AMD vid. drivers). Testing with TV, OV and HD vids (including the 4K Elysium demo) mostly in windowed mode with the occaisional toggle to fullscreen and back:-
1) MP 1.8 Final- No Madvr crashes, just a single incident of a partial hang while navigating (kind of a 15sec hiccup) but no crash (Madvr or MP) which cleared and continued OK. Same test type on my HTPC (MP 1.18 Final, Win 10, 1703 with a slightly older 17.11.2 AMD vid. driver) all 100% OK.
2) MP 1.19 pre- On my Desktop PC, same tests, Madvr crashes quite quickly.
3) V9 based on earlier testing I thought this was OK but sadly after a very long time this also gave a Madvr crash.
Reran 2&3 with an old AMD driver (17.7.2), with same result.
4) v430 after new install of AMD 17.12.1 driver, failed quite quickly. I then enabled the FCU workarround and have had no problems since. Not sure if this gives a clue as to what is happening, I will continue testing and get back if I do get further problems.

 

[Sebastiii]

Guys big thanks
I'm trying also to test old version and find where can be the culprit too

 

[Sebastiii]

Here we go for the V431, it seems better about the D3D null reference exception
@joecrow hope it will be better for you too

 

[daWooky]

thanks seb,
here are some logs from yesterday on the previous version
damn strange.. it worked for hours but then on next start or stop a fullreset or freeze or....

also available in a green and with nvidia dll....

 

[Sebastiii]

Thanks for logs
Will look more in detail but the BSOD can happen on my side with exclusive mode at least on DEV PC it happen so much that i didn't try it anymore but i was also able to reproduce it with mpc-hc so it's a bug in nvidia + windows i think.

The annivers MediaPortalLogs_13_01_18__00_40.zip was with the latest installer ? (from the previous post V431) ?
I have also updated the first post with V433 because i have noticed a freeze when doing pause so added something and i wasn't able to reproduce it lol

 

[kenwonders]

thanks seb,
here are some logs from yesterday on the previous version
damn strange.. it worked for hours but then on next start or stop a fullreset or freeze or....
View attachment 195385
also available in a green and with nvidia dll....

Hi daWooky, I only get BSOD on 390 version NVIDIA driver, yesterday I removed this with DDU and let WU install 388.71. There have been zero issues in latest MP since doing this, including this mornings Kid based OV hammering

 

[daWooky]

have been zero issues

thanks. and well, i wish you that it stays that way but fingers crossed and better put ya axe far away^^

WU install 388.71

on the anniversary i first had to teach wu. to not load the driver..its so great when drivers are being updated unwanted. wumt ftw

s_13_01_18__00_40.zip was with the latest installer

nope, they should be with v430 not tried 431 or 433

BSOD can happen on my side with exclusive mode

what winver on dev currently?
i haven't tried it further on the anniversary image with fse enabled but it was working before with older mepo versions on it... now its somehow busted but same goes for dx11

also able to reproduce it with mpc-hc so it's a bug in nvidia + windows i think

yep, it seems bugged from two sides dito. what i think (fear) too
however with mphc i have to switch many many files with some heavy decoding to get it down to...

 

[daWooky]

and i forget a older thing, @Sebastiii
i wanted to ask you about auto3d detection. tried 16.0.6 and 0.7 on my old htpc and it seems that now it needs more power than before somehow. because now i actually really see some frame drops on the detection runs at the video start. i compared it yesterday also on a strong gaming rig and there i have no visual drops but still see some in stats and the rendering times jumps prtty high on detection, i think way more than before...
btw. old main htpc (1703/nv358.28) with dx9 fse... version is from last year. i dont know the number anymore but the builddate said from 28.12.17. so far still working great.

 

[Sebastiii]

Hey on dev i have set 17074 but didn't try FSE on this, but FSE was able to crash BSOD quite on all insiders i have try not always but while debugging it happen really quick
I need to look the commit on auto3D to remember the change but i think i have added some lock to avoid some issue while madVR wasn't available anymore and maybe it get slower.

I have let running latest MP on DEV so far so good for now