Oh sorry misunderstood. Well, it's a little bit all over the place. Before overclocking, one TV I tried had 720p. It had occasional audio cut outs. Another TV had external speakers and had a resolution of 1920x1080. That one had terrible audio drop outs that lasted the longest. The last one I tried was at 3,840x2,160 and was working better than the other two. The audio dropouts were there but they didn't last as long.

Since that 720p TV still had audio drop outs, I don't think that could be the solution. But I haven't tried changing the resolution for any of the TVs so I'm not 100% sure.

@omen_peter oh yeah, you right. I thought he meant that it literally didn't work, despite typing in "raspberry" and hitting enter

Yeah, that is the page where I read about the workarounds :) I was a bit unsure if there were other differences to think about, but it sounds like it is safe to go for a multiplayer adapter. Thanks for the info.

Thanks yes I'd already done that. :-) I also added lr-mupen64plus and made a couple of tweaks in the audio settings there, such as setting latency to 128 rather than 64, and setting the resampler to lowest rather than lower. Seems to take the edge off lag sometimes.

@Undistaya Glad I could help :)

@mitu than you so much. so all these roms are to heavy for the pie...time to free resources..
thanks again!

@Link You can create a folder for the ROMs on the /media/usb0 partition, copy the contents of /home/pi/RetroPie/roms to it, then symlink /home/pi/RetroPie/roms to the folder on the HDD. Make sure you create a back of /home/pi/RetroPie/roms first, just in case.

Or you can bind mount the folder over /home/pie/RetroPie/roms with something like

mount -o bind /media/usb0/<Folder_name> /home/pi/RetroPie/roms

@omegal98 it did not work but tried emulationstation that worked until I exited out of a game and it brought me back to the retropie login. Is there a command to stop that from happening I appreciate your help.

@beahrdog Please don't revive year long posts, open a new topic instead. The Nespi cases are notorious for power problems, even if your power source is ok. If you have problems with the PI in the case, but the problems don't occur with the PI outside the case, then you know where the issue is.

@mitu worked great! Speakers are installed and volume sounds great! Thanks!

@dankcushions What I did now was putting all my arcade ROMS into the arcade ROM folder, instead of spreading them over the 2 different folders/emus I mentioned before.
Then, for those games requiring Mame4All I set that emulator for the individual ROM via the configurator (press any key on game start-up).
For the others I chose lr-mame2003 via the default emulator value.
Now all my arcade games are running fine out of one and the same (arcade) folder and most important, now for all games I have a (one and the same) configuration UI (press Tab) - perfect.

@administrators tried to edit this title's post and mark as solved, got this popup error in the editor:

"Post content was flagged as spam by Akismet.com"

Please mark this post as [SOLVED]

@Amplifuzz

You don't really need a ton of custom video modes, since the resolution stays the same, and you only have seven or so different refresh rates at maximum to deal with. Two config lines like "lcd_native_res=1920x1080" and "lcd_range=50-60" or whatever the monitor supports would cover it.

on groovymame, sure, but raspberry pi only understands discreet videomodes. you have to tell it when you want to use a new videomode. in retropie, using the runcommand, you would have to add each videomode to the list, and when selected they would have to call the api command i linked above (since these aren't videomodes in the raspberry pi's limited list of videomodes)

I'm afraid that the whole 'snap to the closest available refresh rate once the native ROM refresh is detected' part is best handled by the emulator itself, as well.

agreed, but for that to happen someone woudl have to update CRT switchres (or something similar) in retroarch such that it can communicate with the pi's custom videocore API calls (see the link above).

i'm told that you can get crt switch res to work with pi, but only under X. we don't use X in retropie. there's some info on this on the (huge) crt switch res thread over at libretro: https://forums.libretro.com/t/retroarch-native-crt-support

@trumad i think at this point it would be a good idea to just start a new thread (filling out the info requested in the sticky), and just put a reference link to this [dead] thread.

going into a bit more detail on your setup, what you're tried, etc. can also be helpful when troubleshooting something like this.

best of luck.

I was able to trick Skyscraper into recognizing there are subdirectories in my \RETROPIE\roms\mame-libretro folder by including at least one ROM file in the base emulator ROM folder.

Maybe this will work with your issue.

@Chewie said in No Scrapers Are Working:

I have no clue what this means

It means the ROM file has not been registered in the scraper's site so the site doesn't know which game it belongs to.

@dreaded_walrus Please use a meaningful title when opening a topic.

Thre is not root password in the RetroPie image for the PI. The pi user has sudo privileges, so no password is needed if you prefix your commands with sudo.
What is the command/action you're trying to acomplish ? Move a file, edit a file, run a comand, etc. ?

@MarkHighPeak Can you add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ?