@nemecyys said in runcommand-onstart.sh pass data to python script:

Because im running this python script every time i run onstart.sh or onend.sh does that mean there will be LOTS of instances of it running?

On normal typical usage, no. The runcommand script calls the onstart one and waits it finish. The way you're invoking your python script in onstart also makes it wait the python script to finish.

Then, from what I'm seeing from the codes, I believe that there won't be lots of instances running.

With a Bash Script:
Would this also be the case?
Would i want to exit the bash after running and achieving the desired result?

There's no need.

*also, any links to some of meleu's coding goodness?

You can find links to some of my scripts on the "useful topics" post (link on my signature). You can find many other useful info there. ;-)

Oh, as @cyperghost said, we usually use this thread to talk about shell scripting.

By the way, you asked above and I'm not sure if you got an answer: the /dev/shm/runcommand.log file is deleted after a shutdown/reboot.

@jonnykesh At first I updated the standalone mupen64plus package from source but it didn't solve the problem so I updated the lr-mupen64plus package too.

In reddit someone wrote that it should work from now on with an update from the binarys.
I tried the mupen64plus update from binarys and now it works :D

@weyland can't you give me any advice?

Thank you for the information.
Now I am a bit wiser.

Yes, I just took a look at joy2key.py
https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/runcommand/joy2key.py
and it seems this was fixed already, it reads the user-mapping from Retroarch config! My system is just too old, 4.1, I will upgrade and test again.

@chipsnblip Thank you, that is exactly what I'm looking for.

Solution worked (remove the corrupted file) but since I have way too many mame games with different emulators set, this isn't really a file I wanted to "start over" on. Similar to what @jackyracer already said, just wanted to remind and confirm that in my case I copied the bad file to my computer, still opened (thank goodness), copied and pasted the cfg text from the old file to a newly made emulators.cfg file, and moved the new file back over in the same place. All fixed, but most importantly, no damage done.

@guest-001 The original poster had problems when starting runcommand.sh from /etc/rc.local, for which the solution was to change the /dev/tty to /dev/tty1.
There is no reported problem when using runcommand.sh normally, from ES, so I was wondering if you had a similar script set-up - especially since you were talking about noticing an error when a SSH connection was made before ES starts.
I don't know what might trigger your problems, but if you can reliably reproduce it from a RetroPie image, then share the steps necessary to get the error and we can try and see where the problem occurs.

@meleu That's okay! I've had a few issues specific to the DS4. I guess I'll just roll back to my last SD save.

You're welcome! ;)

Thank you for helping us and your work on that joystick-selection tool. :)

@herb_fargus I found that relying on sleep to properly time a 30 second video was getting mixed results so I modified your script a little to crop the video afterward for a more uniform recording length.

It requires that you install ffmpeg beforehand though.

#!/usr/bin/env bash system="$1" emulator="$2" rompath="$3" launch="$4" rom_file="${rompath##*/}" rom="${rom_file%.*}" mediadir="$HOME/RetroPie/roms/$system/images" tmpfile="/tmp/$rom-video.mkv" videofile="$mediadir/$rom-video.mkv" # Create videos folder in system's rom folder if [[ ! -d "$mediadir" ]]; then mkdir -p "$mediadir" dialog --msgbox "$mediadir created!" 20 60 >/dev/tty fi # Launch to record gameplay on RetroArch Systems. if [[ "$launch" =~ retroarch ]]; then eval "$launch" "--record \"$tmpfile\"" & sleep 120 killall retroarch # Crop video to 30 seconds eval "ffmpeg -y -t 30" "-i \"$tmpfile\"" "-acodec copy \"$videofile\"" & exit 1 else dialog --msgbox "Video recording is not supported for this system" 20 60 >/dev/tty fi

This is an old issue but, I have something to add. The button response, is only accepted right after the dialog/launching.png disappears. There is it seems, either a huge delay, or joy2key won't trigger until the end of the script. I'm guessing this could be fixed, its worth fixing. Additional features should be added to run command as well, though I can't think of any good ones right now.

@SonPluck /dev/shm/runcommand.log

It won't work if you remove the SD to plug in another computer because files under /dev/shm are RAM based, which means that they only exist while the raspi is on.

Glad it can be helpful for others!

Okay folks, I've written up a script to handle this exactly the way I described before.

It runs from the autostart.sh and watches /dev/shm/screen_manager.cfg for updates.
That way any other system process can create/modify that file and this script will respond by either starting the rom, or starting the dashboard.

Cheers!

https://github.com/coderkevin/mini-nes/tree/master/screen

I think it's worth to mention it was implemented. Those who like to update frequently may have noticed. The PR 1980 was merged, and now the "a button" means "A button".

Thanks to all the testers here!