Call for tester for 1.4.0 features and fixes (1 Viewer)

[edterbak]

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?

LOL, yeah. Found her through the internet Ofcourse this is a typical dutch mistake. Direct translation... Ghehehe.. I should know better though

 

[Scythe42]

@riksmith: we deal with the stuff you can reproduce later. No need to hurry. Your HTPC requires some special attention anyway from me for other related issues.

New build is coming up in a few minutes. I now changed the WM_DISPLAYCHANGE to deactivate MP when the resolution doesn't match the D3D setup anymore and restore it once it is back to what it was.

This is safer than playing with D3D resets as we are not supporting a resolution change anyway.

Here how it looks on my dev System (only quoting relevant lines from the logs):

MP is up and running on Basic Home (Fullscreen start in 1920x1080 on Titan /w Splashscreen)

2012-12-17 22:28:45.408400 [Debug][MediaPortal(1)]: WindowManager: unroute to MediaPortal.Dialogs.GUIDialogNotify:2016->WindowPlugins.home.GUIBasicHome:35

I turn off the display or receiver. Both are doing the same on mine beside some different ACPI events that are not logged here.

2012-12-17 22:28:50.540800 [Debug][MediaPortal(1)]: Main: WM_DISPLAYCHANGE
2012-12-17 22:28:50.540800 [Info.][MediaPortal(1)]: Main: Resolution changed to 1920x1200x32
2012-12-17 22:28:50.556400 [Info.][MediaPortal(1)]: Main: Resolution does not match current presentation parameters

We got the WM_DISPLAYCHANGE message and verify it against the resolution in our current presentation parameters. Most of you guys probably get 1024x768x32.

As the resolutions don't match, we request a minimization when windows completed the change. This change will result in a WM_GETMINMAXINFO message.

2012-12-17 22:28:50.556400 [Debug][MediaPortal(1)]: Main: WM_GETMINMAXINFO
2012-12-17 22:28:50.556400 [Info.][MediaPortal(1)]: D3D: Minimizing to tray

Got the message and minimizing ourselves to the tray as it would be a black screen anyway.

2012-12-17 22:28:50.665600 [Debug][MediaPortal(1)]: Main: WM_ACTIVATE
2012-12-17 22:28:50.665600 [Info.][MediaPortal(1)]: Main: Deactivation Request Received
2012-12-17 22:28:50.852800 [Debug][MediaPortal(1)]: D3D: OnLostFocus()

And now we are in the tray. In fact MP triggered this message itself and does nothing on it. This means, windows likes what we are doing.

2012-12-17 22:28:50.868400 [Debug][MediaPortal(1)]: Main: WM_DEVICECHANGE (Event: 7)
2012-12-17 22:28:50.868400 [Debug][MediaPortal(1)]: Main: A device has been added or removed from the system.
2012-12-17 22:28:50.868400 [Debug][MediaPortal(1)]: Main: WM_DEVICECHANGE (Event: 7)
2012-12-17 22:28:50.868400 [Debug][MediaPortal(1)]: Main: A device has been added or removed from the system.

Some other stuff is happening. We don't care for it. If you also see a WM_DEVICECHANGE event in your logs it means that your system properly supports HDMI hot plugging. This means your system is fully compliant with the latest ACPI specs and conflicting legacy stuff is turned off. You did well, configuring your BIOS/EFI.

I turn the receiver back on a few seconds later. Let's see if it works:

2012-12-17 22:28:55.985200 [Debug][MediaPortal(1)]: Main: WM_DISPLAYCHANGE
2012-12-17 22:28:55.985200 [Info.][MediaPortal(1)]: Main: Resolution changed to 1920x1080x32
2012-12-17 22:28:55.985200 [Info.][MediaPortal(1)]: Main: Resolution restored to current presentation parameters

Other way around just happend. Old resolution is back, so this time we request a restoration from the tray.

2012-12-17 22:28:55.985200 [Debug][MediaPortal(1)]: Main: WM_DEVICECHANGE (Event: 7)
2012-12-17 22:28:55.985200 [Debug][MediaPortal(1)]: Main: A device has been added or removed from the system.
2012-12-17 22:28:56.016400 [Debug][MediaPortal(1)]: Main: WM_DEVICECHANGE (Event: 7)
2012-12-17 22:28:56.016400 [Debug][MediaPortal(1)]: Main: A device has been added or removed from the system.

Hot plug stuff we don't care for. Just logging it for debugging reasons.

2012-12-17 22:28:56.016400 [Debug][MediaPortal(1)]: Main: WM_GETMINMAXINFO
2012-12-17 22:28:56.016400 [Info.][MediaPortal(1)]: D3D: Restoring from tray

And when windows completed the change, we again get a WM_GETMINMAXINFO. And as we requested a tray restoration on the next WM_GETMINMAXINFO it gets executed now.

2012-12-17 22:28:56.219200 [Debug][MediaPortal(1)]: Main: WM_ACTIVATE
2012-12-17 22:28:56.219200 [Info.][MediaPortal(1)]: Main: Activation Request Received
2012-12-17 22:28:56.219200 [Debug][MediaPortal(1)]: D3D: OnGotFocus()

And we are back from the tray. In fact MP triggered this message itself and does nothing on it. This means, windows likes what we are doing.

PS: Yeah, this will look different if we go into suspend/hibernation mode in between or right away. But we deal with that scenario after this one is sorted out. Baby steps.

 

[Scythe42]

New build is up.

If you have a hanging MP during DirectX setup just disable the full-screen splash-screen. The way it is currently implemented conflicts with a proper D3D full-screen. Will work on that later with the guys who can reproduce this. Sadly I can't.

 

[edterbak]

And here are the results:

Disabled yami >> crash after turn on.

anything you would like me to do/test?

 

[cubii]

Test:
Mp started normally, after switching off receiver and on again, there was that black screen with mouse.., but after pressing win-key, i was back at the desktop and could restore mp with the try application manually (mp was successfully minimized, but not automatically restored)
Go on with your good work!

 

[Scythe42]

And here are the results:?

Let's take a look at the logs. Looks like you did it during playback of a movie, right?

Movie Player has not been adjusted yet in this fix. Just test with the GUI for now, please.

I also see that you always get 1920x1080x32. A case that is not yet handled. Let's see if this only happens during playback or also in the GUI.

Also you got a WM_DISPLAYCHANGE message during setup. Will filter that one out as nothing should be done at this time.

 

[Scythe42]

Mp started normally, after switching off receiver and on again, there was that black screen with mouse.., but after pressing win-key, i was back at the desktop and could restore mp with the try application manually (mp was successfully minimized, but not automatically restored)Go on with your good work!

Thanks for testing!

Let's see what your logs tell me. Hmmm. Now WM_DISPLAYCHANGE messages at all. Also I see a call to "D3D: CreateGraphicsSample()". Looks to me, like not all files were replaced. Especially MediaPortal.exe. I made some changes to a few log messages and this line isn't anywhere in the current test build.

Can you please test with the latest Build (#4) from the first thread again?

 

[edterbak]

Let's take a look at the logs. Looks like you did it during playback of a movie, right?

Movie Player has not been adjusted yet in this fix. Just test with the GUI for now, please.

I also see that you always get 1920x1080x32. A case that is not yet handled. Let's see if this only happens during playback or also in the GUI.

Also you got a WM_DISPLAYCHANGE message during setup. Will filter that one out as nothing should be done at this time.

Yes, it was during playback. Sorry.
Did the same thing just in GUI now.
Start
Turn off Yama
Turn on again.
BLack screen. full screen
Back to desktop and MP is gone. Not in tray atleast.
Went to task manager to kill MP.exe and logs started to be created. Attached.

as to the 1920x1080 thingy. I might have been messing around a bit with the fallback resolutions in the registry... Still the remains of my tinkering I guess. Dont remember exactly how to undo this right now. Need to search for that, if you need me to.

 

[Scythe42]

Thanks. Same behaviour. Reported resolution by Windows is the same, even though Windows claimed that it changed.

Info is coming from the GPU driver for what ever "compability reason". Probably just reporting a different refresh rate maybe, that WM_DISPLAYCHANGE does not provide to an application.

Or simply switching to another resolution but lying to Windows that it is the same in this hot-plugging scenario.

If the resolution didn't change at all, MP would be able to render. So the driver must be lying! And a refresh-rate change would be very strange.

Will support that one with the next build... Just need to think a bit how I best implement it.

For testing: If you just see the black screen try hitting the Windows key to force a jump to the Desktop. MP should minimize itself to the tray. (the black screen is the active MP). When you then try to restore it, do you see the GUI again? Just want to make sure D3D is still working.

 

[Scythe42]

Oh, have another idea:

Did you include some registry fix that windows always reports the same resolution because of the HDMI issue? That could be the cause for the "lying" as you are overriding what the driver tells Windows with this key.

In fact you are forcing Windows to always report this resolution, no matter what!

You know, these PrimSurfSize.cx, PrimSurfSize.cy, ActiveSize.cx, ActiveSize.cy settings under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration.