@djmoss - I have the exact same setup as you (Pi4, pi2scart, mx7000). I have a couple of problems with overscan. Did you fix this through the config?
If too much OT perhaps we can take it in a pm?

Thanks! 😊

@dclegend By default, there are no onstart, onend scripts - it's an extension that can be used by users to add their own customizations.

Ah, the VIDEO loading screens, there they are. I set that to False and there we go! Thank you @mitu!

@n2185x the distortion I faced with lt-atari800 audio was resolved by applying the patch in this linked thread. The patch, to my knowledge, has not made it into the libretro core

I can confirm that applying this patch and recompiling fixed my audio quality and buzzing

https://retropie.org.uk/forum/topic/22530/lr-atari800-buzzing-sound/4

I posted this in a similar thread. This workaround works flawlessly for me and doesn’t require any editing in Retropie:

Go to the 8bitdo official website, download and install the 8bitdo ultimate software on your PC or Mac, if not already done. Plug the 8Bitdo Arcade Stick to your PC or Mac with a USB cable and make sure your selector knob is in “X” mode (top left of the 8bitdo Arcade Stick) Start the 8bitdo Ultimate software On the right, in the button mapping panel, beside RT, associate RS instead. Do the same for LT except choose LS. Don’t forget to synchronize the controller (icon at the top) before disconnecting the USB cable. Connect your 8bitdo Arcade stick to the Retropie either via a USB cable, the 2. To 4G stick or Bluetooth. Push the start button to get to the main menu (you might need another controller or keyboard to make the selections initially). Select “configure input”. At first, make sure your selector knob is selected to DP (middle selection) to associate D-pad up, down, left, right. This time the RT and RS buttons will work flawlessly.

@xMoJox12 and the rest of the info ?

The reason that Retropie isn't visible in the Win10 Network folder is due to the fact that netbios discovery isn't supported by windows anymore.
But it is possible to make samba shares again visible by the Web Services Dynamic Discovery Method.
I am currently using a little python3 script from Steffen Christgau on my Debian Buster NAS Server which makes WSD available und thus browsing Samba Shares much more conveniant.

https://github.com/christgau/wsdd

@mitu
Might it be possible to make this a standard addon to retropie ?

New cable has made no difference unfortunately. Another oddity is that when I scroll left or right through the emulators (and the transition style is set to 'fade') the red pixels all disappear and only reappear when I stop scrolling.

It's not the biggest issue, just would like to understand what's causing it so I can learn a bit more about it.

Does it work too ?
if i am using two Pro Controller as in Player 1 and Player 2

you could try http://adb.arcadeitalia.net/?search=mame&clone=0&filter_use_chd=1&driver_emulation=1

131 non-clone chd roms, you could also filter by mame version, this is default current mame...

@lostless yes lr-mame2003. Thanks, I will look that up. I was a bit surprised by this behavior and haven’t found much info on it yet

The 'device index' is the order number assigned by RetroArch for the controller, from list of the controllers detected. If you have just one controller connected, it will always be 1.

You can change the device index associated with a player from the Controls menu in the RGUI, under 'Port # Controls'. Given that you only have 1, you'll not be able to change it from the interface, since no other controller is present in the list.

Its like Retroarch is saying "Your N64 USB controller is a PS3 controller whether you like it or not".

It's not RetroArch that's determining the name, is the operating system that gives RetroArch the list of controllers with their names and characteristics. If your USB controller is telling the OS my name is PS3 Controller, this is now I identify myself, then this is what RetroArch shows.

@skoobie0000
Forgot to upload pics.
Pic 1
Pic 2

@chaosgamingx Not sure if those dirty upgrades are supported. Try again on a clean install of retropie 4.7.1 and also update the firmware.

@mitu Updating from source seems to have fixed it.