@pjft I did it just now and I can confirm the problem is solved, OMX is working fine, same behaviour as VLC.
There's still a volume difference between each single videosnap, of course because every video has its own volume.
I don't know if it's possible but it could be great to have an general normalise audio function used to keep the volume level more or less constant between each video.

I'm sorry about that. Was trying to find the right spot to ask this question. Will check out OpenELEC.

Does this setup allow for N64 Hi Res textures?

well, my pc is connected to the tv, and I can use the wireless keyboard from the "unresponsive" state to get to another console and login there on another console.

What other tools should I check?

@used2berx said in [Idea] Game Manual viewing in ES:

@mitu OOPS....

I meant a PDF to PNG, or a PDF to JPG converter.

I believe I found what I was looking for. Have to do a few more tests. It was something called "PDF to Image" that just one dude made and he offers it for free, and it's portable so you don't have to even install it.

I was able to take a 26MB PDF of a magazine and turn it into over 2GB of PDF files using 600DPI. Way overkill and not what I'm looking for. lol

I'll have to try out the 300DPI and 72DPI settings and see what happens.

calibre is a good one, if that doesn't work out

fixed switching hdmi group and mode to one i wrote in original post.

I had that happen once after an update. I had to tell it to uninstall retropie and then reinstall it. it all worked fine after that.

After using ClrMamePro and updating my ROM set... and finding out that i didn't have to go through all of that....
i already had the correct ROM set version. All i had to do was copy over dkong.zip and then ReStart EmulationStation.
Donkey Kong showed up and played just fine after that. Thanks for all the Great Advice.!!!!!
Later, David, ThunderBoyDavid

@mitu

Thank you! Your advice was golden! Working with Qtcreator is so much better.

@hex Well, it is under Advanced Configuration in the wiki, so it shows up under Emulation Station in the Docs. I'm not sure if it would do that if it was in the ES repo.

@erayman Not a bother, and I'm sorry that that is the answer. :|

Thank you for this release, Flerp! I couldn't get the auto build to run at all, but your 2.6 version got retrorama theme working. I can die a happy man now!

@red2blue try setting them to:

input_player1_joypad_index = 0 input_player2_joypad_index = 1

@herb_fargus Helpful, thanks!

Thanks for your reply @edmaul69

I've just finished configuring the new setup with 16.901 roms plus Kodi. All is working fine!

@dankcushions Yeah, I know about this project, but OpenELEC distribution really limits me to make my changes easily, that's why I want to test all on RetroPie and then make changes to Lakka.

Package is removed on my 17.10 Ubuntu - need to update the module to change dependency to just vlc. Should be ok on 17.04 though - you definitely not using the latest beta of Ubuntu?

@meleu said in ensuring ES gracefully finish ... annother approach:

@caver01 it wouldn't work for any shutdown. And I'm afraid it wouldn't work in any case. And you guessed the reason: "those files created by ES too short-lived".

edit: as you can see in emulation.sh script, those files are removed right before calling reboot|poweroff, then killes.sh won't be able to see them.

Correct - the files are not living to long to check via testcommand fileexistance!
Therefore the incron job triggers existance of files and gives feedback to script!
This works in any cases!

I did long testing with this and all files ... even if they were created and removed like

touch /tmp/testfile.dat && rm /tmp/testfile.dat

The script was always triggered. So YES this solution is working as else. But I was in need to use two more files... that give "feedback" what was triggered now?

Is it a shutdown via software? >> action_software-file is created and checked
Is it a shutdown via hardware? >> action_hardware-file is created and checked

So how does a software shutdown + GPIO triggering works?

Quit Menu -- ES Shutdown ES creates file /tmp/es-shutdown incron triggers script and realizes "action_software" /tmp/es-shutdown is removed by ES shutdown script .... incron trigger is still active incronscript triggers GPIO and set transistor to high Now... the button shutdown script from Mausberry, bash, python... as you like is triggered (as a button press is recognizes) This button shutdown script calls again the incron script /home/pi/incrontrol.sh button-shutdown in the incrontrol.sh is a check for file ... "action_software" for usecase button-shutdown > Exit in background the ES shutdown is still performed GPIO is triggered, mausberry is off, regular shutdown performed

@meleu said in ensuring ES gracefully finish ... annother approach:

@caver01 the simplest solution I can think is to use a systemd trick again. Let's discuss on your thread to not mess this one.

As I said in OP ... the systemd trick is a general solution and seems easier to maintain.
But there are always many roads that leads to rome: Let us collect experience