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

[AtTimesPerplexed]

I have a problem with the progress bar in myvideos,TVseries etc (not TV) always being a solid line regardless of which skin I use.

There is a commit for "OSD always showing 100%", if I manually reverse that code and recompile the progress bar works again.
Have also tried with this threads 18a binaries in a VM with a fresh MP install and it has the same problem.

 

[hello_joe]

This happens for me also without Scythe's rework.

So that means we've got a missing .dll in 1.3 Final?

Or is this something that is installed when you have the appropriate hardware?

It is only required for the Floppy/FireDTV remote. You should not be distributing it. People copy it from the FireDTV software/driver package when needed.

 

[Holzi]

So maybe this is just a logging issue.

 

[HomeY]

So maybe this is just a logging issue.

Maybe this popped up because we switched to Log4Net?
Anyways, we got it in Mantis now, so we won't forget it again.

 

[Holzi]

I think so too.

 

[vuego]

Also having multiple displays connected on multiple adapters may also not work correctly. But that is a more exotic use case these days anyway that MP users using multiple GPUs at the same time and they each control displays on their own and MP gets switched between adapters all the time.

I'm using two GPUs since MediaPortal is using the wrong display for refresh rate. For example when playing a 50 fps video on the secondary monitor while the primary monitor is set to 60 Hz will cause mad stuttering since it will try to sync to 60 Hz. This is prevented when using multiple graphics cards. I got the tip from another MediaPortal user so there's probably more users in the same situation (granted still possibly exotic).
However I do not constantly move MediaPortal. I use a command line switch to start MediaPortal - /fullscreen /screen=1.

 

[azzuro]

@Scythe42 : tested on ION (Win7 32b) chipset
MP start correctly, no bug happen, really fast : switch Fullscren-Windowed

all slowdown/freeze MP is related to my Wifi network ... for acces to dummy Tvserveur on Workstation, because is not asyncrone (not a fix is available for this ?)

i push my log, normally with all plugins are disabled !

PS : Windowed mode (screen size) is based on Fullscreen size.

 

[HomeY]

Wanted to test this on my productive system, so upgraded HTPC, but unusable in combination with my current StreamedMP skin.
Switching to DW makes MP start up, so might be skin issue:
[hide]

[2013-04-14 12:19:51,968] [Error  ] [MPMain  ] [ERROR] - D3D: InitializeDeviceObjects - Exception: Error in the application.
-2147024882 (E_OUTOFMEMORY)
  at Microsoft.DirectX.Direct3D.Font..ctor(Device device, Font font)
  at MediaPortal.GUI.Library.GUIFont.InitializeDeviceObjects()
  at MediaPortal.GUI.Library.GUIFontManager.InitializeDeviceObjects()
  at MediaPortalApp.InitializeDeviceObjects()
  at MediaPortal.D3D.InitializeDevice()
[2013-04-14 12:19:55,150] [Error  ] [MPMain  ] [ERROR] - D3D: Could not create device
[2013-04-14 12:20:17,492] [Error  ] [MPMain  ] [ERROR] - D3D: Reset failed - System.NullReferenceException: Object reference not set to an instance of an object.
  at MediaPortal.D3D.InitializeDevice()
  at MediaPortal.D3D.RecoverDevice()
[2013-04-14 12:20:17,492] [Log	] [MPMain  ] [ERROR] - Exception: System.NullReferenceException: Object reference not set to an instance of an object.
  at MediaPortal.D3D.RecoverDevice()
  at MediaPortalApp.OnProcess()
  at MediaPortal.D3D.OnIdle(Object sender, EventArgs e)
  at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
  at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
  at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
  at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
  at System.Windows.Forms.Application.Run(Form mainForm)
  at MediaPortalApp.Main(String[] args)  Message: Object reference not set to an instance of an object.  Site  : Void RecoverDevice()  Source : MediaPortal  Stack Trace:	at MediaPortal.D3D.RecoverDevice()
  at MediaPortalApp.OnProcess()
  at MediaPortal.D3D.OnIdle(Object sender, EventArgs e)
  at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
  at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
  at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
  at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
  at System.Windows.Forms.Application.Run(Form mainForm)
  at MediaPortalApp.Main(String[] args)
[2013-04-14 12:20:17,492] [Error  ] [MPMain  ] [ERROR] - MediaPortal stopped due to an exception Object reference not set to an instance of an object. MediaPortal	at MediaPortal.D3D.RecoverDevice()
  at MediaPortalApp.OnProcess()
  at MediaPortal.D3D.OnIdle(Object sender, EventArgs e)
  at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
  at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
  at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
  at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
  at System.Windows.Forms.Application.Run(Form mainForm)
  at MediaPortalApp.Main(String[] args)

[/hide]
** EDIT **
After 2 reboots the above error is gone.

 

[Sebastiii]

Also having multiple displays connected on multiple adapters may also not work correctly. But that is a more exotic use case these days anyway that MP users using multiple GPUs at the same time and they each control displays on their own and MP gets switched between adapters all the time.

I'm using two GPUs since MediaPortal is using the wrong display for refresh rate. For example when playing a 50 fps video on the secondary monitor while the primary monitor is set to 60 Hz will cause mad stuttering since it will try to sync to 60 Hz. This is prevented when using multiple graphics cards. I got the tip from another MediaPortal user so there's probably more users in the same situation (granted still possibly exotic).
However I do not constantly move MediaPortal. I use a command line switch to start MediaPortal - /fullscreen /screen=1.

I do a tricky workaround on fork for it, not sure if it will solve it for you lol

 

[Scythe42]

#1 : As soon as we drag the window to a 'fixed' border of the monitor, the cursor continue to move to the edge

Resizing is aspect ratio safe, the mouse cursor still can move on X or Y axis. Cosmetic issue that is inherent to Windows itself (OSX would never allow such a glitch!).

You see the same with a ton of video players as well. I was under the impression that users know what this is. I feared not allowing them to move the cursor even more will confuse them. Obviously I was wrong. Will change that.

#2 : hidden mouse (seems to be related to focus but didn't find a way to catch it each time)

Yes, there might be a glitch left here and then when focus switches. I did my best to catch them all and get them in a defined state at least. For stuff that is left I need exact steps to reproduce. Cosmetic more or less. Could not fix all stock 1.3.0 mouse issues. I took care of the most annoying ones like the stupid cursor always popping up on playback.

As said need steps to reproduce, when mouse cursor issues are showing up always with: (a) what is seen and (b) what as expected to be seen. And with logs that only show the issue itself with a few seconds pause between actions to reproduce, so I can read the log easier.

#3 : strange MP windowed appear after hitting border of the monitor (top it seems) and when moving mp windowed i can see mp windowed switch between normal windowed window and higher one very fast. (hard to explain and a video will appear soon)

No bug. That is a Windows feature.

When you "bump" a window to the side, Windows wants to to resize a window right away. Try with "notepad" for example and you understand better.

MP preserves the aspect ratio but allows the width change from Windows. What you are seeing is perfectly ok, you are just not used to that Windows feature. Let me guess, you recently upgraded to Win8? The "bumping" also shows a small circle around the mouse cursor at this time.

My recommendation: turn this annoying feature off that tries to resize windows when dragging and the mouse cursor hits the edge of the screen. It's somewhere under accessibilty features I think. It is really really really annoying.

Here we go for video
So after hitting (top screen) the issue appear, i hold left mouse button but you can see that the cursor stay not fixed again MP Window
I will reproduce it with log too

Thanks for the video!

That is because Windows wants to continuously resize the Window to a not aspect ratio safe resolution after you bumped the mouse cursor to the top screen while dragging a window.

Even if you continue to move the mouse cursor Windows will try over and over and over again every time you change the Window position and MP fights against it. Actually you should just see shortly the border of the window but not the content itself and only at the time you hit the border.

Do you run any stuff like Classic Shell in Win8 and/or changed the behaviour of screen borders and corners? If so, you have the guilty party.

Anyway, no bug. But please Mantis, that we have a visual glitch here for future reference. But as said it is not MP, it is Windows.

Just a accessibility feature of Windows that does not really work out well in general. It is intended for touch control to resize windows by dragging them to the screen corners and resizing happens when the finger hits the end of the screen. Feels absolutely unnatural with the mouse.