[WiP] madVR support in MP1 (6 Viewers)

[Sebastiii]

i've tried to start a recording .ts file (hd h264 @13 Mb/s), from myvideos

play ok, Gpu load 50/60% gpu memory 860

pressed x , clik on the same video

play ok , GPU load 100% gp u memory 1100

pressed x , click on the same video

play started ok, GPU load 100% gpu memory 1370

then freeze while playing ...needed to kill mp



thank you

Is this V35 ?
https://forum.team-mediaportal.com/threads/madvr-support-in-mp1.133972/page-23#post-1181539

 

[kenwonders]

V33 Full installer in first post
I hope it will solve the crash on stop/zap channel from different TVCard.

Sorry not for me

I started MP, changed between BBC1HD and Quest repeatedly. After about 7-8 changes, the screen stayed in top corner and MP reported a message 'unable to play ts9.0' (can't remember number). After confirming the message it returned to MP guide, I started BBC1HD which worked, but on flicking to Quest MP returned to guide with the revolving whatsit and needed killing with task manager. Logs attached.

What did you do on ZAP channel change ?
I mean, can you explain me the step by step
Did you use context menu and TVGuide and select the channel ?
Maybe some screenshot (F11 key) is welcome, just to be sure that i'm doing the same.

Hey Sebastii, keep it up! Your persistence is hugely appreciated

To change channel, I selected the 'Guide' button on my MCE remote, bringing up the full sceen guide with windowed TV. I then scroll to the other channel and hit enter on the remote.

I can see some other stuff here so I'll check out the newer build. Also, does anyone here know the good/bad about flush or flush and wait in madVR windowed options?

 

[kenwonders]

Ok v35 still not there. The first failure identical to the previous v33, but unlike v34 it returned to the guide after the 'unable to play' error. When selecting a channel I got a madVR crash and then a full MP crash straight afterwards. Logs attached.

Just found this: http://forum.kodi.tv/showthread.php?tid=259188 Kodi guide to madVR setup, I'll run through it in case there are similar requirements.

 

[Sebastiii]

You mean that you have zap / zap right, will look the log
I'm sure it's because memory are not freed between zap.

 

[mrmojo666]

i've tried to start a recording .ts file (hd h264 @13 Mb/s), from myvideos

play ok, Gpu load 50/60% gpu memory 860

pressed x , clik on the same video

play ok , GPU load 100% gp u memory 1100

pressed x , click on the same video

play started ok, GPU load 100% gpu memory 1370

then freeze while playing ...needed to kill mp



thank you

Is this V35 ?
https://forum.team-mediaportal.com/threads/madvr-support-in-mp1.133972/page-23#post-1181539

sorry i missed v35 build

i repeated test.

this time gpu memory seems not growing much after 8/10 loops

gpu utilization was around 60% for the firsts 4 loops then always 100%

but in the end MP crashed (lasted more than v34) windows said mp crashed, but it couldn't kill by itself. I had to kiil Mp from task manager

here logs

thank you

 

[kenwonders]

You mean that you have zap / zap right, will look the log
I'm sure it's because memory are not freed between zap.

You could be right there, it's never happened on the first few zaps.

For another test to see if it was just about time rather than a leak, I waited 10 seconds between zaps, and the problem still occurred. Strangely this time the next attempt to play worked, followed by an error on the next zap. Back at the guide, I selected a channel and it worked, in fact it's still working a few zaps later.

So whatever happened in the middle of my test, the resources must have been freed so that I could start the leaking all over again. No idea if the difference is the speed of zapping!
EDIT: I should start looking at GPU stats. I think mrmojo666 is describing the same thing pretty much.

 

[Sebastiii]

So the next step test, would be to stop the TV after 6 or 8 zap (wait 10 or 20s) and try again and stop/wait etc.
It will confirm that it's really an issue with memory not freed.

When i register madVR[debug].ax, we can see that on zap the graph is not destroyed when zapping from tuner to tuner. When doing the stop, after few second the madVR instance is freed (because Garbage Collector do his job).

When talking with madshi, he tell me that madVR destroye his instance when all related COM object are release and the counter goes to 0. But with .NET, the release COM object are done async and memory is freed by garbage collector. So right now i don't know if we can do another way lol

Maybe @arion_p can have an idea ?

 

[daWooky]

hallo guys,
ts. loop play test like ya wrote in post #221outcome d3d error screenshot
no stop bug so far and file playback with my normal test files madvr memory usage seems ok
also tested some zapzap (dvb-s dual) with memory eat up after i switch to the second tuner -blue line in gpuz pic

btw quick onlinevideo try- on select play, mepo vanish silently

but anyway big thx as always seb

 

[kenwonders]

So the next step test, would be to stop the TV after 6 or 8 zap (wait 10 or 20s) and try again and stop/wait etc.
It will confirm that it's really an issue with memory not freed.

When i register madVR[debug].ax, we can see that on zap the graph is not destroyed when zapping from tuner to tuner. When doing the stop, after few second the madVR instance is freed (because Garbage Collector do his job).

When talking with madshi, he tell me that madVR destroye his instance when all related COM object are release and the counter goes to 0. But with .NET, the release COM object are done async and memory is freed by garbage collector. So right now i don't know if we can do another way lol

Maybe @arion_p can have an idea ?

I'm sure i did some dirty hack a few years back with something like GC.Collect() Or failing that a huge MP pause that the user will think is a HD spinning up or something.

If I stop the TV every few zaps, it is not going bad.

 

[daWooky]

So the next step test, would be to stop the TV after 6 or 8 zap (wait 10 or 20s) and try again and stop/wait etc.
It will confirm that it's really an issue with memory not freed.

tried that

first lots off zap (autozap still works ) , stop it and wait some time then enable tv again, same memory eat up happend like switching tuners or .ts playback