@flower4000 I explained in the previous reply what it means: if your path element contains the folder (i.e. /home/pi/RetroPie/roms/genesis/game.md), then remove the folder part of the path and leave only the file name (./game.md).

For future internet reference........

That 'lv10 Volume Control: Failed to find mixer" error is the cryptic message that Emulationstation gives when it cannot find the Audio Mixer on the selected Audio Card. You can find more information about that in the Sound Troubleshooting instructions I wrote on the Retropie website

To solve this, we need to figure out what the name of the Audio Card is, and the name of the Audio Mixer on the Audio Card, so that we're able to correctly reference them from within Emulationstation.

Firstly, you can run aplay -l to get a list of the Audio Cards that ALSA recognises. You should get something like this (this is for an ODROID):

odroid@odroid64:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ODROIDHDMI [ODROID-HDMI], device 0: I2S.27 dit-hifi-0 [] Subdevices: 0/1 Subdevice #0: subdevice #0

(You may have different results, just take note of the the HDMI audio card name and keep it for later.)

In our example we have an Audio Card named 'ODROIDHDMI', which is not an Audio Card type that is in the built-in list of Audio Cards in Emulationstation.

The second thing we need to do is figure out what the audio mixers are available on the audio card. For my example I run the amixer scontrols -D ODROIDHDMI command, which will show you the names of the audio mixers on the ODROIDHDMI audio card. Replace the ODROIDHDMI name with the name of your Audio Card you just got above. Based on my research you should see something similar to this:

Simple mixer control 'Analogue',0 Simple mixer control 'Deemphasis',0 Simple mixer control 'Digital',0

(Again, you may have different results, just take note of them and modify the command below as needed.)

Take a note of the names of the all the Audio mixers on that Audio Card as we'll need them later.

The next step is figuring out which audio mixer from that list actually controls the volume. On my Rpi Justboom DAC HAT, its the 'Digital' mixer. You will need to experiment to see what works for you. To test the audio mixer, you need to first make a noise out the HDMI, and then second use amixer to adjust the various mixers until you figure out which one changes the volume of the HDMI.

To make a sound out the audio device you can use speaker-test -D ODROIDHDMI -t wav -l 20 & to run the speaker test 20 times in a loop (and go into the background) (replace ODROIDHDMI with the name of your Audio Card you got in step 1). You quickly then run alsamixer to get a nice GUI for the ALSA mixer, which you can then use to adjust the various audio mixer devices on the audio card

At the end of that testing you should know the Audio Card name, and the Audio Mixer name on that card that controls the volume.

For our example, lets say the 'Digital' mixer on the ODROIDHDMI is the one that controls the volume.

So now we need to tell emulationstation how to use these new cards.

As mentioned earlier 'ODROIDHDMI' is not an Audio Card type that is in the built-in list of Audio Cards in Emulationstation. Luckily this isn't an issue for us, as the patch I added to emulationstation last year allows you to add a Custom Audio Card, and a Custom Audio Mixer (the audio mixer is called an 'Audio Device' in emulationstation).

To add a Custom Audio Card just follow these instructions and replace the <string name="AudioCard" value="default" /> line in the es_settings.cfg file with <string name="AudioCard" value="ODROIDHDMI" /> . This should allow emulationstation to successfully look for an use the ODROIDHDMI Audio Card.

To add a Custom Audio Mixer just follow these other instructions and modify the <string name="AudioDevice" value="Digital" /> line in the es_settings.cfg file so that Digital is changed to the Audio Mixer name you discovered above with your alsamixer testing.

Please note that if you change the Audio Card or Audio Device settings from within the Emulationstation GUI at any stage, you will lose your custom settings, and you will need to readd them in es_settings.cfg again as described above.

With the combination of settings above you should be getting sound when you go into emulationstation.

Hope that helps people avoid these problems again!

Cheers
Tminit

@Shadowkiller324
Check the pcsx.cfg in /opt/retropie/configs/psx/pcsx/
the first line should have the bios name.
I know you have probably tried this but update the pcsx emulator.

I wouldn't give up hope on the lr-pcsx, I use it for every psx game. Maybe one of the retroarch configs has a problem, like; system_directory = "~/RetroPie/BIOS" being something else
You could backup both /opt/retropie/configs/psx/retroarch.cfg and /opt/retropie/configs/all/retroarch.cfg if you have them, or if youre not attached to your configs then you could delete them. A new one will be generated and you could copy it as configs/psx/retroarch.cfg then restore the configs/all/retroarch.cfg.backup.

well that would take me almost a month to do every game. the favorites folder should list the whole title even if its in brackets. because all the other folders don't do that.

Through trial and error, I figured out how to solve the problem.

Assuming it was a permissions problem, I first reset all the permissions to the ones all files had at the beginning. As expected, my conf file did not run.

I then copied the default dosbox configuration file from ~/.dosbox/dosbox-SVN.conf and edited that with my custom setup.

Now everything works fine, though I never did figure out which permissions were broken.

Thanks anyway!

@SpudsMcToole I’m new to Amiga emulation... Have been trying this but it doesn’t load as seems unable to load the right rom

I had the same issue, with the same brand PDP controller as the OP but purple controller (vVendor ID 0x0e6f, product ID 0x02bd). I followed the instructions to recompile the driver, but it still wasn't getting picked up.

I then did full update as per https://retropie.org.uk/docs/Updating-RetroPie/ and it all came good :)

Regards
Dan

From the logs, yes, it looks like the detection works ok. You can try contacting the author and provide the logs, maybe they have an idea what is going wrong here - the RetroPie side (emulators) is not changed from what is declared in the configuration.

@GGrieves8322 asking for copyrighted content is expressly forbidden.

Read the form rules.

https://retropie.org.uk/forum/topic/3/read-this-first

@Lermatroid you didn't provide any information to help. No idea even which version of the OS you're running.

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

if you have no cec package, your OS is likely too old. you can install without it with some hackery but if your os is old, you probably want to upgrade.

I got it working with gambatte. This will work for me. Thank you for your help folks! I appreciate it!

@rkoster OK, thanks!

Yeah I wouldn't think so either, but it totally works with 6 button in Picodrive

@Sebiohazard Please add more info about your system - https://retropie.org.uk/forum/topic/3/read-this-first.
What application are you launching exactly ?

@Solid-One yes if you are already in retroarch systems the order wont change but when you exit and go back in it takes usb order as was the case in your situation.

@ucald4amarine one thing to add. All the sounds on the screensaver worked fine up to I told the arcade to do a random splash screen on startup.

@AssPunchMan said in PS3 Shanwan Controller lossed on every update:

Its possible fix this? update without loss the PS3Controller pairs.

The upgrade that broke the PS3 controllers - the Linux kernel - also broke other Bluetooth controllers and it's not under the project's control. It's a badly timed bug, but that's not something that happens regularly.
If you wish to not be bitten by such situations, then only upgrade the packages you need (for bugfixes or new features) and skip the OS and driver upgrades.

@mitu

Thanks for reply. From retropie website. I have been tinkering alot I've messed it up myself somehow following various guides for controller settings in mame. I might have to just start again with new image.

I would recommend the standalone Fuse emulator for keyboard use. Has a lot more functionality if you don't want to just play games. Eg. Typing in code, saving things etc.

@TPR Super late reply, but this is one game that is known to fail if you have SIO acceleration turned on. Try turning it off and see if that works.