@Grumbles I've found that any images over 1000 pixels either vertical or horizontal either won't load, or are slow to load. The sweet spot for HD resolution and speed seems to be in 750-850 range. Don't use 300 dpi, drop it to 144 or 72 dpi as well.

I've done this to all of my images and I'm happy with the look and load speed on a 55" screen.

One last one .. make sure the size of the file is not over 900k. Reduce it to around 600-500k as long as it doesn't screw-up the quality.

I'm running a Pi3b+, a highly modified version of Eudora with custom system pics and logos if you need to know

@james-milroy apologies again the delayed response, been a bit snowed under with work. At the weekend I finally found time to have a play and document it this time.

I thought I would try and start again, and document the process, and rather maddeningly sound worked with less fiddling. Here is the process I went through, my setup:

Picade 10”, using the USB-C Picade X HAT on a Raspberry Pi 4B 4GB

standard setup where a simple speaker in the Picade case is connected to the Picade X HAT via the 2-wire speaker connector on that HAT

In case it matters I have the USB power for the screen in the top USB 3 port

I also have all my ROMs on a USB stick in the bottom USB 3 port – which made starting from scratch a lot easier.

Using Raspberry Pi Imager I installed RetroPie 4.8 (RPI 4/400) image on a 32GB micro-SD card.
The Picade booted up this clean image fine, and the 10" display worked straight away (no commenting out HDMI lines in config.txt required).
After the initial storage resize reboot, it was at the Emulation Station configure input screen.
Using a USB keyboard, F4 to drop to the command line and run the Pimoroni Picade X HAT install script:
curl https://get.pimoroni.com/picadehat | bash
Then sudo reboot
This then finished in Emulation Station showing a black screen when the reboot finished.
Blindly press F4 again to drop to the command line and re-comment out the hdmi_force_hotplug=1 line in config.txt, then reboot again.
This time the Emulation Station screen showed correctly after the reboot – something must have changed as my Picade used to need that HDMI hotplug line enabled.
Sound is not working at this point, but feel free to configure the joystick and buttons now in Emulation Station.
If you were to run alsamixer from the command prompt you would see the familiar error about the hifiberry_dac soundcard not having a mixer, and no volume control being available.
Instead, just start an emulator from Emulation Station by selecting a game.
Sound now starts, at a painful 100% level.
Drop back to Emulation Station.
Open the menu and set the sound settings to:

Volume: 40% or your preference Audio Card: Default Audio Device: PCM OMX Player Audio Device: ALSA

Audio now works, and the volume persists over reboots etc. Dropping to command prompt and alsamixer shows a PCM volume control. Basically it’s working, and I can’t work out why it wasn’t working previously and why I had to fiddle with .asoundrc etc.

Again, in case it matters, the bootloader and eeprom on my Pi is up-to-date for default branch:

CURRENT: Tue 25 Jan 14:30:41 UTC 2022 (1643121041) LATEST: Tue 25 Jan 14:30:41 UTC 2022 (1643121041) RELEASE: default (/lib/firmware/raspberrypi/bootloader/default) Use raspi-config to change the release. VL805_FW: Dedicated VL805 EEPROM VL805: up to date CURRENT: 000138a1 LATEST: 000138a1

Finally, with sound now working I brought everything up to date, and sound still works fine:
sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get autoremove && sudo apt-get autoclean

I do hope this helps, and works for others. Very best of luck! I'll keep my fingers crossed that mine stays working as it is now!

@sirhenrythe5th
After i update retropie it then comes to a yes/no screen asking "would i like to update the underlying of the os packages (eg kernel etc)
I select no and then it take me to this
1.JPG
2.JPG
and then fail at the end

It's probably too much to ask as that's 100s of projects and updates to curate. i would guess that every day there's at least one update to a bit of software in retropie.

just 'watch' the relevant projects in github. eg https://github.com/RetroPie/RetroPie-Setup to receive update messages.

updates are also summarized in each retropie release: https://retropie.org.uk/news/

Are the speakers connected through the audio jack? I'm not sure which one but do you need to/did you already select a different (besides HDMI) audio device in EmulationStation > [Start button] > Sound settings > Audio settings > Audio device?

@sleve_mcdichael ah - I doubt it very much! Thanks for pointing the way, feeling a bit silly now.

@tjuk though I fear that @mitu may be right here, two tests for that come to mind: 1st what happens if you just plug in an unconnected cable and 2nd have you tried any other OS besides retropie (Edit: ok, strictly speaking RetroPie ain't an OS - but I'll guess everyone understood what I meant :] ) ?

Hi, is anybody having a problem installing this? When I run "sudo ./setup.sh install" I get the statement: "sudo: unable to execute ./setup.sh: Permission denied"
Capture.JPG

@mitu said in Retropie 3.5mm Jack No Sound:

dtoverlay=audremap,pins_18_19

VOLUME!!! Thank you

@mitu nice one... My concern is about heavily customized setups (for example mine) where I have one directory per Arcade manufacturer (although they use the same emulator, they have a different theme setup for example), and directories do not necessarily match the system name, but I guess I can consider that as an edge case.

Thanks Again!

If we're talking about emulated games, the date/time of the emulator may not have an influence on the RNG the game implements - most of the emulated systems didn't have a real time clock or the concept of the system date/time.

@Addison it all depends on how the game implemented the RNG, some of the games relied on the RAM contents to initialize the RNG. On an emulator, the emulated RAM may get initialized to the same value (zero for instance) and thus there's no RNG at stake. Some emulators cater for this kind of situation with options - for instance Snes9x has a Randomize Memory option for this kind of situations, others may initialize the RAM directly with random values to prevent RNG failures.

Funny enough, some games' RNG can be manipulated, a technique used in speedruns to get a predictable set of events/weapons/etc. An example is below, where the runner saves and resets the game during startup

@mitu
thx it works.

Ps.
I checked. Can also just create normal file .cfg and edit with notepad++
custom-(theme name).cfg

:)

Some of the palettes are built-in into the emulator and they don't have a file on disc associated. Only when you choose custom as the core option you need to provide a palette file in the BIOS folder.

The name of the file depends on the emulator, if you're using the default NES emulator (fceumm), then the file must be named nes.pal, see https://docs.libretro.com/library/fceumm/#custom-color-palettes. If you're using the nestopia core, the file is named custom.pal.

@yewox50273 no, alsathread has always (at least, for longer than this issue) been used for pi3, which is why i was clarifying what @nesfredo was using. the change you refer to only made it the default on pi4.

it didn’t cause the skipping issue on pi3 in years past, so clearly alsathread/RA has had some kind of change causing the issue. we should bisect this to a specific retroarch commit (version is not specific enough) to find the culprit, but it would be tricky to do so since the issue seems to occur after a game has been running a while and is sometimes hard to spot.

@sirhenrythe5th No worries, the issue was resolved as mame2003plus worked with all the games.

I just upgraded to a Pi 4 and Atari 5200 works now!

However I still get segmentation faults in runcommand on a Pi 3.

Both are running Retropie fully upgraded with the latest lr-atari800 binary.

So I guess if this is happening to you, ditch the Pi 3 like I did.

Please add some actionable info to your post - what games/emulator are you using ? Also, when asking for support, please include the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.