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

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.

pjft

@ckp Not a bother, no urgency whatsoever.

The UI Settings menu has a slider as the first element, that's why I wanted you to check if it works for you and you can change its value at will.

Thank you, no hurry!

mediamogul

The slider in the UI Settings menu being at the top seems to make all the difference. "World's lamest fix" or not, it appears as though it'll mask the issue until something better comes along. Thanks for taking the time to look into this @pjft.

pjft

Hi all,

I believe the proposed workaround has now been merged to the main repository.

If you can update EmulationStation from source and test, it'd be very much appreciated so you can confirm whether or not the issue is, for the time being, mitigated.

Thanks!

mediamogul

@pjft

Works like a charm here. You'd never know there was an issue. Nice job!

ckp

@pjft , I'm still pretty new to RPi. So to install from source to get this change, what do I need to do? Do I need to do the update setup thing first and then find the ES package and choose install from source? If I install from source, will I still be able to update to future stable versions using update from binary? Thanks.

cyperghost

@ckp There might be issues here >> Read ahead next 10-20 postings.
So wait after the issue is resolved or the binaries are available :)

ckp

@cyperghost , thank you. how do i know when the binaries are available?

cyperghost

@ckp Just check the updates for emulationstation - binary update - daily. I can provide my compiled binary in the thread I've posted. There is also intruction how to do that manually but you need SSH access and must paste/copy some commands - Read this thread and post results.

pjft

I've reported the issue, so hopefully we'll have a solution soon. We are starting to run out of memory when compiling.