Mediaportal Resume from Standby (Recording) not working (1 Viewer)

[jimbeam128]

Hello,

I´ve got a problem with resuming from Standby(S3) to record a TV-Show. Powerscheduler is configured to Standby after 2 Minutes ideling and that works. -> System goes to Standby. But the configured scheduled Recording does not wake up the system.
The Powerscheduler++ Config shows on "next wakeup time" my configured scheduled recording.
Standby is handeled by PowerScheduler
and Standby is prevented by SetupTV

I´ve got a Win7 64 bit SP1 Installation with MP 1.3 and Powerscheduler ++

I´ve got a scheduled Task in Windows which will grab the EPG for me. This scheduled Task is configured to wake up the system to execute the Task. -> That works!

So there must be something wrong, telling Windows to "plan" the wake up for a scheduled recording.

In the past I had with the same physical system configuration Windows XP and MP 1.3 installed. On that plattform resuming was no problem...

Does anybody have a clue?

I don´t know which logs I shall post. Maybe someone can tell me which logs could be interesting to investigate...

 

[mm1352000]

I don´t know which logs I shall post.

The answer to this question is always all of them.
Please use the watchdog tool with the 3rd option (to grab existing log files):
http://wiki.team-mediaportal.com/1_..._Non_Reproducible_Problems_within_MediaPortal

...and also specify the name and time of the recording which was meant to cause wake-up.

 

[jimbeam128]

OK, so here the logs. I´ve scheduled a manual recording for 22:00 on 2013-09-18 and it should woke up at 21:52...

On 21:57 I woke up the system manually and then colleted the log-files.

What I can say is that when I entered the command

powercfg /waketimers there is the recording entered in the list... But it does not wake up.

I also checked my tests and sometimes it works, the system will be waked up by tvservice. (look at system_eventlog) Sometimes it doesn´t....

 

[jimbeam128]

Here another test I did last night. I´ve scheduled 3 recordings for waking up at
01:08
02:15
03:13

The recordings are shown in tvserver_tv.log.

The first two recordings were sucessfully executed. System woke up from stand by and recorded my planned items.

The third one has not been executed. Due to the fact that the system did not wake up.

 

[mm1352000]

I see what you mean. Unfortunately I have no idea what is going on. @michael_t any thoughts?

 

[jimbeam128]

I think I could isolate the problem a little. Mediaportal seems to "unload" my mdapifilter and is running out of time.

The 2nd recording (02:15) was configured with a channel which uses that mdapifilter0

When the recording is finished MediaPortal wants to go to standby and I can see these last messages in the tvserver log:

2013-09-20 03:01:52.838000 [PowerEventThread(9)]: Remove filter from graph: BDA MPEG2 Transport Information Filter
2013-09-20 03:01:52.839000 [PowerEventThread(9)]: Remove filter from graph: MediaPortal Ts Analyzer
2013-09-20 03:01:52.840000 [PowerEventThread(9)]: Remove filter from graph: MPEG2-Demultiplexer
2013-09-20 03:01:52.841000 [PowerEventThread(9)]: Remove filter from graph: Inf Tee
2013-09-20 03:01:52.842000 [PowerEventThread(9)]: Remove filter from graph: mdapifilter0
2013-09-20 03:12:19.649000 [(7)]: TCP connect took : 999
2013-09-20 05:20:14.638000 [(6)]: TCP connect took : 1000

When the standby is "sucessfully" executed so that the system wakes up for the next recording I can see this messages in the log:
This is the output of the end of my first test-recording starting at 01:08

2013-09-20 01:56:52.839000 [PowerEventThread(9)]: Remove filter from graph: BDA MPEG2 Transport Information Filter
2013-09-20 01:56:52.840000 [PowerEventThread(9)]: Remove filter from graph: MediaPortal Ts Analyzer
2013-09-20 01:56:52.841000 [PowerEventThread(9)]: Remove filter from graph: MPEG2-Demultiplexer
2013-09-20 01:56:52.841000 [PowerEventThread(9)]: Remove filter from graph: Inf Tee
2013-09-20 01:56:52.842000 [PowerEventThread(9)]: Remove filter from graph: mdapifilter0
2013-09-20 01:56:52.848000 [PowerEventThread(9)]: Remove filter from graph: Inf Tee Second
2013-09-20 01:56:52.850000 [PowerEventThread(9)]: Remove filter from graph: FireDTV BDA Receiver DVBS2
2013-09-20 01:56:52.851000 [PowerEventThread(9)]: Remove filter from graph: FireDTV BDA Tuner DVBS2
2013-09-20 01:56:52.852000 [PowerEventThread(9)]: Remove filter from graph: Generic Network Provider
2013-09-20 01:56:52.853000 [PowerEventThread(9)]:  free devices...
2013-09-20 01:56:52.854000 [PowerEventThread(9)]:  decompose done...
2013-09-20 01:56:52.854000 [PowerEventThread(9)]: Controller: dispose card:MediaPortal IPTV Source Filter
2013-09-20 01:56:52.855000 [PowerEventThread(9)]: Controller: dispose card:RadioWebStream Card (builtin)
2013-09-20 01:56:52.855000 [PowerEventThread(9)]: RadioWebStream:Dispose()
2013-09-20 01:56:52.855000 [PowerEventThread(9)]: PS: Run external command
2013-09-20 01:56:52.856000 [PowerEventThread(9)]: PS: Send "EnteringStandby" event

I think in the upper case here posted Mediaportal seems to run out of time:

2013-09-20 03:12:19.649000 [(7)]: TCP connect took : 999

and cannot "inform" the OS about entering Standby-State as shown in the lower case:

2013-09-20 01:56:52.856000 [PowerEventThread(9)]: PS: Send "EnteringStandby" event

Is there maybe any chance to force "quitting" by stopping the tvservice before going to standby to workarround this issue?

 

[michael_t]

I think I could isolate the problem a little. Mediaportal seems to "unload" my mdapifilter and is running out of time.
The 2nd recording (02:15) was configured with a channel which uses that mdapifilter0
...
Is there maybe any chance to force "quitting" by stopping the tvservice before going to standby to workarround this issue?

Looking at the tvservice log and the system event log I see that your system suspended at 03:01:52 (03:01:57). On a suspend event PS++ stops the TVController and this got stuck in unloading the mdapifilter0. The PC suspended with TVService hanging and resumed at 03:12:05. At this time the TVService was still hung up and did not react, nor did it make the scheduled recording. It suspended 2 minites later and woke up again at 05:20 to do some scheduled task and suspended again...
So the errors you experience on your PC result from a bug in unloading the filter and not from PS++ suspend / wakeup.

Michael

PS: Though you configured PS++ to suspend your system actively it is indeed suspeded by something else. I see only a code (7) as reason in the logs, but you can look into your event logs and see in plain text what made your system sleep. If it is the Windows idle timer you should set your PS++ config to automatically set the Windows power settings to avoid any inconsistencies here.

 

[jimbeam128]

Hello Michael,

thank you for your time analysing the logs! Indeed, the Windows Standby and Powerscheduler++ Standby were configured the same (2 Minutes). I´ve reconfigured it to let PowerScheduler always suspend the system.

I´ve uninstalled this additional filter and checked again. -> Issue solved.

 

[michael_t]

thank you for your time analysing the logs!

You're welcome... Fine to hear that everything is ok now.

Michael