i think i found a bug with the vram limit and Volume sliders

ckp

@pjft , here is a video while using my usb xbox 360 and its dpad. if i use a usb buffalo classic gamepad it works fine.
https://streamable.com/ynr7v

pjft

@ckp Thank you!

This is extremely helpful. Let me see if anything stands out in the code, then, as it's not related to controlling the actual slider then (which was what the previous comments seemed to suggest).

ckp

@pjft , the slider itself works for me. if i press up and down like mad along with right or left it will move the slider a couple numbers as it passes through the setting. it think all this worked with my xbox 360 right after i installed the 4.2 image, but stopped sometime after, like maybe after i ran the all-updates thing.

pjft

@ckp I see. It might be a driver thing, but I'm surprised then by the variety of controllers it seems to affect.

I just tried it out on my end and it doesn't seem to act that way, for better or for worse.

Browsing through the code didn't raise any immediate concerns so far either, so this will have to go on the "to look into at a later stage" thing.

I'll add it to my list, though it'll be hard to nail down as I can't obviously replicate it. I'll reach out to the group here for testing - unless someone who suffers from it would like to take a stab at trying to fix it, though.

ckp

also part of the issue in this thread is the volume slider going back to 0 after it was set higher. I saw that too when I was trying to use 3.5mm speaker connected, but since changing that to HDMI, it keeps the volume setting.

ckp

which config file and setting has the volume slider setting in case i ever want to change it and not have to plugin a different controller?

paffley

It only started to happen to me when I updated the build to 4.2.8, all previous builds were fine. Hope this helps.

ckp

i also plugged in a second usb xbox 360 controller and that one has this issue also.

pjft

It should be in ~/.emulationstation/es_settings.cfg.

I don't know what exactly happened in 4.2.8, but if anyone would be willing to download this old build form March:

https://github.com/pjft/EmulationStation/releases/download/v0.2/emulationstation

and test it out, let me know how it goes. You can download it anywhere to your pi, you'll need to run chmod +x emulationstation before executing it with ./emulationstation. There's no need to overwrite your current setup, don't worry. Just make sure to exit from the current ES before running this.

I'm actually thinking now that it may be happening in recent builds because before the sliders used to be either at the top or at the bottom of the menu :)

I haven't checked, but see if that is what's happening. If that build has all sliders on top/bottom, try this one from April:

https://github.com/pjft/EmulationStation/releases/download/v0.1-ES-OMX-Apr17/emulationstation

Thanks.

ckp

@pjft , i just tried both.
the first one had a messed up ES gui but i still was able to try it.
the second one, from april, ran normal.
both files had only two items in Sound Settings (system volume and enable sounds).
the scrolling worked properly with both using my usb xbox 360 controller.

ckp

@pjft , let me know if you want me to try anything else.

pjft

@ckp Thank you, and sorry for the late reply here.

I don't think any further testing is needed at the moment.

Just so we're on the same page, if there are only two items in the menu, is it your assessment that it can be that things are working equally badly then, but the fact that there are only 2 items there masks it? Meaning: from watching your video, it seemed that the behavior was mostly that, when going from an adjacent item, " towards and through" a slider item, it would automatically keep moving to the next one(s) until it reached the end. Since we only had two then, it seems that we don't really know if it's working as intended because there was no problem then, or if it's because there are only two so we never need to "cross" a slider item - is that a fair hypothesis?

Or is there any specifically different behavior here?

Thanks!

ckp

@pjft , that does indeed sound like a fair hypothesis.

pjft

@ckp Thanks for confirming.

Following this train of thought, given that I can't really replicate this, you can kind of see what's going to come as a fix for this :P

Anyways, it's on the backlog of things to tweak and improve. Thanks for the help in narrowing this down, and if/when there's a build to test, I'll share it here.

I'm assuming you can manage in the meantime, and that this is not a critical thing, correct?

Thanks!

ckp

@pjft , i have no idea what would fix this. i would assume that it could possibly be reproduced with any controller that uses the same driver as the usb xbox 360, or maybe it's just the xbox 360. but several people have this problem, so i would hope it can be fixed sooner rather than later as this can be very frustrating until you find a workaround (which many people don't do). plus i think setting the volume is one of those things that almost everyone does (high exposure area).
as for me, as long as these settings can be changed from a config file, i can deal with that, plus i can switch controllers to my Buffalo as well if i want to change it in the gui.
thank you.

mediamogul

@ckp

maybe it's just the xbox 360.

It also seems to affect all Logitech controllers as well. I know it's going to be hard to find the root here without being able to replicate, but if it helps narrow the search window, this particular problem was introduced between 4.2.7 and 4.2.8.

ckp

i think @pjft is saying, even if it was only seemingly "introduced" since 4.2.7, it may have always been there if the menu before 4.2.7 only had two items in it, as the problem might have been masked by that fact. I didn't have the problem with my fresh 4.2 image, but I don't remember if the menu only had 2 items in it or not then.
yeah, i thought i read some other users with other controllers had the same issues as well. maybe all controllers that use xinput?

mediamogul

@ckp

maybe all controllers that use xinput?

Some Logitech controllers have a switch for xinput, but most operate solely on direct input and those are affected as well.

pjft

@ckp Can you briefly check if it behaves well on the "UI Settings" menu?

If so, I'll re-sort the components for now and submit something in the coming days.

<world's lamest fix>

ckp

@pjft , i think it works fine everywhere except the volume slider area and the vram area. i'm at work and not near my RPi, so I can't 100% confirm until I get home later, unless someone beats me to it and can answer first. i can say right now for sure that the Quit menu scrolling works totally fine as well as several other ES menus, which makes this so odd.