Can you please add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ?
How are you trying to wake up the system - keyboard, controller, etc ? If you're running a screensaver, consider disabling the power saving option in ES.
For the audio part, try adding audio_pwm_mode=2 to your /boot/config.txt and see if it improves the sound cutting part.
@nevsan It's a neat little feature, like a mario coin collection left to right and a space invaders shot up and down.
Personally I totally despise GUI navigation sounds. They just grate on me. I know I'm scrolling... They are the first thing I turn off in the likes of Kodi, an amazon firestick, a steamlink...
@pjft I guess I could try that. It was working fine till yesterday so version 4.3.1 was good for awhile.
What version are you thinking I should try?
I have been thinking about it and what might have happened but I don't know how to fix it is.
I had the videos playing for screen saver and the audio turned off for screen saver only. Let it run that way for a few hours every so often. Sometimes I would hear sound jump in and out. Like a noise from the other room. Then yesterday I noticed I didnt have any sound.
The reason I had it on so often and wasn't playing is I'm a designer working on a theme. Was wondering if this could be the source of the trouble?
Since no one chimed in I blew away my setup and started over moving step by step to identify where the audio broke.
The power button configuration was the culprit. The script worked for the power button perfectly powering on and off the Pi but killed audio from the Mifiberry AMP 2. Upon further researching the reason behind the issue was that the Mifiberry AMP 2 uses several GPIO pins to communicate between itself and the Pi3. Of course one of which is the same pin the power button configuration script uses.
I have since tried to modify the script to use a different GPIO pin (GPIO 5, pin 19). The script works to power off the Pi but not on. Further research told me that the script doesn't power on just off and that I can solder in a header or use pins 5/6 (GPIO3/GND) to power on the Pi. Given the Mifiberry, it looks like my only option is to use the header which is doable but I'd prefer to have only one power button that performs both power on and off functions.
Is there a way I can meet my goal via script, resistors, etc given what I have to work with, a long button press for off maybe? I thought about wiring the button to both the reset header pins as well as off function pins (19/20) but don't believe the Pi will know what to do with that input.
Old topic I know, but I created it so live with the bump! lol
So my 16-year old cousin brought his Pi Zero I built for him over to his buddies house and the sound wouldn't work. Regular consumer-style like 50" flatscreen (he didn't remember the brand/model), with the same cable he uses at home. After my other cousin had an issue with sound on an older ~32" Sony I've used hdmi_drive=2 on all of these. Any suggestions on what to try?
The elinux wiki says to also try adding:
but I honestly have no clue what those do and haven't seen them referenced anywhere else...
@Wizardling I assume it's just a rounding issue from converting the saved alsa value to a percentage - just ignore it :)
Yeah, but each visit drops the audio level another point. It's not just once. It is every visit, forever, after the initial change. If one installs RetroPie and never changes the default 75% audio level, this doesn't happen. But as soon as one changes the audio level, it drops every single visit, thereafter.
Or if you're saying ignore it regardless of all that, well, I call this a fairly serious sound settings bug. Nothing should be altering settings on it's own every time the user visits settings :-)