[Merged] Power Saver feature

[Hex]

@meleu \m/ :)

You guys dont ever waste my time. Your feedback is really important.

Given enough eyeballs, all bugs are shallow -- Linus Torvalds

EDIT : can you post some screenshots. That would be helpful

[meleu]

@Hex said in Testers needed :: Power Saver features :: PR #172:

can you post some screenshots. That would be helpful

I'll try a video, give me some minutes.

[meleu]

@Hex sorry about the video quality, but here it is:

[Hex]

@meleu Firstly stop apologising. Secondly it was my mistake. Since I am using a theme that doesnt have description shown I was unaware that that is what was not working. I was under the impression that you were talking about the game name which scrolls nicely in my build:facepalm:

So to makes things easy the description is not going to scroll. Asking the description to move is same as not having PS. Frames need to be rendered to show the moving text. This is a side effect. A switch would solve this trouble. Users will have to decide what is important for them. Both features are mutually exclusive just like Video preview and PS.

---

Guys what do you think about this. Can anyone suggest a better way to handle this?

[meleu]

@Hex said in Testers needed :: Power Saver features :: PR #172:

So to makes things easy the description is not going to scroll.

Yeah, I think it's a fair price to pay for power saving, specially for those who build handhelds.

But now I have changed my mind about it being enabled by default. Once this change is merged in a couple of days people will come to the forums complaining about text not scrolling...

Well, after all this conversation on this thread my opinion is:

• this option should be disabled by default (otherwise people unaware about this change will open topics about "issues after updating ES").
• (obviously) it must have a switch to enable/disable (it's already done, I'm just putting clear that I changed my mind).

[Hex]

@meleu Lets talk tomorrow. I am too sleeppy to type

[dankcushions]

@Hex said in Testers needed :: Power Saver features :: PR #172:

So to makes things easy the description is not going to scroll. Asking the description to move is same as not having PS. Frames need to be rendered to show the moving text. This is a side effect. A switch would solve this trouble. Users will have to decide what is important for them. Both features are mutually exclusive just like Video preview and PS.

Guys what do you think about this. Can anyone suggest a better way to handle this?

in my opinion, when you highlight a game, the text should scroll to the very end, then go back to the beginning, and then stop (at this point i guess power saving kicks in). That way if someone wanted it to scroll to the end again, they would just have to re-highlight it in the list. that's intuitive to me - in fact i think that's how i've seen it handled in other interfaces. something constantly scrolling can be distracting.

OR, powersaving doesn't start until the 'screen dim'/screensaver function? could that work?

i don't like the idea of any new options added to ES. i think it's cluttered already.

[Hex]

Waiting for powersaver to kick in after screensaver is very bad for video screensaver and it defeats the purpose altogether of PS. PS is ment to act like a screensaver without modifying the screen. It just allows CPU to sleep

[dankcushions]

@Hex ok, then i vote for my first suggestion :)

[pjft]

Let's keep the conversation here rather in GitHub then :)

My take on the descriptions not flowing is mentioned there, but I'll repeat it here:

• I believe that no default option should remove or reduce functionality from the users. From what I'm reading, this does happen in some situations, so I am not ready to support this becoming the default as it is. Always bear in mind that, while any particular change may improve the life for several people, there are several users for which ES is just fine as it is. In this particular work, people with RPis 2 and 3s won't really "feel" any impact from this change unless they're actively monitoring CPU cycles and such (which, let's be fair, isn't what a "normal" user will do unless they're a bit OCD).
• I agree that, regardless of whether this is an option or not, or whether this is a default or not, this can certainly be the default for when this is in screensaver mode for DIM and BLACK. I'll even expand more: I think that this can be the default for screensaver mode when using OMXPlayer, as it has nothing to do with ES in terms of rendering pipeline.

My recommendation, though, is to try to understand - and enumerate exactly - what functionality does this not allow for, and then working together to make that work, or at least designing a proper, working experience. Can someone help compile that?

If there are animations that don't work when in PS mode, I'd push for changing them from scrolling to flipping after a while, in PS mode - meaning, rather than slowly scrolling for a few seconds, have them just "flip" (as in if you'd press "page down" on it) to the next section.

Alternatively, can we not just get more power savings by forcing ES to render less frames per second during the animations? Or alternatively, can we not be in PS mode, but if there's an animation to be triggered, it is smart enough to run the animation (scrolling) and then just stay in low consumption mode if there's nothing to do?

I see mentions of code to "disable" and "enable" PS before and after animations. I believe the right thing for it would be to be centrally - and transparently - controlled rather than each individual component to have to replicate the exact same thing.

I wonder how hard it'd be to rearchitect the whole rendering pipeline so that it is overall smarter, and we only effectively render "dirty" (changed) objects, and objects on top of them? Would that alleviate the burden?

I mean, surely a scrolling text box wouldn't be responsible for 20% or so CPU consumption?

A few questions here.

Thanks for working through this.

[cyperghost]

@pjft @Hex @dankcushions

I believe that no default option should remove or reduce functionality from the users. From what I'm reading, this does happen in some situations, so I am not ready to support this becoming the default as it is. Always bear in mind that, while any particular change may improve the life for several people, there are several users for which ES is just fine as it is. In this particular work, people with RPis 2 and 3s won't really "feel" any impact from this change unless they're actively monitoring CPU cycles and such (which, let's be fair, isn't what a "normal" user will do unless they're a bit OCD).

That's the point I always gave feedback to. The PS option is more usefull for RPi0/1 builds and even "essential" for devices that get powered via battery. I think if it would made be option via selection menu and a message would be displays like "be aware, there are some effects on GUI but it will save CPU cycles" then it should be okay, even for the normal user.
There are other options which seem sometimes difficult to understand. Normal user also asks... What are the gamelist options for? What means parsing the gamelist only? I think small info notes if you activate/deactivate can help unexperinced users und may avoid backtalks in the form.
What do you think of?

I agree that, regardless of whether this is an option or not, or whether this is a default or not, this can certainly be the default for when this is in screensaver mode for DIM and BLACK. I'll even expand more: I think that this can be the default for screensaver mode when using OMXPlayer, as it has nothing to do with ES in terms of rendering pipeline.

That's imho a question that should be cleared by the developers ;) I'm just an average user.

[Zigurana]

I've made this comment earlier on the Github thread:

There are several ways to cope with the scrolling text issue. For instance, you could think of linking it with the screensaver time-out. This to me seems the more natural solution, going into PS mode only once the screensaver kicks in.

That way, we also circumvent the video display issue: If you select a dim/black screensaver, you also get PS, if you select video-screensaver, you're better wired to a wall...

All in all I think we should strive to limit the amount of options, especially for features that are supposed to work under-the-hood like this one. If we want to signal it explicitly, we could consider renaming the dim/black screensaver types to "DIM (POWERSAVER)" and "BLACK (POWERSAVER)".

[jdrassa]

@pjft said in Testers needed :: Power Saver features :: PR #172:

If there are animations that don't work when in PS mode, I'd push for changing them from scrolling to flipping after a while, in PS mode - meaning, rather than slowly scrolling for a few seconds, have them just "flip" (as in if you'd press "page down" on it) to the next section.

As is, I don't think this would work. Power Saver works by switching input event processing from polling to waiting, essentially halting all logic until another input event occurs.

I wonder how hard it'd be to rearchitect the whole rendering pipeline so that it is overall smarter, and we only effectively render "dirty" (changed) objects, and objects on top of them? Would that alleviate the burden?

I mean, surely a scrolling text box wouldn't be responsible for 20% or so CPU consumption?
This approach could help, but would be a very large undertaking. The complex problem is determining what is "dirty". It is not just the component that requires animation. It is anything that overlaps with that component and potentially anything that overlaps with those. A background image (as most themes have) would likely force everything to be re-rendered.

I would hate to see @Hex's work on this get bogged down by us trying to design the perfect solution. I am OK with a Power Saver option that comes at the cost of some reduced functionality. That doesn't prevent us from learning from it and making general improvements.

[pjft]

@cyperghost Correct.

My question on the rendering pipeline was indeed more for @Hex , @jdrassa and @Zigurana who are more familiar with ES development, and could comment on the validity and worthiness of exploring any such alternative.

@jdrassa Agreed. My intent was not to increase scope (and thanks for calling out that that was how it was coming across), but more to see if there's a smaller but more manageable way to address this.

Truth be told, I was mostly thinking of whether there'd be something that could be done at the GuiComponent level to reduce rendering objects that aren't dirty - not to edit massive amounts of code.

And, once again, one thing does not preclude the other - this can certainly be launched, and we can still look into reducing the overall rendering overhead at a later stage.

I won't oppose to launching with reduced functionality - and following @Zigurana 's suggestion of, in screensaver mode, to actually default to that - provided that the reduced functionality is spelled out.

Also, @Hex : I'm pretty sure that if the video player is OMX Player you don't need to animate things, as the video rendering is a separate process. You only need to animate things if it's VLC. So that's a bonus, but I'd love to test that.

[Hex]

@pjft said in Testers needed :: Power Saver features :: PR #172:

Let's keep the conversation here rather in GitHub then :)

Agreed

My recommendation, though, is to try to understand - and enumerate exactly - what functionality does this not allow for, and then working together to make that work, or at least designing a proper, working experience. Can someone help compile that?

If there are animations that don't work when in PS mode, I'd push for changing them from scrolling to flipping after a while, in PS mode - meaning, rather than slowly scrolling for a few seconds, have them just "flip" (as in if you'd press "page down" on it) to the next section.

This is a good suggestion

Alternatively, can we not just get more power savings by forcing ES to render less frames per second during the animations? Or alternatively, can we not be in PS mode, but if there's an animation to be triggered, it is smart enough to run the animation (scrolling) and then just stay in low consumption mode if there's nothing to do?

I would like to disagree on this point. ES already does its best at rendering with as much FPS as possible (probably capping it at 60fps). I would not like to see that reduced forcefully. Its a timed process ie.

0.......0.......0......0...
XzzzzzzzXzzzzzzzXzzzzzzXzzz

Here "zzz" represents processing time and is variable from machine to machine
"X" refers to when next frame is starting to render
"0" refers to when rendered frame is shown

Since "zzz" varies per machine the frames are rendered with great precision by hooking into the clock "...". Simply said the rendered checks what time it is and decides which frame of the animation to render. So if your animation lasts a minute, renderer checks how much time is elapsed and based on that which frame to render. Without this animations would be very fast on laptop and very slow on Pi.

I see mentions of code to "disable" and "enable" PS before and after animations. I believe the right thing for it would be to be centrally - and transparently - controlled rather than each individual component to have to replicate the exact same thing.

I agree on this but I dont know at present how that could work.

I wonder how hard it'd be to rearchitect the whole rendering pipeline so that it is overall smarter, and we only effectively render "dirty" (changed) objects, and objects on top of them? Would that alleviate the burden?

It would help a lot. The renderer hasn't been touched in 2 years.

I mean, surely a scrolling text box wouldn't be responsible for 20% or so CPU consumption?

What is being done to support that feature is responsible for the increased CPU consumption.

[Hex]

@cyperghost I am not interested in adding more and more options to the menu. These quickly become stagnant as the user only looks at it once and never again. I would like to suggest having a screen like setup where user can configure all one time options just like Configure Input, which is never used unless you screwed up.

[pjft]

@Hex Sounds good, no further questions.

Still, I'd like to test whether PS can be turned on if using OMX Player as the video player in video gamelists - except that the text won't scroll, and same with OMX Player as the screensaver player. I imagine with VLC you'll need to have it off, but do test that.

Also, as mentioned, I don't think it should be the default at this stage, though it is looking good so far!

[Hex]

@Zigurana said in Testers needed :: Power Saver features :: PR #172:

I've made this comment earlier on the Github thread:

There are several ways to cope with the scrolling text issue. For instance, you could think of linking it with the screensaver time-out. This to me seems the more natural solution, going into PS mode only once the screensaver kicks in.

So you are suggesting that scrolling occur when screensaver starts? that wont help.

That way, we also circumvent the video display issue: If you select a dim/black screensaver, you also get PS, if you select video-screensaver, you're better wired to a wall...

Not necessarily. Power savings reduces overhead processing and hence heating of cpu. Even walled devices are helped. BTW ES utilizes 60% on Pi zero while OMX hovers on 10% with video. So you see.

All in all I think we should strive to limit the amount of options, especially for features that are supposed to work under-the-hood like this one. If we want to signal it explicitly, we could consider renaming the dim/black screensaver types to "DIM (POWERSAVER)" and "BLACK (POWERSAVER)".

On one hand I do not think combining options is a good way to proceed. On the other I am against increasing options in ES

[Hex]

@jdrassa said in Testers needed :: Power Saver features :: PR #172:

@pjft said in Testers needed :: Power Saver features :: PR #172:

If there are animations that don't work when in PS mode, I'd push for changing them from scrolling to flipping after a while, in PS mode - meaning, rather than slowly scrolling for a few seconds, have them just "flip" (as in if you'd press "page down" on it) to the next section.

As is, I don't think this would work. Power Saver works by switching input event processing from polling to waiting, essentially halting all logic until another input event occurs.

It can also have a timeout parameter. That is how it is currently handling screensaver. Waiting timesout just before screensaver timeout and triggers screensaver.

I wonder how hard it'd be to rearchitect the whole rendering pipeline so that it is overall smarter, and we only effectively render "dirty" (changed) objects, and objects on top of them? Would that alleviate the burden?

I mean, surely a scrolling text box wouldn't be responsible for 20% or so CPU consumption?
This approach could help, but would be a very large undertaking. The complex problem is determining what is "dirty". It is not just the component that requires animation. It is anything that overlaps with that component and potentially anything that overlaps with those. A background image (as most themes have) would likely force everything to be re-rendered.

I would hate to see @Hex's work on this get bogged down by us trying to design the perfect solution. I am OK with a Power Saver option that comes at the cost of some reduced functionality. That doesn't prevent us from learning from it and making general improvements.

Reduced functionality can be rectified later. Given a choice between power saver and scrolling description, I will choose PS any day. Be honest, have you ever read that description?

[Hex]

@pjft said in Testers needed :: Power Saver features :: PR #172:

Also, @Hex : I'm pretty sure that if the video player is OMX Player you don't need to animate things, as the video rendering is a separate process. You only need to animate things if it's VLC. So that's a bonus, but I'd love to test that.

The video rendering is in different process but not everyone uses OMX. Animation is in GIF images instead of static box art. You could have GIFs of gameplay instead of video to reduce over head in processing.