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

[edmaul69]

@alrdtakn1 have you tried with a different controller or a keyboard? I tested on 3 pi 's and had no issues.

[alrdtakn1]

So the dragon rise allows me to change the slider with no issue. It's just the Xbox wired 360 controller. I am using what i believe is the xpad driver. In Retropie Setup I only have the xpad driver installed it doesn't say I have the Xboxdrv installed. Don't know if that helps.

[ckp]

@alrdtakn1 said in i think i found a bug with the vram limit and Volume sliders:

"lvl: VolumrControl::init()- Failed to find mixer elements!"

I have the same exact issue. I get "lvl: VolumrControl::init()- Failed to find mixer elements!" every time I move to the Retropie menus and back. My 3.5mm speaker is working though.
And I have erratic controller scrolling in the vram and trying to set ES system volume (i can't).
Both thing only came up recently. I have been using the same 4.2 with usb xbox 360 controller and 3.5mm speaker the whole time. I have the Comic Book theme and have run all updates.
I can't even set the ES system volume because of the scrolling that has started, so I posted a different thread trying to find out if that setting is in a config file somewhere, but I'd really like to solve both these problems.

[ckp]

I switched from 3.5mm audio to HDMI audio and stopped getting "lvl: VolumrControl::init()- Failed to find mixer elements!" messages, but my ES scrolling is still whacko.

[paffley]

same issue here for me too, using 8bitdo controller - when on volume option and slider, it moves down or up depending on how you got to it.

[pjft]

I suspect it isn't something introduced recently, unfortunately, as that component hasn't been touched in 3 years:

https://github.com/RetroPie/EmulationStation/blob/master/es-core/src/components/SliderComponent.cpp

That being said, this report isn't isolated - I believe @TMNTturtlguy suggested that this was happening to him as well a few months ago using a DS4 on his end, though we didn't think much of it given that it doesn't seem to be easily replicable, nor that widespread. He used other controllers and it was fine.

I'm referring to the slider, not to the audio piece. Note taken. If anyone can share a small video, given that I can't replicate it on my end, and explain what exactly you're doing at each step so we understand what inputs you're pressing to make whatever's happening on the screen happen, it would be great so that others can follow.

I think there are some settings there for audio now, that may hopefully help you route the audio through the right port - or maybe you need to change settings on the /boot/config.txt file for that.

I'm not sure, as I only use HDMI audio.

Just suggesting that these two issues might not be related, for the sake of clarity and adequate follow through.

[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!