@jamrom2 said in Berzerk (STERN 1980) - MAME missed sound issues:

"They are about as close as it's going to get until another version is coded that has the modern updates of recent MAME versions for use on a Pi."

And i was pointing out that mame2016 has those modern updates while mame2015 hasn't. Did you miss that ?

Yet again there is absolutely no reason to use mame2015/mame2016 when latest mame is available, better integrated with the libretro api, and will perform just as fast most of the time.

@mitu
I think I must have hit the audio settings script module several times. with a healthy amount of reboots before it did anything in the way of successfully setting up ALSA

I'm still lost on this one. I know a clean install after installing retropie it did have audio, somewhere i lost audio updating and configuring pretty early on. I gave up on it several months back only to come back to it today.

I'm starting to lean towards it being some issue with argon one HDMI daughter board. But in the end it is working now, and i admit it is very unlikely that my "fix" did anything.

I just remembered I installed Kodi, from optional packages, somewhere in this attempt too. I feel really dumb, but at least there is always something to learn

@LeatherWing Thank you for the confirmation. The fix has been merged now.

That did the trick, uninstall IMP using the install script to do the uninstall.
Check all the sound was working as expected and it was
Reinstall of imp and I have audio goodness coming out of my Arcade Machine again :)

The volume control error is not related to the crash - it comes from EmulationStation.
Assuming you're using RetroArch and one of the NES cores to stream, the problem is probably in RetroArch's streaming module. You haven't added any of the info asked https://retropie.org.uk/forum/topic/3/read-this-first, so it's difficult start diagnosing what's at fault here.

@mitu Thanks! By total chance I just found the same thing. I don't know why that configuration menu is not mentioned in the retropie docs. Hopefully this post will help someone else in the future

@seatbeesate
I stand corrected, I did a fresh install again/installed safe shutdown script rebooted and seems to be working.

Going to try and reproduce to make sure maybe it was just the config.txt that got screwed up or something.

@hooknc Sure, let it be logged there.

@yewox50273 no, alsathread has always (at least, for longer than this issue) been used for pi3, which is why i was clarifying what @nesfredo was using. the change you refer to only made it the default on pi4.

it didn’t cause the skipping issue on pi3 in years past, so clearly alsathread/RA has had some kind of change causing the issue. we should bisect this to a specific retroarch commit (version is not specific enough) to find the culprit, but it would be tricky to do so since the issue seems to occur after a game has been running a while and is sometimes hard to spot.

@mitu Yeah, the Splash screen and menu aren't a huge deal, so I don't mind too much, I just wish I could figure it out. At this point I'm hoping it's resolved with a future update.

@dankcushions

Sorry I am replying so late; I have been running an experiment and got to the bottom of all my issues. Its the audio drivers that are causing my screen tearing. Currently I am running Alsa sound driver, ZFAST curved along with some pretty fancy overlays (As I stated prior I ran everything without them still with issues). I am noticing 0 performance drops. No audio drops or screen tearing. I just couldn't believe how well its running with the load placed on it. I have tried my other pies and low and behold; Alsathread was the cause of all my issues. I know you said Alsa is slower but I have been testing the most graphically intense PS1 games on playstation (Duckstation) and I am experiencing no performance drops. I actually just beat Final Fantasy 8! I know you had mentioned something about a driver stack which is probably the cause. Now I didn't try the n64 cores and probably wont as I will wont be playing those games on my pie.

@mitu I agree with you.
I was experimenting recently on pi0 and checked the RetroFlag "patch" for their GPi Case and it has by default disabled#dtparam=audio=on applied to the config .txt which causes the exact error posted
If the # is removed and reboot the sound is back to normal.

They should update their scripts/info rather users get troubles and need to apply cmdline alsa or edit sudo nano /usr/share/alsa/alsa.confand change

defaults.ctl.card 0 defaults.pcm.card 0 to defaults.ctl.card 1 defaults.pcm.card 1

This may be the same...
https://retropie.org.uk/forum/topic/29625/startup-audio-quality-is-bad-a-v-connectivity?_=1631181389467

[bump]

No one else? This problem persists for me regardless of what device I hook it up to. Originally it was hdmi audio but I now have it hooked up via the audio jack into an amplifier in my bartop and the same thing still happens.

@iandaemon I was transferring files via ftp on ssh (laptop on wifi, pi on ethernet). I’ve tried a different sd card and still the same so have ordered a new hdmi cable coming today to try that. If not I guess it’s the Pi itself. If I change themes I also lose the sound as well. I do now believe it’s hardware issue, still driving me mad! Thanks again for replying.