Scythe42's fixes for 1.4.0 (7 Viewers)

Status
Not open for further replies.

Scythe42

Retired Team Member
  • Premium Supporter
  • June 20, 2009
    2,065
    2,703
    51
    Berlin
    Home Country
    Germany Germany
    Code:
    [2013-04-24 19:41:49,631] [Log	] [MPMain  ] [DEBUG] - D3D: InitializeDevice()
    [2013-04-24 19:41:49,639] [Log	] [MPMain  ] [ERROR] - Exception: Fehler in der Anwendung.
    -2005530518 (D3DERR_NOTAVAILABLE)
      bei Microsoft.DirectX.Direct3D.Manager.GetDeviceCaps(Int32 adapter, DeviceType deviceType)
      bei MediaPortal.D3D.InitializeDevice()
      bei MediaPortal.D3D.Init()
      bei MediaPortalApp.Main(String[] args)  Message: Fehler in der Anwendung.  Site  : Microsoft.DirectX.Direct3D.Caps GetDeviceCaps(Int32, Microsoft.DirectX.Direct3D.DeviceType)  Source : Microsoft.DirectX.Direct3D  Stack Trace:	bei Microsoft.DirectX.Direct3D.Manager.GetDeviceCaps(Int32 adapter, DeviceType deviceType)
      bei MediaPortal.D3D.InitializeDevice()
      bei MediaPortal.D3D.Init()
      bei MediaPortalApp.Main(String[] args)
    For whatever reasons, Managed DirectX could not get the capabilities of the device. Can you reproduce this?

    At the moment we tried to get the capabilities, no D3D hardware device was present. Will catch this error for a proper error message.

    But wonder why on your system....
     
    Last edited:

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    It's that commit that break RDS support :
    SHA-1: 8e8c14eb500205cf8ef7c1edf709f8c353bc89b7
    * added debug logging of display and adapter information
    That happens during startup only. Can I please have logs when you try to start MP over an RDP sessions. And please not will 10 different tests inside the logs like the last one. Only reproduce the issue with as few steps as possible.

    I don't know what to say it's maybe random them :(

    I just go to my HTPC with your build on it and i have see something strange :
    HTPC was in S3 from yesterday and the wakeup (21H55) didn't work well.
    Log attached + screenshot :)
     

    Attachments

    • Resume_from_S3_small_windows.jpg
      Resume_from_S3_small_windows.jpg
      218.7 KB

    FreakyJ

    Retired Team Member
  • Premium Supporter
  • July 25, 2010
    4,024
    1,420
    Home Country
    Germany Germany
    Can you reproduce this?
    As you see in the logs it worked as I started MP by hand. I restarted the PC now and MP came up without this error, so the short answer is: No I can't reproduce it on demand, sorry :(
    But hopefully the logs help you to find a way that this can't happen again :) So far I'm pretty happy with your work (y)
     

    Scythe42

    Retired Team Member
  • Premium Supporter
  • June 20, 2009
    2,065
    2,703
    51
    Berlin
    Home Country
    Germany Germany
    Hi!
    Unfortunately the issue, i've reported in #92 doesn't seems to be fixed here! Log and Screenshot attached!

    - System Specs used : PC
    - How many displays : 2
    - What resolution does each display use : LG 42LM660S/1920*1080 - Samsung 226BW/1152*864
    - More than one GPU used : NO
    - How are displays connected : LG -> HDMI - Samsung -> DVI
    - How are they positioned : Screenshot
    - Which one is the primary one : Screenshot
    - On which do you start MP : On Display #2 (LG 42LM660S)
    - Where is the taskkbar positioned of Windows : On Display #1
    - Screenshot of the whole windows desktop when it is wrong. Not just MP, that does not elp me.
    - Skin Used : Default wide

    Best regards
    Helios
    Let's check what MP got:
    Code:
    [2013-04-23 08:21:58,103] [Log	] [MPMain  ] [DEBUG] - Display: \\.\DISPLAY1 - IsPrimary: True - BitsPerPixel: 32 - Bounds: 1152x864 @ 0,0 - WorkingArea: 1152x824 @ 0,0
    [2013-04-23 08:21:58,103] [Log	] [MPMain  ] [DEBUG] - Display: \\.\DISPLAY2 - IsPrimary: False - BitsPerPixel: 32 - Bounds: 1920x1080 @ -1920,0 - WorkingArea: 1920x1080 @ -1920,0
    [2013-04-23 08:21:58,200] [Log	] [MPMain  ] [DEBUG] - Adapter #0: Intel(R) HD Graphics - Driver: igdumd32.dll (9.17.10.3062) - DeviceName: \\.\DISPLAY1
    [2013-04-23 08:21:58,200] [Log	] [MPMain  ] [DEBUG] - Adapter #1: Intel(R) HD Graphics - Driver: igdumd32.dll (9.17.10.3062) - DeviceName: \\.\DISPLAY2

    So we got two displays here.
    Primary with 1162x864 and a secondary 1920x1080 that is positioned to the left of the primary. Matches your description and what I see from the screenshot.

    Code:
    [2013-04-23 08:21:58,350] [Log	] [SplashScreen] [INFO ] - SplashScreen: Splash screen is using screen: \\.\DISPLAY2 (Position: -1920,0 Dimensions: 1920x1080)
    [2013-04-23 08:21:58,369] [Log	] [MPMain   ] [INFO ] - Main: MP is using screen: \\.\DISPLAY2 (Position: -1920,0 Dimensions: 1920x1080)
    Both Splashscreen and MP itself decided on the correct screen. Matches your screensshot as we on the right screen.

    Then we have endless repetitions of WM_GETMINMAXINFO probably because the system is not yet ready, meaning the form is not displayed yet. Takes several seconds. Probably waiting for the TV Server or something.

    Log file gets hammered with over 40K lines of entries, where Windows is waiting for us.

    MP keeps battling with Windows to set the size to 1920x1080, but Windows refuses.

    Hmmm... I think I have an idea... 4:3 primary display vs. 16:9 display vs. 16:9 skin.
     

    Scythe42

    Retired Team Member
  • Premium Supporter
  • June 20, 2009
    2,065
    2,703
    51
    Berlin
    Home Country
    Germany Germany
    [I just go to my HTPC with your build on it and i have see something strange :
    HTPC was in S3 from yesterday and the wakeup (21H55) didn't work well.
    Log attached + screenshot :)
    Can you compile my branch and test again please? That is a clear regression.

    Can you reproduce this?
    As you see in the logs it worked as I started MP by hand. I restarted the PC now and MP came up without this error, so the short answer is: No I can't reproduce it on demand, sorry :(
    But hopefully the logs help you to find a way that this can't happen again :) So far I'm pretty happy with your work (y)
    I'll add a re-try loop. Looks like the GPU driver when MP was autostarted was not yet fully up and running. Probably some display driver software was autostarted setting D3D temporarily into a softwar only mode for a couple of ms.

    Question is after what time should I assume that we do not have a hardware device available? What do you guys think is a reasonable timeout?
     

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    [I just go to my HTPC with your build on it and i have see something strange :
    HTPC was in S3 from yesterday and the wakeup (21H55) didn't work well.
    Log attached + screenshot :)
    Can you compile my branch and test again please? That is a clear regression.

    It seems to be related to screen selector but i'm not sure :)
    I will retry i have 2 install on htpc, my fork (based on you work) and your build sorry, i messed up both :)
     
    Last edited:

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    I just retry, this time it's fullscreen but mp is freezed. (need to kill it)
    Will retry tomorrow after the htpc goes to sleep by itsefl, maybe it will make a diff compared to this test :)
     
    Last edited:

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    hmmm sorry, i didn't see that you commit/push into your branch :unsure:
    I will retest with your last fix :)
    thanks.
     

    AtTimesPerplexed

    MP Donator
  • Premium Supporter
  • May 8, 2011
    127
    48
    Home Country
    New Zealand New Zealand
    - System Specs used : Core2Duo, Nvidia 9500GT
    - How many displays : 1
    - Skin Used : Any, Defaultwide in logs
    Start any video, press X so the video is a small preview window, then ALT-Enter. All text and thumbnails disappear.
    Wrong.jpg
    It should look like this,
    Correct.jpg.
    Changing to any other screen (homescreen, pictures etc) results in a mostly blank screen with just the preview window showing.
    Further switching between fullscreen/windowed doesn't fix the glitch.
    Using other skins results in MP hanging completely, or throwing an error box "Can't create D3D device".
     
    Last edited:

    swado

    New Member
    January 25, 2013
    3
    1
    37
    Engadine, New South Wales, Australia
    Home Country
    Australia Australia
    Just updated to latest build in first post, still having issue with it opening not fullscreen.

    Installed Update --> launched fine --> put to sleep --> woke up and its not full screen

    Appear mediaportal may have frozen, its not responding to any input in the halfscreen.
    tried a 2nd time with same results, 3rd and 4th attempt worked as it should.
     

    Attachments

    • display.jpg
      display.jpg
      300.5 KB
    Status
    Not open for further replies.

    Users who are viewing this thread

    Top Bottom