@retropieuser555 I notice in your picture that the User 1 Device Type is set to Sinclair 1 Joystick. I tested this setting and Hen-House Harry moves to the left if I press the B button and to the right if I press the X or Y button even though I have nothing mapped to those buttons. Could you try selecting the User 1 Device Type to the Cursor or Kempston joystick?

@fabthegamer LOVE the cabinet! Used to play the game competing against a friend (a great game for deliberately trying to kill the other player)

@squishykoishi said in Auto mount USB HDD doesn't mount, HDD does work:

As for /etc/fstab I'd probably ask something pathetically stupid about it, and would rather not waste time for people who need to answer more important questions/fix bugs or whatever :p

My local LUG had a motto - don't just ask to ask, ask directly. That's why the forum (including the Help & Support category) exists.

As with the old controller, there's no 1:1 mapping between the cables/wires and the actual buttons - you can't wire it directly to the GPIO and expect it to automatically work, you'll need a driver.
When you're talking about the 'new' NES controller, do you mean the one for the NES Classic Mini or the one for the Switch ?
The controller for the NES Classic Mini has the same port type as a Wii (U) Classic controller - see here and here for details.

@wmarcio thank you so much , read my last post.

@RetroDuck Re-read the forum rules - there's no download links to ROMs or other copyrighted material.

@greengrounds but yeah put the power supply into that hub. Then the power supply is giving power to the controller and the pi.

I remember a similar post - after the 4.4 image was released - mentioning that DInput behaves differently and switching to XInput made it work.

@Protocultor
Protocultor for President :D
Thank you very much, it works. Now the only thing left I need to know is, can you change the deadzone amount of the left analog stick somewhere? I know you can change it in the option for ingame movements but it doesen't apply for the menu navigation and when I move up and down it often register a left or right movement and messing up my settings.

UPDATE: Nevermind I found the settings in the config folder inside zdoom.ini

Running the update appears to have fixed the problem for me. Tested real quick with Super Bomberman 3 on SNES and Crash Team Racing on PSX and all four controllers are working. Powering off a controller while EmulationStation is running no longer causes it to crash or freeze.

I'll keep an eye on this and report back if anything changes.

I've just read this on the mamedev wiki... "The original controller for 720 Degrees was a joystick that was hardware-limited to only travel along the outermost edges in a circle. The internal mechanism for reading this control was similar to a spinner except that it had the additional benefit of knowing which direction the joystick was pointing. Because this knowledge is an important aspect of the game, the current emulation of the controller maps an analog joystick to the underlying controls instead of a spinner." I've never heard of this before! That would be hard to emulate. So does this mean that the system doesn't recognise when the joystick is central, so you always have to be facing in a direction for the game to work? I'm guessing you would have to set the controls in mame to allow this, but you wouldn't need to configure it as a spinner. I'm pretty sure your left right up down system would work as normal.

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.