MP2 - Spring'16 Return from sleep - display is messed up (1 Viewer)

[Jay_UK]

Hi there,

I am starting to get back in to Mepo (thought I'd try MP2)

I recently installed the "latest" release (Spring) but encountered one or two issues (here's one of them)

When returning from sleep, occasionally MP2 is not displayed correctly, it is squashed in to the top left corner of the screen (sounds like an old MP1 issue :O ), where it's about 2" wide by 6" tall - it's still responding to commands, just squashed!

My system consists of:

Windows 10
Intel i5
Yamaha AVR Amp
Samsung TV
Pulse Eight CEC (I do not use the CEC control in MP2, it is too limited at present)

Everything connected by HDMI, running 1080p. The HTPC wakes the AVR and TV via CEC

Please see the attached log

J.

 

[Lehmden]

It's a well known HDMI issue... Windows is changing the display resolution while the AVR is turned on or off. And this is not done in a clean manner, so lots of programs have issues with. E.G. Chrome, Photoshop or Firefox also have issues on this scenario...
You can easily prevent this by closing MP2 before the AVR is turned on or off. As MP2 is starting that fast (average is less than one second) it's no big deal...

Edit... It looks as if you are not using the recent build... You have the old icons on your desktop and you have tried Titanium, which isn't available any longer...

 

[CyberSimian]

When returning from sleep, occasionally MP2 is not displayed correctly, it is squashed in to the top left corner of the screen (sounds like an old MP1 issue)

When I used WMC with my previous LCD TV (a Toshiba dating from 2006), I also had problems with unwanted screen-resolution changes. I eventually found a solution that partly used a WMC-specific action, and partly used a setting on the graphics card. However, I no longer had problems when I got a new Sony TV last year.

The difference between the Toshiba and the Sony is their behaviour when I switch them to standby. Both TVs offer a power consumption of less than 1 watt in standby, so I always use that (I don't switch the TV off at the mains socket). But the Toshiba breaks the HDMI connection when switched to standby, whereas the Sony maintains the HDMI connection when switched to standby. Consequently, whenever the HTPC wakes up (e.g. to perform an unattended recording), the Sony TV is always available for Windows to query in order to determine the display's capabilities; hence no unwanted resolution change.

Does your Samsung maintain the HDMI connection when in standby? If it does, does it also support the "Audio Return Channel" (ARC). If so, you could try this connection:

HTPC -> TV -> AV amplifier

in place of this connection:

HTPC -> AV amplifier -> TV

My Sony TV has four HDMI sockets, but only one supports ARC (that is the one that you connect to the AV amplifier). I have never used this setup myself (my amplifier is analogue!), so I don't know whether the AV amplifier also needs to support ARC.

-- from CyberSimian in the UK

 

[Stéphane Lenclud]

I have had a similar issue at some point on Windows 10 here is my solution:

Due to the various side effects a TV power cycle was having on my apps and desktop I eventually realized that turning off and on the TV caused Windows 10 to trigger a change of resolution and/or font size/DPI.

After some research I forced the same DPI for all my displays, virtual and physical by doing the following:

- Go in "Control Panel\Appearance and Personalization\Display".
- Click on "set custom scaling level".
- Set it to whatever works for you. 100% was working fine for me.

Here is a very interesting link regarding that resolution change issue when disconnecting a display, read through the various solutions suggested as one of them may work for you:
http://superuser.com/questions/2670...-the-monitor-display-channel-is-turned-off-sw

Here is a link on how to adjust scaling:
http://www.tenforums.com/tutorials/5990-dpi-scaling-level-displays-change-windows-10-a.html

See:
http://answers.microsoft.com/en-us/...ns-reset/b6a21478-3d2c-4f86-8807-c7b1e6b2fc86

 

[Jay_UK]

Hi guys

Thanks for all the responses, I knew what the cause was (HDMI negotiation/screen resolution change), but I had hoped MP2 would have handled that (it used to be a problem for MP1).

I have worked around the issue by delaying the startup of MP2 by a few seconds.

Thanks,

J.

ps -Lehmden, I was testing/trying different versions of MP2 to see if any gave me different results for the other "issues" I was having. Now back running Spring (and newer) versions

 

[Jay_UK]

Hi again,

Well I thought I had worked around the issue, but I get the problem when waking from sleep, so obviously delaying the startup of MP2 isn't going to work (unless I start killing it off and relaunching each time).

I have tried the reg hacks of manually setting the primary resolution for the various display types - no joy

I am now using the latest weekly build, but still have the issue. without me going through the code, can anyone remember what the "fix" was that was applied to MP1 to solve the problem?

Defining a custom scale of 100% hasn't helped either

My TV/amp does support ARC, but the ARC/CEC setup is a bit hit and miss and I'd rather not touch it (CEC is working nicely at the moment - they seem to be linked on my setup)

I'm still continuing to find a "work around"

J.

ps - It looks like this was the fix for MP1: https://forum.team-mediaportal.com/...ug-please-help-me-im-about-to-give-up.122073/

 

[morpheus_xx]

There are a lot of quite uncommon errors in your logfile, they should be checked separately.

Regarding to screen resolution changes I can read from log, that the dimensions where changed multiple times. And they were handled by the MainForm:

[2016-05-28 02:00:52,067] [10988237] [Main ] [INFO ] - SkinEngine MainForm: Display changed to 1024x768@32.
[2016-05-28 02:00:52,067] [10988238] [Main ] [WARN ] - GraphicsDevice: Resetting DX device...
[2016-05-28 02:00:52,098] [10988269] [Main ] [WARN ] - GraphicsDevice: ContentManager.TotalAllocationSize = 22, should be 0!
[2016-05-28 02:00:52,193] [10988363] [DX Render] [WARN ] - Cannot open texture: fanart_overlay.png
[2016-05-28 02:00:52,503] [10988673] [Main ] [WARN ] - GraphicsDevice: Device successfully reset
[2016-05-28 02:00:52,905] [10989075] [DX Render] [WARN ] - CommandBaseMarkupExtension: Could not find method, could not execute command ({Command Source=MediaPortal.UiComponents.BlueVision.Models.HomeMenuModel,Path=OnScreenShow})
[2016-05-28 02:00:53,306] [10989476] [Main ] [INFO ] - SkinEngine MainForm: Display changed to 1920x1080@32.
[2016-05-28 02:00:53,306] [10989477] [Main ] [WARN ] - GraphicsDevice: Resetting DX device...
[2016-05-28 02:00:53,396] [10989566] [Main ] [WARN ] - GraphicsDevice: ContentManager.TotalAllocationSize = 22, should be 0!
[2016-05-28 02:00:53,443] [10989613] [DX Render] [WARN ] - Cannot open texture: fanart_overlay.png
[2016-05-28 02:00:53,695] [10989866] [Main ] [WARN ] - GraphicsDevice: Device successfully reset
[2016-05-28 02:00:53,696] [10989867] [Main ] [INFO ] - SkinEngine MainForm: Display changed to 1024x768@32.
[2016-05-28 02:00:53,696] [10989867] [Main ] [WARN ] - GraphicsDevice: Resetting DX device...
[2016-05-28 02:00:53,954] [10990124] [Main ] [WARN ] - GraphicsDevice: ContentManager.TotalAllocationSize = 22, should be 0!
[2016-05-28 02:00:53,962] [10990132] [Main ] [WARN ] - GraphicsDevice: Device successfully reset
[2016-05-28 02:00:54,418] [10990588] [DX Render] [WARN ] - CommandBaseMarkupExtension: Could not find method, could not execute command ({Command Source=MediaPortal.UiComponents.BlueVision.Models.HomeMenuModel,Path=OnScreenShow})
[2016-05-28 02:00:55,122] [10991292] [Main ] [INFO ] - SkinEngine MainForm: Display changed to 1920x1080@32.
[2016-05-28 02:00:55,125] [10991295] [Main ] [WARN ] - GraphicsDevice: Resetting DX device...
[2016-05-28 02:00:55,190] [10991360] [Main ] [WARN ] - GraphicsDevice: ContentManager.TotalAllocationSize = 45, should be 0!
[2016-05-28 02:00:55,358] [10991528] [DX Render] [WARN ] - Cannot open texture: fanart_overlay.png
[2016-05-28 02:00:55,700] [10991870] [Main ] [WARN ] - GraphicsDevice: Device successfully reset
[2016-05-28 02:00:55,701] [10991871] [Main ] [INFO ] - SkinEngine MainForm: Display changed refresh rate, size remained 1920x1080@32.

So from this point of view it looks correct.

 

[Jay_UK]

Hi there,

To try and help (not sure it will be much use), I have deleted my log files and tried the following:

1) A full reboot, where the AMP and TV were off, on the HTPC rebooting it automatically turned on these devices during startup (using PulseEight CEC tray app) - This is the "reboot" log file. Everything seemed to work fine and MP2 displayed correctly.

2) I then put the HTPC to sleep (it automatically turned off the AMP and TV), let it sleep for a few minutes and then woke it (it automatically turned on the AMP and TV) - This is the other logfile. This logfile detects a 1600x1200@32 resolution and then a change to 1920x1080@32, so as you have said MP2 seems to detect the change, but MP2 is not resized/displayed correctly - please see the attached screen grab.

Many thanks,

J.

 

[morpheus_xx]

Thanks. I have an idea what we could do when a resize change is detected. Currently we "only" recreate the DX device, but I'd like to try a manual resize of the MainForm first. Although this should happen automatically, maybe this helps.

I'll create a test build and let you know

 

[HTPCSourcer]

@Sebastiii played around this when we had the issue on MP1 last year and introduced some code to manage the different conditions. Mybe it's of interest.