@h2805270 Really clever idea, looks a lot like Teletext, and clean layout too. My only reservation is that I'm not sure I'd want to spend too long looking a Teletext screen, as they're not the easiest on the eye. I was never a big user back in its heyday though, and others may well have a greater fondness and nostalgia for it.
Emulstation and kodi should not be services enabled/start by default at boot but rather autostart.sh start the first service by something like:
systmctl --user start kodi.service
if kodi is configured to be the first one.
To go further we can also think about replacing the autostart script by a retropie service which is enabled at boot time. At start, it launches the first configured service. At stop it ensures that emulstation and kodi are stoped.
If the service is run as pi user (which is more secure), the pi user must be lingered to enable autostart of the service at boot even if the user is not logged in.
loginctl enable-linger pi
systemctl --user enable retropie
All the services could be controlled, inspected, logged through the systemd tools
Not need for automatic login
It could be easily extended to any number of services not just 2.
I think it might be a good idea to add an audio configuration menu to RetroPie-Setup, which allows the user to select a default output device and automatically updates the ALSA config based on the user's preferences. This could also be added in EmulationStation to the RetroPie menu for easy access.
There is already an Audio settings menu in EmulationStation - in the RetroPie system. Right now it only works for choosing the audio output for the Pi's onboard audio - i.e. no USB/I2S sound card support. It should be possible to extend it to support other audio options.
The only issue would be the EmulationStation own Audio menu, where you can choose the Card and Device (volume control) - the ALSA name of the default mixer varies, depending on the audio card, but the list of Audio Devices is fixed (in source).
@p33te I built a bartop arcade machine. Like you said, building it was fun, really fun, but I don't have the space for it. The build process is what I'm really in for so although I at this moment think that some sort of small case and wireless controller would be smartest it doesn't sound very interesting. Right now I'm thinking about doing some sort of CRT build. That would add some extra challenge and the games we play on a Pi are all(?) originally meant to be played on CRTs.
@jrb555 My main pc monitor is at 1440p and I use RetroPie on a separate smaller 480p. Love those pixels, part of the charm, but only if its sharp image. Your tv or monitor have to scale up the 720p to its native 1080p and that is where blurryness comes. If you play on a native 720p monitor, the pixels will be sharp.
I think you're trying to use the mk_arcade_joystick_rpi one ? If so, then you need to install it first from the RetroPie-Setup script (it's in the drivers section of the packages) and then configure it - as described on the Github page of the driver. You can ignore all the installation steps and just look at the pinout and make sure you connected the wires correctly, then jump to the Loading the driver section.
There is no recalbox.conf file in RetroPie, that is part of the Recalbox image -a different project.