Call for tester for 1.4.0 features and fixes (3 Viewers)

[doveman]

In simple terms: we cannot render a 1920x1080 skin on a 1024x768 full screen. 1024x768 is what your GPU/Driver combo jumps to when it doesn't see any display. That's perfectly fine.

This info is VERY helpful!

A simple: If resolution is smaller than skin ignore display resolution change and minimize yourself to tray. If the next resolution change comes in with the old resolution then come back from tray. That should work in general, as I am not forcing MP to obey any resolution changes, which I tried. Worked for me as my GPU jumps to the maximum resolution it supports (1920x1200)

Hi Scythe

Reading this reminded me that I run catavolt's PVHD 1080 skin on my 1280x720 TV and it scales fine (see our brief discussion on this page https://forum.team-mediaportal.com/threads/purevisionhd-16-9.28714/page-194 ). I imagine it would scale to the 1024x576 resolution I was running my brother's HTPC at with a SD CRT TV as well but I haven't got round to trying that yet.

So anyway, I hope you're not planning to change MP so that I will no longer be able to use catavolt's skin on my TV.

 

[Scythe42]

No change in this area. This will work as before.

 

[riksmith]

The last changes (custom build based on your branch) behave very badly on my HTPC . I managed to get MP started 1 out of 20 times. The rest of the times it hangs at initializing directx. Also something in resolution is screwed up in some tries, the text is not in the center of the screen but on the bottom right edge. Logs attached, the bak file is the only successful start. On my DEV pc it is starting normally.

 

[FreakyJ]

Regarding RDP/VNC and similar Software:

After some try and errors and googling I conclude that it is impossible to see a real D3D fullscreen over RDP sessions.

Remember that MP didn't "live" in a real full screen before. It was always a borderless window in screen dimensions. I'll add an option for that mode.

First of all thanks for all your work, I know moaning that things don't work is easier than the actual fixing
Is it possible to detect a RDP session and than switch automatically to "borderless fullscreen window" and after the session back to real fullscreen?
Maybe i should explain why this RDP stuff is so important for me:

1) It is easier for me to make some adjustments on my HTPC via RDP, because connecting a mouse + keyboard isn't that comfortable, eypecially if you have to sit in front of a big screen and the cables are to short to sit on the couch
2) My dad uses sometimes the RDP session on his HTPC to program some recordings, because he is traveling much (MpExtended/WebmediaPortal has no search engine for EPG yet^^)

 

[Scythe42]

Yes, detecting RDP sessions should be possible over System.Windows.Forms.SystemInformation.TerminalServerSession

 

[Scythe42]

The last changes (custom build based on your branch) behave very badly on my HTPC . I managed to get MP started 1 out of 20 times. The rest of the times it hangs at initializing directx. Also something in resolution is screwed up in some tries, the text is not in the center of the screen but on the bottom right edge. Logs attached, the bak file is the only successful start. On my DEV pc it is starting normally.

If you use a custom build can you try to remove the SplashScreen.Run() line for a quick test and check if it still has problems?

 

[edterbak]

Ah.. Damit.. I want to test. The wife is busy behind the tv... Is it possible to do the test through remote desktop? I guess not.
Ill just set it up and wait till she's gone to sleep.

 

[tourettes]

The wife is busy behind the tv...

A wife who sorts out the cabling mess while you are watching tv? Where did you find a woman like that?

 

[riksmith]

Windowed mode is not working either. See log.

The last changes (custom build based on your branch) behave very badly on my HTPC . I managed to get MP started 1 out of 20 times. The rest of the times it hangs at initializing directx. Also something in resolution is screwed up in some tries, the text is not in the center of the screen but on the bottom right edge. Logs attached, the bak file is the only successful start. On my DEV pc it is starting normally.

If you use a custom build can you try to remove the SplashScreen.Run() line for a quick test and check if it still has problems?

I can tomorrow. Busy with using the working version of MP now

 

[edterbak]

Ive got an hour or two now.

Here are my findings:
Start MP 1.3b
Video starts normally
Turn off / on Yamaha rxv 661 (HTPC >> Yami >> TV)
Black screen + after a minute a crash of non responsive MP.
Attached are the logs.

Specs are hardwarewise up-to-date[DOUBLEPOST=1355780472][/DOUBLEPOST]

The last changes (custom build based on your branch) behave very badly on my HTPC . I managed to get MP started 1 out of 20 times. The rest of the times it hangs at initializing directx. Also something in resolution is screwed up in some tries, the text is not in the center of the screen but on the bottom right edge. Logs attached, the bak file is the only successful start. On my DEV pc it is starting normally.

If you use a custom build can you try to remove the SplashScreen.Run() line for a quick test and check if it still has problems?

Yeah, I see the same problem with the splash screen. I just disabled it from config.exe and now it starts up even faster.