[WiP] madVR support in MP1 (6 Viewers)

[GeYe]

Ok first test. Mp windowed, but desktop with 4k resolution. Channel changed initiated at 14:35 and completed at 14:36. madvr was with gpu queue size 6. Material was Deluxe Music SD Channel on TV.

High CPU Usuage comes from connection via VNC while doing screenshots. For me i dont't see a memory leak or problem with memory.

1: GPU Usage without MP
2: Pre Channel Change
3: Black Screen while channel change, also audio stopped temporaly
4: Channel Change

 

[Kotik]

Did you get any OSD flashing during ur tests?

Sent from my GT-I9205 using Tapatalk

 

[GeYe]

Next test: 4k Desktop fullscreen. Madvr GPU Queue Size 8.

14:56:01 TV stop clicked
14:56:45 TV stop done
14:57 Starting Series Full HD but shown @4k
15:56:00 Stop Series clicked
15:57:40 Stop Series done

Don't see OSD flickering in series today, but in TV is see OSD flickering with GPU Queue Size 6 and 8.
--- Post updated ---
Last Test: 4k Desktop fullscreen. Madvr GPU Queue Size 8.

16:30:40 Start 4k Series
16:59:18 Stop Series clicked
16:59:29 Stop Series done

My personal result: No limitation of GPU, neither GPU core nor GPU memory. But good I get a 4 GB model

And maybe one note: In logs you see 100% GPU Core, but i see no stuttering while watching the Full HD series. While SD and 4k material I wasn't in front of TV, but in Tests before i see no problem in dropped frames or so. Also the GPU clock can go till 1200 MHz and is only with 4k material near that.

 

[Kotik]

And maybe one note: In logs you see 100% GPU Core, but i see no stuttering while watching the Full HD series. While SD and 4k material I wasn't in front of TV, but in Tests before i see no problem in dropped frames or so. Also the GPU clock can go till 1200 MHz and is only with 4k material near that.

U can ignore this indicator cause it is % based on the CURRENT GPU clock, so on lower clocks it will report 100% while in reality the GPU has plenty more power to spend.

 

[Sebastiii]

Hey
I will push an update that i was getting when madVR stop rendering on LiveTV is we get like PES error etc. , madVR is waiting some rendering video side to have GUI working.
So i have added a workaround about it, if after 2s of video freeze, it trigger something to be able to get back GUI rendering.
Seems to works

 

[joecrow]

Is/could that be a fix for the long delay on stop seen with TVS and OLV? (for whatever reason it no longer seems to be happening with TV recently).

 

[cabala]

Hi Seb,

on my side, I have two major issues:

1) During 3D playback when I stop a movie, "MP" remains in 3D mode. I tried everything. The curious thing is that if I wait until the movie ends, MP returns to 2D mode so perfect ...
2) Sometimes, in MP Basic Home I miss the background image when I come back from another menu (Moving Pictures or TVS). Returning to the previous menu and coming back again to Basic Home, fixes the issue.

Testing with the last version (220), StreamedMP skin and AMD RX470 with the last Crimson driver.

Thanks for all!

 

[Sebastiii]

Is/could that be a fix for the long delay on stop seen with TVS and OLV? (for whatever reason it no longer seems to be happening with TV recently).

I don't think so it's another issue, i didn't run into that long pause on my side, so it can be a setting in madVR and/or in LAV too or really inside MP if it happen only on MP.

 

[Sebastiii]

Hi Seb,

on my side, I have two major issues:

1) During 3D playback when I stop a movie, "MP" remains in 3D mode. I tried everything. The curious thing is that if I wait until the movie ends, MP returns to 2D mode so perfect ...
2) Sometimes, in MP Basic Home I miss the background image when I come back from another menu (Moving Pictures or TVS). Returning to the previous menu and coming back again to Basic Home, fixes the issue.

Testing with the last version (220), StreamedMP skin and AMD RX470 with the last Crimson driver.

Thanks for all!

Hey
Can you share logs for both issue with time when it happen ?

So about :
1) if it stay on 3D then madVR seems not fully released and then lead to memory leak or something similar.
2) it comes from loadskin issue, sometimes the skin is not fully loaded and it can happen randomly and for now didn't find a way to fix that (it happen here near 0 but i already seen this and depend of the skin too)

 

[Sebastiii]

V221 in first post