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

[Scythe42]

2012-12-15 23:43:33.246304 [Info.][MPMain(1)]: Main: MediaPortal v1.2.200.0 is starting up on Compatibilty Mode: Windows 7 [6.1.7600.0]
2012-12-15 23:43:33.247304 [Info.][MPMain(1)]: Build: 1.2.200.0
2012-12-15 23:43:33.248305 [Info.][MPMain(1)]: *******************************************
2012-12-15 23:43:33.248305 [Info.][MPMain(1)]: * WARNING, OS not officially supported    *
2012-12-15 23:43:33.248305 [Info.][MPMain(1)]: *******************************************
2012-12-15 23:43:33.249305 [Info.][MPMain(1)]: Main: Last install from WindowsUpdate is dated 2012-12-11 21:49:28
2012-12-15 23:43:33.249305 [Debug][MPMain(1)]: Disabling process window ghosting
2012-12-15 23:43:33.250305 [Info.][MPMain(1)]: Main: Using Directories:
2012-12-15 23:43:33.250305 [Info.][MPMain(1)]: Base - C:\Program Files (x86)\Team MediaPortal\MediaPortal
2012-12-15 23:43:33.250305 [Info.][MPMain(1)]: Log - C:\ProgramData\Team MediaPortal\MediaPortal\Log
2012-12-15 23:43:33.250305 [Info.][MPMain(1)]: Skin - C:\ProgramData\Team MediaPortal\MediaPortal\Skin
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Language - C:\ProgramData\Team MediaPortal\MediaPortal\Language
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Database - C:\ProgramData\Team MediaPortal\MediaPortal\Database
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Plugins - C:\Program Files (x86)\Team MediaPortal\MediaPortal\Plugins
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Thumbs - C:\ProgramData\Team MediaPortal\MediaPortal\Thumbs
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Cache - C:\ProgramData\Team MediaPortal\MediaPortal\Cache
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Weather - C:\ProgramData\Team MediaPortal\MediaPortal\skin\Default\Media\Weather
2012-12-15 23:43:33.251305 [Info.][MPMain(1)]: Config - C:\ProgramData\Team MediaPortal\MediaPortal
2012-12-15 23:43:33.252305 [Info.][MPMain(1)]: Main: Assembly creation time: 15.12.2012 21:04:37 (UTC)
2012-12-15 23:43:33.253305 [Warn.][MPMain(1)]: Main: MediaPortal is already running

Logs don't show anything beside that you tried to restart MP while another MP instance was already running and that didn't work (might be possible with the currently build).

Backup logs (from the start before) looks perfectly fine. Last entry is from 23:43:27. And 6 seconds later the new one with an attempted restart. There are about two minutes where nothing happend on Mediaportal at all. Then it was minimized to the tray.

Please try again without trying to restart MP on top of another instance.

 

[Scythe42]

Regarding the Black Screen in general:

I think the black screen is just a missing forced re-plaint as the content got lost. It isn't half-full screen is it? That would be proof that the issue is in fact gone and just needs some fine-tuning.

Just try hitting the Win Key to jump to the desktop and then double click on the minimize to tray icon of MP. Does this work?

 

[cubii]

Logs don't show anything beside that you tried to restart MP while another MP instance was already running and that didn't work (might be possible with the currently build).

what should i do else for testing? i just started mp and powered off the receiver, this results normally in the half fullscreen proplem

Backup logs (from the start before) looks perfectly fine. Last entry is from 23:43:27. And 6 seconds later the new one with an attempted restart. There are about two minutes where nothing happend on Mediaportal at all. Then it was minimized to the tray.

Please try again without trying to restart MP on top of another instance.

yeah, perhaps this happed because i had a black screen, went back to desktop and didn't saw mp open in the tasklist. so i thought it was closed and restarted it again...


And you are right! its not halffullscreen --> its a full black screen!

Problem nearly solved!

 

[FreakyJ]

thanks for the fast update!
It improved already alot, but some issues are still there, but small ones:
- mouse courser is not showing up (I think that is already on your list)
- various RDP problems (also on your list)
But I thought I will provide you with logs again, because you wrote that you added some more log messages Maybe that helps you to track down the issues better

In the rar you will find the logs like the last time, I think that was fine for you

EDIT:
In the first two test there was a DB error :/ I fixed it after that, sorry... but i think it had no impact except some log noise^^

 

[Scythe42]

New build is up. This should fix the black screen issue, where MP cannot render.

This was caused by the following fact: when you turn off your display/disconnect it, your GPU jumps into a different resolution (should be 1920x1200, but need to verify on a few GPUs).

In fullscreen mode D3D needs to be re-initialized to the new resolution or you won't see what it tries to render. Did no adjustment to windowed mode here as no one reported window mode related problems yet. So please check also if problems are there in windowed mode.

I chose a re-init because the resolution change could also come from a display change in general.

Please test again in regards to half/full screen & black screen (you only see the mouse cursor).

Provide logs even when it works, so I can see the behaviour of your system & GPU and what it reports!

 

[cubii]

Hi, tried it again:
After replacing the files, i started mp, but it stopped/hanged at initializing direct x. The logs are called direct-x...
After a restart of the pc, i tried it again, and mp started fully. But after shutting off and on of my receiver, an error occurred, mp crashed (second logfiles : MediaPortalLogs_16_12_12__23_35 , generated by watchdog)
Hope this helps!

 

[Scythe42]

Let's take a look at the logs:

DirectX One is unrelated. Have seen this once in a while with MP. From the logs the Window Manager simply couldn't activate a window and then hangs on this one. If this happens often it needs to be investigated.

Now the Crash Log:

We start in Fullscreen:
2012-12-16 23:31:22.945656 [Info.][MPMain(1)]: D3D: Client size: 1920x1080 - Screen: 1920x1080

You turned off your receiver:
2012-12-16 23:32:04.559603 [Debug][MPMain(1)]: Main: WM_DISPLAYCHANGE
2012-12-16 23:32:04.559603 [Info.][MPMain(1)]: Main: Resolution changed to 1024x768x32
2012-12-16 23:32:04.559603 [Debug][MPMain(1)]: D3D: UpdateResolution()
2012-12-16 23:32:04.561603 [Info.][MPMain(1)]: D3D: Client size: 1920x1080 - Screen: 1024x768
2012-12-16 23:32:04.562604 [Debug][MPMain(1)]: D3D: Fullscreen Presentation Parameter Back Buffer Size set to: 1024x768
2012-12-16 23:32:04.562604 [Info.][MPMain(1)]: GraphicContext: MP will render at 60 FPS, use animations = True
2012-12-16 23:32:04.562604 [Warn.][MPMain(1)]: Main: ***** OnDeviceLost *****

And then the D3D Device is lost. And cannot be re-created with the same parameters. And MP is stuck in a loop trying over and over again to setup the D3D device with parameters it doesn't support.

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)

I can simulate your setup by using hardcoded values and find a way that works best.

So we are already in fine tuning and testing on various GPUs!

Couple of more builds for compatibility tests with more people and the issue can be closed and the rest of the code can be adjusted to the new D3D code (see known issues).

 

[Scythe42]

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.

 

[Lightning303]

Hey,
so i just did some testing using your build 3.
My HTPC is connected via hdmi to my av receiver, and from there also via hdmi to my tv.
I did two test runs.
- Start MP, wait a bit, turn off avr (tv still on), wait a bit, turn avr back on
- Start MP, wait a bit, turn off tv (avr still on), wait a bit, turn tv back on

Both times i got the same result, a black screen. After a few seconds on black screen, mp crashed.
Hope this will help you.

 

[Scythe42]

Thanks a lot. Same behaviour as cubii.

2012-12-17 02:50:58.902547 [Debug][MPMain(1)]: Main: WM_DISPLAYCHANGE
2012-12-17 02:50:58.907547 [Info.][MPMain(1)]: Main: Resolution changed to 1024x768x32

Anyone with a different resolution? Just check your logs for instances of WM_DISPLAYCHANGE after MP starts (usually after the "BASS" lines).

But I think that's the common denominator: 1024x768. Everyone not having that problem probably has 1920x1080 (or greater....)

Will be handled correctly in the next build if i don't screw it up. And we take it form there.

The black screen indicates that there is NO half/full screen anymore. Only thing left is to help the D3D device through the various resolution changes without getting unrecoverable lost and taking MP down with it.

Afterwards the next scenario will include sleep/hibernation. But not for now guys. Let's just get the TV/Receiver On/Off sorted out and then we take it one step further. Once scenario at a time.

And again, thanks for helping making MP better! The issues is really really annoying.