Based on this output, I think you'd need to set in EmulationStation the Audio Card to Device.

To get the name of the mixer (volume control), run

amixer scontrols -c Device

and choose the 1st entry and set it as Audio Device. For instance, in my case, the USB audio card is named 'Controller':

amixer scontrols -c Controller Simple mixer control 'PCM',0 Simple mixer control 'Headset',0

I would use PCM as the AudioDevice settings in ~/.emulationstation/es_settings.cfg:

<string name="AudioCard" value="Controller" /> <string name="AudioDevice" value="PCM" />

This should fix the audio not working (or the volume slider rather) in EmulationStation.

For Amiberry, I'm not sure why it's not working - maybe it's trying to use the 'default' card and it's not working ?

Try following the advice here and create a /home/pi/.asoundrc file containing

defaults.pcm.!card 1 defaults.ctl.!card 1

@iandaemon Mainly the file size that I'd save in using Gifs rather than a video format - oh and I could make my own backgrounds and animations easily myself too.

alt text

@mitu said in N64 Controller Setup - Inconsistent Documentation:

@busywait said in N64 Controller Setup - Inconsistent Documentation:

If you don't have a 'retropad A' button defined, of course it's not going to work in the menu . My remark was:

How the button is mapped to the underlying core doesn't matter for the menu (RGUI or otherwise).

I agree, but the reason that I don't have a retropad A button defined is because the core doesn't use it for it's logical function in the mapping. I could have had both [N64 "A" and RGUI "A"] if the core used different bindings.

Obviously this is a minority problem for people trying to use pads without the full set of retroarch inputs, and I can still navigate the RGUI using a keyboard in my case :)

@venkman383 please provide more information

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

Please give an example of a file that doesn't work. A logfile will be useful. Which ROM files did you install and to where? Which lha files are you trying?

@g30ff YES! That was the best advice someone could give me at this moment! It worked! Big thanks!

Edit: Regarding the shell script. Should have quoted...

@dankcushions
Yeah, I checked the sites myself and had no issue. I don't see how it could be the connection on the Pi, though, since the wifi works for anything I do via the GUI - both the main Retropie interface and the setup interfaces. Scraping, updating, etc, all works until I go into the terminal. I'll probably have to seek help elsewhere as I suspect that's still outside of your ability to assist.

Thanks for the help, though. I at least now know some stuff to look at should other problems arise in the future.

@fadangalini had one as a kid as well. Virtua racing and Virtua fighter are worth checking out.

Another option:

I use a bezel that I made. Get asteroid.png and asteroid.cfg from here if you're interested. https://github.com/busywait/retroboxes/tree/main/overlay/Asteroids

I've tried lr-mame2003-plus and lr-fbneo. They need different ROMs, get the correct one from a relevant romset.

lr-mame2003-plus has more control over vector lines, but the screen is slightly squashed in height (black unused space at the top and bottom). The screen shot below shows that problem.
asteroids game with a bezel running in RetroArch

You can scale the picture to be a little taller, but then motion doesn't look as smooth. So, I use lr-fbneo.

With either core I used with the "normal" resolution, and integer scaled 2x to fit my bezel in the retroarch video options.

I don't use a shader. I do run with video_threaded = "false" to reduce latency by a frame. (I can't remember if I tested if that actually made any difference! I assume that it's taken away 16mS of lag).

@ericsnis said in Remapping buttons for runcommand.sh:

Is there a way to remap the buttons used for runcommand without messing up the mapping for games?

runcommand will use the RetroArch configuration file of the gamepad. If you didn't generate one - it's automatically done when you configure the input in EmulationStation - it doesn't which buttons are A/B to enable them in the launch menu.
Since you copied the ES configuration for input, and didn't run the input mapping dialogue, the RetroArch configuration file hasn't been generated - hence the missing mapping in the launch menu of Runcommand.

@scrumpydaniel

try power up the speaker via usb within the pi4 or by some audio converter from hdmi to 3,5 jack audio and have the audio setting of pi4 to hdmi and not 3.5 jack.

I thought I'd tried that option and have just realised why it didn't work. When you change the Port 1 controls to "Keyboard + Mouse", you can't actually assign any of the controls. You have to go back to the main Controls menu, THEN go back into the sub-menu and assign the ones you want.

The guide should still apply, though I'm not sure using F2FS would yield any benefits over other widely used filesystems (especially if you want to connect the SSD to another system/PC).

@0sabotagecopper said in NES Seg Fault:

Below is a verbose log of a launch using the lr-mess emulator.

NES emulation in MAME is not great, and that's a bit of an understatement, so i would really recommend to avoid it.

@zappyowl2482 those instructions are correct and current for official retropie. we do not install third party builds like those on twister os.

@mehmethakan please fill out https://retropie.org.uk/forum/topic/3/read-this-first

@jimmyfromthebay well, a verbose log would tell us what it is.