What do you mean with "worse than 1.3.0"? Its great that 1.4.0 will support the windows inbuilt screensavers and the MP inbuilt screensaver options are working as the should. The only problem with screensaver seems that the windows screensavers not work with "MP always on top" option. The other usecases are working fine for me.
Call for tester for 1.4.0 features and fixes (4 Viewers)
- Thread starter Scythe42
- Start date
- Status
Well, if something in these fixes breaks something that was working okay in 1.3.0, this is a problem.
However, if something works better than 1.3.0 but not quite perfectly, then we have a clear improvement so this is okay (within reason!).
Yeah you are right! In my opinion the option that you can use windows screensavers in 1.4.0 are definitely an improvement. So its definitely no step backwards. For me, the only issue left with this is that the windows screensaver doesnt work when "mp always on top" is enabled. Everything else related to the MP inbuilt screensaver works like in 1.3.0 (AFAIK)
.
Last edited:
- Thread starter
- #744
Just did a quick test on a Win8 installation with my builds:
For the guys thought they saw a glimpse of the screen saver: check your logs afterward for "Main: SC_SCREENSAVE".
That would mean Windows send the message and you should have seen a screensaver (except during playback of movies and slideshows as MP then stops it). And of course make sure when testing that the MP screen saver is disabled.
Possible that there is a glitch in Win7 that was corrected in Win8. But a no SC_SCREENSAVE message by Windows itself indicates that it has nothing to do with MP. XP maybe even worse or more inconsistent.
But it makes perfect sense. If you want something fullscreen always on top then it stays always on top and does not get overlayed by another always on top thing. That would be a race condition. So the Win8 behavior seems complety logical to me.
But honestly: I never ever had the need for an always on top feature in my life. But that's just me.
Blanking the display, meaning the power management settings work, regardless of settings.
MP Screensaver works as before.
- If you have an always on top form that is fullscreen Windows will not even try to kick in the screensaver. Meaning the SC_SCREESAVE message is not send!
- As soon as it is a always on top window it kicks in and overlays MP.
- No always on top, screensaver gets started an overlays MP regardless of mode.
For the guys thought they saw a glimpse of the screen saver: check your logs afterward for "Main: SC_SCREENSAVE".
That would mean Windows send the message and you should have seen a screensaver (except during playback of movies and slideshows as MP then stops it). And of course make sure when testing that the MP screen saver is disabled.
Possible that there is a glitch in Win7 that was corrected in Win8. But a no SC_SCREENSAVE message by Windows itself indicates that it has nothing to do with MP. XP maybe even worse or more inconsistent.
But it makes perfect sense. If you want something fullscreen always on top then it stays always on top and does not get overlayed by another always on top thing. That would be a race condition. So the Win8 behavior seems complety logical to me.
But honestly: I never ever had the need for an always on top feature in my life. But that's just me.
Blanking the display, meaning the power management settings work, regardless of settings.
MP Screensaver works as before.
Last edited:
- July 8, 2006
- 879
- 259
- Home Country
-
Germany
In Windows 7 there is a different behaviour. I have tested in window mode / always on top too and the screensaver was not started.
- Thread starter
- #746
Thanks for letting me know. Then MS fine-tuned it for Win8 a bit more in regards to usability.
We are dealing with specified behavior by Windows here. As said check for SC_SCREENSAVE in the logs. That indicates that Windows started the screensaver and it should be visibiel. No Entry = Windows did not even try to start it or MP screen saver is used.
Open Items:
We are dealing with specified behavior by Windows here. As said check for SC_SCREENSAVE in the logs. That indicates that Windows started the screensaver and it should be visibiel. No Entry = Windows did not even try to start it or MP screen saver is used.
Open Items:
- Bringing back support for D3D software devices, but log it as a warning. Will put it in probably tomorrow evening. Tonight is movie night!
- Verification on latest changes in regards to splash screen and multi display setups. I guess @legnod will be so nice and do a test in the evening when he comes home.
- Any mouse issues lefts in current GIT. @FreakyJ and @Sebastiii will probably try it. I cannot reproduce any at the moment. Does not mean I got them all.
Last edited:
Last edited:
- July 8, 2006
- 879
- 259
- Home Country
-
Germany
@Scythe42:
A wish from my site: Is it possible to merge this to your next Testbuild?
https://forum.team-mediaportal.com/threads/option-to-disable-stop-live-tv-dialog.116503/#post-965178
It seems to be ready for me and I would like to test your new features and this one together.
My HDMI-CEC device has some nice features regarding switching off the TV-set or changing the sources and I would like to test together with TV switching off in MePo.
Do you think that this is possible?
A wish from my site: Is it possible to merge this to your next Testbuild?
https://forum.team-mediaportal.com/threads/option-to-disable-stop-live-tv-dialog.116503/#post-965178
It seems to be ready for me and I would like to test your new features and this one together.
My HDMI-CEC device has some nice features regarding switching off the TV-set or changing the sources and I would like to test together with TV switching off in MePo.
Do you think that this is possible?
Wow, this thread moves fast! The Away Mode is there to save the user from accidentally shutting down the system while the htpc is recording. Yes, the power button on some remotes will trigger the action in MP (and MP can ignore it if there is a recording going on). But that is not the only setup we have. Many remotes (I guess even the MCE ones) will send the power request directly to Windows, which will shutdown as per spec. A shutdown (or hibernate) may not be aborted by SW anymore, so the recording will be interrupted.
The same is true for my power switch on the htpc case. Yes, I set it to hibernate (all my power switches do the same thing here) and still I want MP to interrupt me (or my wife ;-) if there is a recording going on.
Scythe, you do fantastic rework here, but removing existing functionality (even if you sometimes think of it as bugs, not features) has to be checked very carefully.
The same is true for my power switch on the htpc case. Yes, I set it to hibernate (all my power switches do the same thing here) and still I want MP to interrupt me (or my wife ;-) if there is a recording going on.
Scythe, you do fantastic rework here, but removing existing functionality (even if you sometimes think of it as bugs, not features) has to be checked very carefully.
The two fixes are entirely separate. Sorry, but the purpose of this thread is to get the fixes tested, rather than to provide build for users. All building instructions are in the wiki, so you could possibly make your own build with both branches included. Once you get used to doing this, it is actually quite easy.
What we need right now with this branch is a period of testing, consolidation and then we have a chance to get it into a release version of MP. Adding new stuff at this stage really isn't a good idea.
- Status