[WiP] madVR support in MP1 (8 Viewers)

[kenwonders]

Another bit of visible evidence: 85 and 86 do not appear to raise the rendering times to vsync value 'so often'. This is regarding the issue whereby sometimes the rendering time in madVR is raised to the vync timing value (as if something is 'holding' the rendering process for the lengh of the vsync timing).

So is this good ? [emoji4]

Psychologically yes

It the lower values are correct then I have more NNEDI3 neurons to spend on PQ

I think also this results in less stutter, as scenes that need more than frame time to render will have the time to do that without lowering the overall queue (how will it catch up if it can only run as fast as the frame rate). The Star Wars 2160p played with a few little stutters in older builds, and so long as I've checked it started ok with low rendering times (it does not always), it plays frame perfect now.

I'm also getting the madVR crash at first video/tv play a lot in recent builds as reported before.

 

[Sebastiii]

@kenwonders

Can you use the latest dshowhelper, it has more log :
Correct log should be :

[2016-05-27 20:26:49,246] [       0] [73ec] - MPMadDshow::MadInit 1
[2016-05-27 20:26:49,246] [       0] [73ec] - MPMadDshow::MadInit 2()
[2016-05-27 20:26:49,246] [       0] [73ec] - MPMadPresenter::Constructor() - instance 0x136db6e8
[2016-05-27 20:26:49,246] [       0] [73ec] - MPMadPresenter::MPMadPresenter()
[2016-05-27 20:26:49,246] [       0] [73ec] - MPMadDshow::MadInit 3()
[2016-05-27 20:26:49,246] [       0] [73ec] - MPMadPresenter::Init 1()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 2()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 3()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 4()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 5()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 6()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 7()
[2016-05-27 20:26:49,293] [       0] [73ec] - MPMadPresenter::Init 8()
[2016-05-27 20:26:49,294] [       0] [73ec] - MPMadPresenter::Init 9()
[2016-05-27 20:26:49,294] [       0] [73ec] - MPMadPresenter::Init 10()
[2016-05-27 20:26:49,294] [       0] [73ec] - MPMadPresenter::Init 11()
[2016-05-27 20:26:49,294] [       0] [73ec] - MPMadDshow::MadInit 4()
[2016-05-27 20:26:49,294] [       0] [73ec] - MPMadDshow::MadInit 5()
[2016-05-27 20:26:49,294] [       0] [73ec] - MPMadDshow::MadInit 6()
[2016-05-27 20:26:49,474] [       0] [72a0] - MPMadPresenter::SetDevice() pD3DDev 0x:b96e2c0
[2016-05-27 20:26:50,835] [       0] [73ec] - MPMadPresenter::Shutdown()
[2016-05-27 20:26:50,835] [       0] [73ec] - MPMadPresenter::Shutdown() 1
[2016-05-27 20:26:50,835] [       0] [73ec] - MPMadPresenter::Shutdown() 2
[2016-05-27 20:26:50,835] [       0] [73ec] - MPMadPresenter::Shutdown() 3
[2016-05-27 20:26:50,835] [       0] [73ec] - MPMadPresenter::Shutdown() 4
[2016-05-27 20:26:50,836] [       0] [73ec] - MPMadPresenter::Shutdown() 5
[2016-05-27 20:26:50,836] [       0] [73ec] - MPMadPresenter::Shutdown() 6
[2016-05-27 20:26:50,836] [       0] [73ec] - MPMadPresenter::Destructor() - instance 0x136db6e8
[2016-05-27 20:26:50,836] [       0] [73ec] - MPMadPresenter::Destructor() 2
[2016-05-27 20:26:50,836] [       0] [73ec] - MPMadPresenter::Destructor() 3
[2016-05-27 20:26:50,836] [       0] [73ec] - MPMadPresenter::Destructor() 4
[2016-05-27 20:26:50,837] [       0] [73ec] - MPMadPresenter::Shutdown() 7

 

[kenwonders]

@kenwonders

Can you use the latest dshowhelper, it has more log :

Is that a new version that you've just pushed or that I was using the wrong version?

 

[alexdepalma]

So is this good ? [emoji4]

Psychologically yes

It the lower values are correct then I have more NNEDI3 neurons to spend on PQ

I think also this results in less stutter, as scenes that need more than frame time to render will have the time to do that without lowering the overall queue (how will it catch up if it can only run as fast as the frame rate). The Star Wars 2160p played with a few little stutters in older builds, and so long as I've checked it started ok with low rendering times (it does not always), it plays frame perfect now.

I'm also getting the madVR crash at first video/tv play a lot in recent builds as reported before.

I didn't notice the video 4K playback improvement.
I can play H265 4K Elysium trailer fluent by the first time (EVR also).
May be one small jump and few frame lost. But visually perfect with CPU close to 100%.

Unfortunately MP crashed (forgot to get Madvr freeze rep, sorry)

Great.

Congrats Seb

 

[Kotik]

Seb hi,

How do i remove the stats from the left side? I tried CTRL + J but it simply doesn't work. It does work outside of MP, if i do it in MP-HC stats do turn off, but inside MP they always remain on no matter what i try to do.

And my final question, where do u suggest we switch refresh rate? From MP or from madvr?

 

[daWooky]

Not sure if this is new with V85 but;-

When playing anything (TV, HD, SD OV +++) in fullscreen mode if I toggle to windowed mode then stop the playback I get a blackscreen hang, no response to remote except until I toggle back to fullscreen and then everything goes back to normal. Same thing the other way round i.e. play video in windowed mode then toggle to fullscreen then stop playback....blackscreen hang.
100% reproducible on my HTPC.
No problem with playback and stop as long as I don't toogle.
Can upload logs if required.

yap, i have the same

 

[Sebastiii]

Seb hi,

How do i remove the stats from the left side? I tried CTRL + J but it simply doesn't work. It does work outside of MP, if i do it in MP-HC stats do turn off, but inside MP they always remain on no matter what i try to do.

And my final question, where do u suggest we switch refresh rate? From MP or from madvr?

It simply works about refresh rate when using madVR we need to not use internal one, in next version (later) internal refresh rate will be disable when madVR is in use

 

[Sebastiii]

@kenwonders

Can you use the latest dshowhelper, it has more log :

Is that a new version that you've just pushed or that I was using the wrong version?

In last few log, there is not all log line (mad.log) or i missed to push ? need to check that

 

[daWooky]

and did a simple madshi splashscreen for default hd

@Kotik the stats should disappear, but the show stats stay enable if u use it, for example if you enable it in mphc it is also enabled in Mepo.

 

[Sebastiii]

Strange it seems that is pushed @kenwonders