Hi Calikw,

I know that 'lv10 Volume Control: Failed to find mixer" error well! I had exactly the same problem last year with a RPi and a JustBoom DAC HAT soundcard, and got so annoyed that I provided an Audio patch that was incorporated late last year to fix it! In other words... I think I can help you troubleshoot.

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

I see that you are running Ubuntu 18.04. I'm guessing you're running ALSA sound drivers, so I'd like you to do a couple of test for me to get to the bottom of this issue.

Firstly, can you please run aplay -L to get a list of the Audio Cards that ALSA recognises on your Odroid XU4. You should get something like this (based on my research):

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.)

This will likely show that you 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 ODROIDHDMI audio card. To do this I will need you to run the amixer scontrols -D ODROIDHDMI command, which will show you the names of the audio mixers on the ODROIDHDMI audio card. 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 Audio mixers as we'll need them later.

The next step is figuring out which audio mixer 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) 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.

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 Device.

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.

Now I've got something to ask of you. As you have an ODROID XU4 and I don't, can you please reply to this message with the output of the aplay -l and amixer scontrol -D ODROIDHDMI, so that I can see what the audio dcard and audio mixer names are, as I would like to submit a new patch for the ODROID, so that ODROID users in the future will be able to just select the ODROIDHDMI option from the list.

Cheers
Tminit

I have this curse...both at home and I work. I can't figure out a problem to save my life. Then, after I publicly make an ass out of myself by asking...the situation just clears itself up, as if there is some sort of cosmic force at work who wants me to constantly humiliate myself. This situation seems to be no exception. Without changing a thing, it seems to be working the way I want it to the past day or so.

@GreenHawk84 - I think the vector code for mame2003 and mame2003-plus are pretty much identical now.

One thing that has changed is instead of a vector resolution multiplier of 1, 2, 3, etc. it will be the actual render resolution under the Quick Menu -> Options settings.

If one of the core resolutions match the native native resolution of your monitor it should like decent. If you can't match the resolution to the display exactly then shoot for something close. I find using an HD display (1920x1080) that 1440x1080 looks decent for both horizontal and vertical vector games.

Try a vector beam width of 1 or 1.2 (Quick Menu -> Options) and if it still doesn't look satisfactory try turning on bi-linear filtering under Settings -> Video.

Some of the options require a core restart, basically exit the game and restart it.

@mitu said in Audio Problem:

sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel

Thank you :)

@hostolis
yep its gpu_mem=320.

Thanks for the reply.
Removing the line autospawn=no enabled PulseAudio again if I'm not mistaking.

Already tried the 3rd answer on that thread with no luck.

@Efriim Ive done some overclocking tests with PPSSPP and its core_freq and sdram_freq that make the biggest difference with performance. I ran "top" while running a couple psp games and I never saw the CPU go much above 50% so I dont think overclocking ARM will help.

@granderjoree There are several scripts that can work like you want

Here is a topic ... in your case use the multi-switch.sh --generic command
https://retropie.org.uk/forum/topic/21992/onoff-latching-switch

Also a good tutorial
https://retropie.org.uk/forum/topic/14537/tutorial-adding-a-dedicated-on-off-switch

or here a combo with reboot and poweroff
https://retropie.org.uk/forum/topic/21932/solved-how-to-make-a-momentary-push-button-that-exit-games-and-take-me-back-to-game-menu

@robhubbard86 https://retropie.org.uk/forum/topic/3/read-this-first and give us more info about your system

@mitu okay. Thanks.

You'll have to offer more info than that - what type/model ? Do you have a link to the model ? Also, did you try my suggestion about unplugging the HDMI cable and see if the main screen switches to the LCD screen ?

any can share the artworks, please? thanks

@mitu I never tried playing them with omxplayer from command line i am sorry still new to all of this. I been working on this image from scratch for a few months now and just when i thought i was done i went and updated the script and this is what happened. The videos do play in the gamelist previews just fine. its when the screen saver kicks in is when i get the issue. This image is for an arcade1up cab and i use the screensaver option so that in can just run when i am not using it.

@mitu I have tried disabling it, it still doesn't work. I honestly don't know what the resolution is for my screen, I think it's 720x480. I'm actually using a car dvd player, the kind that straps onto the back of a headrest. I'm using the composite output.
EDIT: Ok then, I just rebooted without touching anything and it's working fine, so thank you for your help.

@mitu thank you so much!

@mitu Thank you, I'll try this out and get back to the community.

@DreadfulDreamZz You need to change the controller type in both the Quick Menu's Options and the Quick Menu's Controls, then restart for the Quick Menu's Options changes to apply.

I use DualShock and RetroPad w/Analog as the Core's default options and controls, while I change to Standard in the options and Retro Pad (alongside mapping the D-Pad to the left analog) on controls for games that are digital-only or don't have analog controls then save the changes for that game specifically.

The spreadsheet listed on the wiki is fairly accurate and quick way to see which controller each game used.

https://retropie.org.uk/docs/Playstation-1/#game-specific-control-information

Only covers USA games though. Go to the PlayStation DataCenter for information on everything else: it's what the spreadsheet above was based on.

http://psxdatacenter.com/sitenews.html

Might be some inconsistencies between the two as the sheet hasn't been updated much since creation, incorrect info was seen on the site yet not reported (because I was already putting so much time into the spreadsheet), and it's possible something was incorrect on the site when the spreadsheet was made and is now fixed on the site.

One of these days I need to make the time to update that PSX documentation since it has so many problems such as directing users to do manual edits when things could be done in RetroArch.