[WiP] madVR support in MP1 (7 Viewers)

[Sebastiii]

I have looked the log and didn't notice something wrong, but if you can reproduce easily :
1- Can you try with watchdog (first option) but clear/remove older log ?
Madshi send me a tool that permit to create a freeze report when madVR itself can be done.
So could be nice to use that tool and save the freeze report from it.

2- D3D11 has a possible deadlock but should be ok with the future madVR version but if you can supply log from it hang, it can confirm that it's the same issue

 

[joecrow]

Attached are Option 1 logs as requested and the trace from the Madshi tool (seperate incidents).
Cheers

 

[Sebastiii]

So we can see the freeze
Does it happen only with D3D11 right ?

 

[joecrow]

Does it happen only with D3D11 right ?

Yes, Cuvid and DXVA2-Copy-back work fine, did not try native with TV yet.

 

[Sebastiii]

Guys
V327 in first post
Should fix some issue on zapping with D3D11, internal blu-ray menu when starting with a static one (selection language for ex).
Thanks.

 

[joecrow]

V327 in first post
Should fix some issue on zapping with D3D11

Great job that has fixed my zapping problem with D3D11, (using atest nightly Lav and std. Mafvr 0.92.2)
D3D11 still goes into stutter/hang with problem recording (the one that gives green screen with copy-back but works ok with cuvid).

 

[el Filou]

Hello fellow madVR users.

I started using madVR recently and I am quite happy with how MP works with it except for a few issues, but I'm confused about the first post: I wanted to know if it was possible to just replace only some files on a release/pre-release MP installation with the newer ones with changes to madVR, or do you need to reinstall the whole builds each time?
I customise my MP install a bit and I wouldn't want to install unstable builds every few days just to test madVR. Is that possible and if so which files should I backup and replace with new ones? Or are these "madVR branch builds" only changing the madVR support and always based on the latest release/pre-release?
I currently use MP 1.17 Final with the madVR support that came with it, with latest LAV nightly and madVR 0.92.2, and use D3D11 for decoding and present (Windowed mode).
Thanks!

 

[Sebastiii]

Hi @el Filou

I'm trying to keep up to date madVR build against master branch, so latest installer is 1.18pre-release + latest madVR change that will be go in 1.18Final, ofc we need to have regression testing about it.
Still you can easily revert to 1.17.
You need full installer because recent change also change by new code so you can't only overwrite files (sometimes it's ok but over a 1.17 it will not work)
EDIT : The installer in first post do an upgrade, so it will keep your current settings

@joecrow that's nice, maybe nevcairiel need to analyse file to see if it can do something one thing i would try is to play the .ts over myvideo (with that setting below) :

from :

If it works, then it's maybe to solve this from TsReader but it it does the same, then LAV Video need to be fixed or not (nevcairiel can tell us)

 

[Ruben35]

I'm also new with madvr and mediaportal. I installed the latest patch from page 1, but it's still v1.17 and not v1.18 pre.
Do I have to install the v1.18 pre after? Thank you for your great work !

 

[Sebastiii]

Thanks
Will look why maybe i didn't merge the branch update.
Let see and i will provide a new installer if it's the case.