@lolkthxbai just got this message as well. I have sound before EmulationStation boot in my video splash but nothing after that. Not in the previews and not in retroarch

@yfzdude thanks... will try them out.

@MeltedPineapple hello! I suspect you're having an eXoDOS version of the game. @mitu is correct in saying there are parameters to help you configure your setup. To have the dosbox.conf (or any conf file or commands) you did use to launch the game would help a lot! Off top of my head here are some parameters you can use to run the game:

c:\> monkey.exe r <- enable Roland MT-32 (requires specific files and setup) c:\> monkey.exe i <- enable internal speaker c:\> monkey.exe a <- enable Soundblaster and Adlib (most compatible) c:\> monkey.exe v <- force VGA

You can use a combination as well:

c:\> monkey.exe a v <- enable Soundblaster and VGA

Search for Monkey Island reference card for DOS on the Web to get more keyboard shortcuts and interesting info. The most interesting shortcut for you would be Ctrl + S which turns on / off the sound (only working for Internal Speaker though).

Note: my recommendation would be for you to give a try to ScummVM for anything Lucasfilm games/LucasArts related. Very easy to use and you'll get the best experience possible. Check Retropie docs here for installation and ScummVM wiki to properly configure the games.

@dankcushions Case solved. The log obviously does generate and the roms do work. It was just a bit embarassing mix-up on my end regarding file formats.

You missed my other question:

@Clyde said in Sound Problem acter the last update:

Installed from the official Retropie image or a third-party image?

I.e. did you download Retropie from https://retropie.org.uk/download/ or somewhere else?

@t3stin I don't know, I use a stock config and this is not set on my system. If you just want to test the sound, there's a command line speaker-test command you can use. Or download an .mp3 and play it from the command line with cvlc.

@mitu that worked! Now I'm getting an error "1v10: VolumeControl::init() - Failed to attach to default card!" But the sound is working, so I dont know if it's a big deal or not.

@Gazmeister said in Emulator sound issues:

Retrodroid, an odroid xu4

Thats tough, I don't notice a lot of XU4 users here, and I don't know anything about them. XU4 forum is a better idea.

Perhaps updating the kernel, to the latest.

Is there any sort of config.txt for the kernel options, like as on the raspberry pi? Usually for overclock, or hdmi configuration, also kernel overlays modules.

there is a uboot.ini for XU4, and I didn't look far into it, there may be some configuration here that simply works

How long of an hdmi cable just out of absurdity? I think a very long 50ft hdmi could have problems like that. TVs okay probably, but maybe there is 4k upscaling(?) interference, switch it to a "Game" or "Graphic" mode if you already haven't. Maybe disable 4k options if possible.

@eggman I think you can force a specific order for the sound cards through configuration, described in this Archlinux wiki page. You just need to know the name of the sound kernel modules loaded, but that's easy - you look in /proc/asound/modules:

pi@retropie:~ $ cat /proc/asound/modules 0 snd_bcm2835

This means the 1st soundcard (index=0) is controlled by the onboard PI sound chip, with the kernel module called snd_bcm2835. Your output will have 2 sound modules loaded, so you can note the name of the USB wireless sound kernel module and create a file ( /etc/modprobe.d/0-sound.conf) with 2 lines:

options snd_bcm2835 index=0 options <NAME_OF_THE_2ND_SOUND_MODULE> index=1

Ideally you can try to replicate the problem - sound routed to the wireless card - then see if applying this configuration fixes the problem.

@dlesko250 said in Sound stopped working for just Arcade games in Arcade rom folder/all other rom types work.:

it's mixed rom set in the arcade folder. It's not separated into MAME or FBA.

So, you're launching multiple emulators from the arcade directory and they're all without sound? Narrowing down which you're using is still important. Keep in mind, there's something like nine versions of MAME to choose from when using it the way you are and three versions of FBA.

@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?

@simonster I can try that, I'm tempted to just rebuild my retropie system and see if that fixes the problem since I've already sunk hours into troubleshooting this and could have rebuilt/restored everything in 1/10 the time :)

I would think if anything retropie running on OSMC would be slower since OSMC is still running in the background and using up CPU/Memory.

I think it would be useful to note that the menu plays noises perfectly and the video goes extremely smooth.

I have this exact same problem months later, was this ever resolved?

@r3d007 said in Volume control init():

Volume control init: Failed to find mixer elements

try changing the audio device in Sound Settings from the emulationstation menu, you may need to reboot between changes. refer to this guide in the wiki for further troubleshooting steps: https://github.com/RetroPie/RetroPie-setup/wiki/Sound-Issues

i would also test a different HDMI cable as well

Im beginning to think its an issue with either retroarch or raspian itself on how its reading streamed data from a disk. It seems to happen when trying to read music or a video. Not only am i getting pauses and stops in pix games, but also sega cd games. hmmm

@kirk glad to help. Keep your other settings that you did too. All 3 keeps this as universal to tv's as possible.