MP1-4420: Potential Fix for the broken Startup Delay on resume (1 Viewer)

[michael_t]

This has never worked properly, except for fullscreen DefaultWide skin so it seems.

There has never been a "wait for resume" message at all - for no skin. There is a "Waiting xx sec for start..." message on the splash screen (maybe shown skin dependent), but this is only shon on start of MP, not on resume.

Michael

 

[Brudertac]

Hm, i was 100% sure there was a "Wait x seconds" on Resume on older MP Versions. 1.3 or 1.4... ;-)

 

[michael_t]

I just looked at the sources of MP 1.3 - no mesage found

Michael

 

[Sebastiii]

I think it comes when restart mp on resume was there

 

[Sebastiii]

But now this option doesn't exist anymore

 

[Brudertac]

I think it comes when restart mp on resume was there

Ahhhh. That was it! Thank you.

 

[Brudertac]

There it was again. But not after Resume from Standby. I was switching HDMI Inputs on the connected Receiver and also Switch TV on/off.
After those Tests MP does not react to any Inputs with Remote or Keyboard.

I had to use the Taskmanager to end it. But Taskmgr also does not shown MP as crashed.

Logs are attached.

 

[HomeY]

There it was again. But not after Resume from Standby. I was switching HDMI Inputs on the connected Receiver and also Switch TV on/off.
After those Tests MP does not react to any Inputs with Remote or Keyboard.

TsBufferExtractor plugin:

[2014-08-08 20:32:03,966] [Error  ] [MPMain   ] [ERROR] - TsBufferExtractorClient exception: System.Runtime.Remoting.RemotingException: Der Channel "http" wurde bereits registriert.
   bei System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel chnl, Boolean ensureSecurity)
   bei System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel chnl, Boolean ensureSecurity)
   bei TsBufferExtractorClient.TsBufferExtractorClient.Start()

@regeszter any ideas?

 

[regeszter]

There it was again. But not after Resume from Standby. I was switching HDMI Inputs on the connected Receiver and also Switch TV on/off.
After those Tests MP does not react to any Inputs with Remote or Keyboard.

TsBufferExtractor plugin:

[2014-08-08 20:32:03,966] [Error  ] [MPMain   ] [ERROR] - TsBufferExtractorClient exception: System.Runtime.Remoting.RemotingException: Der Channel "http" wurde bereits registriert.
   bei System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel chnl, Boolean ensureSecurity)
   bei System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel chnl, Boolean ensureSecurity)
   bei TsBufferExtractorClient.TsBufferExtractorClient.Start()

@regeszter any ideas?

Yes, I have. It is not an error, just an wrong logging message from me. Should be fixed in 0.4.0

Edit: sorry, it is a new issue. Lets go to https://forum.team-mediaportal.com/...r-tvserver-1-9-pre-release-2014-08-07.125776/

Edit 2: fixed https://forum.team-mediaportal.com/...elease-2014-08-010.125776/page-3#post-1095587

 

[pdiaz]

Hi all,

I implemented a totally new fix for the problem which works fine for me (can even handle suspend while still waiting for delayed resume cleanly). Please give it a try.
The new branch is: MP1-4420_Delay_resume_is_not_working_correctly. A code review has been created (MP1CR-517).
To test the new code just replace 1.9 Pre-release MediaPortal.exe with the one provided in the zip file.

I tested the branch on Win7 with both sleep mode and hybrid sleep.
To be done yet:

• Test on Win8
• Test with hibernation (S4)
• Implement a dialog / splash screen indicating that MP is waiting to resume after wakeup (at the moment the screen is shown but unreactive)

Michael

PS: The solution in the previous post also came from me but is conceptionally buggy. So it makes not much sense testing it any longer

Hi Michael,

Mediaportal seems to freeze up on my system if it wakes up automatically for recordings or other scheduled events. I have tried your fix after I installed the 1st one in this thread posted by HomeY (which didn't solve my problem). Unfortunately it doesn't seem compatible with the 1.9.0 pre-release version used in the 1st link so haven't been able to see if it will fix my issue. Is there any chance you could redo it for the same version as HomeY's post as I don't want to do a reinstall to 1.8.0.

Thanks!