home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Media Portal freezes on wake
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1158907" data-attributes="member: 82144"><p>You know what ALT+TAB does, right?</p><p>When you use ALT+TAB to select an application, that makes the application active. Another way of saying this is that it focusses the application. That's what I'm talking about when I ask "does MP have focus" or "is it the active application/window".</p><p></p><p></p><p>You already checked it by testing ALT+TAB. Nothing further needs to be done. That was what I was trying to say.</p><p></p><p></p><p>That is called "away mode". Away mode is used because TV Server is recording "Formula One Racing". If standby/hibernate were allowed, the recording would not succeed.</p><p></p><p></p><p>The difference between the 2 scenarios is quite clear in the log files.</p><p></p><p>In the first case ("not working") Windows tells MP that it has "resumed automatically" (which means that you didn't trigger the resume). We both know this is correct because PowerScheduler woke the computer in order to record Formula One. In this scenario - automatic resume for recording or EPG grabbing - MP does not activate the user interface. It's unnecessary if there's nobody actually there wanting to use MP, and usually the display/screen/TV is off.</p><p></p><p>When you start clicking etc., Windows is meant to tell MP that it has fully resumed from suspend (ie. that there's now somebody actively using the PC). <strong>Windows does not do this</strong>, and that's the problem. Without that notification, the MP user interface remains inactive and unresponsive. Windows <em>does</em> indirectly tells MP that you're "providing input", but this is not enough to get MP to activate the interface.</p><p></p><p>In the second case ("working"), Windows does what it's expected to do and notifies MP that it was triggered to fully resume from suspend by you. MP knows that it needs to activate the interface, and so everything works properly.</p><p></p><p></p><p>I think this is a different problem. Your earlier log files show something different to these latest log files. Please let's try and focus on one thing at a time.</p><p></p><p></p><p>Okay... but not relevant.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1158907, member: 82144"] You know what ALT+TAB does, right? When you use ALT+TAB to select an application, that makes the application active. Another way of saying this is that it focusses the application. That's what I'm talking about when I ask "does MP have focus" or "is it the active application/window". You already checked it by testing ALT+TAB. Nothing further needs to be done. That was what I was trying to say. That is called "away mode". Away mode is used because TV Server is recording "Formula One Racing". If standby/hibernate were allowed, the recording would not succeed. The difference between the 2 scenarios is quite clear in the log files. In the first case ("not working") Windows tells MP that it has "resumed automatically" (which means that you didn't trigger the resume). We both know this is correct because PowerScheduler woke the computer in order to record Formula One. In this scenario - automatic resume for recording or EPG grabbing - MP does not activate the user interface. It's unnecessary if there's nobody actually there wanting to use MP, and usually the display/screen/TV is off. When you start clicking etc., Windows is meant to tell MP that it has fully resumed from suspend (ie. that there's now somebody actively using the PC). [B]Windows does not do this[/B], and that's the problem. Without that notification, the MP user interface remains inactive and unresponsive. Windows [I]does[/I] indirectly tells MP that you're "providing input", but this is not enough to get MP to activate the interface. In the second case ("working"), Windows does what it's expected to do and notifies MP that it was triggered to fully resume from suspend by you. MP knows that it needs to activate the interface, and so everything works properly. I think this is a different problem. Your earlier log files show something different to these latest log files. Please let's try and focus on one thing at a time. Okay... but not relevant. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Media Portal freezes on wake
Contact us
RSS
Top
Bottom