@sugarfree yeah, it's kinda what I had in mind.
I'm not very practical about shell scripting, however from what I could grasp it seems that they're creating a whole new mapping script to create evdev mappings.
Since I was trying to create a Python script that was going to be launched when a ROM had been selected and didn't want to add more dependencies, I tried to use SDL2 as library in my script: however the naming a of the buttons are extremely different from what you could get from evdev and had to make an intermediary translator between evdev and Dolphin passing through the SDL mapping of that gamepad.
Their solution is far more practical. However I think one of their bigger limits is that the script essentially creates a Dolphin profile for each gamepad, basically a 1:1 mapping between the gamepad and the GameCube controls. For the GameCube I think it's a pretty neat solution. Different matter is when you try to apply the same strategy when mapping a Wiimote: one profile isn't enough since you can have more peripherals setups on a Wii.
Two things I could think of are: making a profile for each possible setup (Wiimote, Wiimote+Nun chuck, Wiimote+Classic Gamepad etc...) and asking at each ROM load which profile should be loaded to each player, probably with a nice whiptail+joy2key TUI; or creating on the fly a configuration after asking which peripheral setup the player wants.

@mitu alright thanks man! this will help me so much on this project!

@kazuuu
You could install a port from the setup script and it’ll create one for you at /home/pi/RetroPie/roms/ports. I would assume you could just create your own folder there but not sure if there’s anything else that would need to be created for it work? Installing from the script would make sure everything was made and you could always delete the other game after the folder was made.

@mitu Got it all working, took a little time to figure out it was calling bash scripts lol got it going now :)

The encoders should appear as regular joystick/gamepads under Linux, so something like pygame or python-evdev should be enough to read the inputs.

@mitu Interesting! Thank you very much for your feedback! I'll check how the library emulates the keyboard!

My fallback is a microcontroller to emulate the keyboard, if the software portion is too complex.

@buzz no, as i dont know if there is an issue with the script, or if there is a common issue with retropie settings that other run into with this using this script

PyGame has the pygame.event and pygame.joystick modules to process inputs.

Wikipedia has an elaborate artikle about Parsing and its meaning in Computer Languages.

RetroPie is based on Rasbperry Pi OS (Lite), you can install the desktop and then separately install IDLE with

sudo apt install idle

You can then find it in the list of programs in the start menu.

Try running it with full paths to both the python executable and your python script. No need for anything in runcommand.cfg.

One more piece of the puzzle...at the end of my script, if I remove the GPIO.cleanup(), then the light stays on.

But, in subsequent calls to my script, I receive a warning that the channel is already in use. It doesn't stop the code, but the programmer in me doesn't like warnings.

My question now is why does the cleanup function change the output of the GPIO pins?

After my genius idea to delete all stuff in this discussion, which only cause trouble and chaos, I figured out to do another attempt and post again. This is version 2 of the little app. The gui and commandline are streamlined into one app. The commandline options are flexible now and it supports a configuration file. Unfortunately in GUI mode only one patch file at a time is supported (but I think this is not a real issue and is a limitation in GUI only). And it can create output folders too. Updated the first post with all relevant information.

It started out so simple.

So with 4.4, most core and main packages installed, but there were a few that wouldn't. lr-stella, lr-pcsx-rearmed failed to build.

So in short - trying this is a mixed bag. Some things will build. Some things won't.
At least the raspberry pi image is a stable platform, but doing PC builds will always be a forever-forward moving target

Thanks. As soon as I posted here, I found this topic and with a bit of modification I was able to get it working. :)

@mitu no problem, I’m working around it with the other emulator for now. I’ve not tested what it’s like but I’m sure I can hold on! Thanks!

@WesleyBidsnipes said in I'd like the Retropie to power on our Xbox and switch to its OneGuide app:

@mitu It's been years since I've messed with udev... does that work with Bluetooth as well? We have one of the Playstation 3 wireless controllers, I think it's the Sixaxis.

It should work.