Thanks for taking a look at this. I'm not familiar with this part, but I'll take a look later on.

I get a lot of errors trying to run this script, syntax errors and unexpected tokens. We're just copying what you posted into a .sh file?

Whatever you point of view is on this. I like to have peers (you, the other maintainers and also forum members) which help to streamline a change or fix. It was fun to solve this with you. :)

@Lolonois cheers! This is working on my end, thanks!

@mitu FYI for the time being, I have a partial workaround to execute commands to stop and start emulationstation via a remote.

@spaceblaze Just to confirm the above code change does work.

I reexported all the videos at 480p and now have control over the size.

As it turns out, the end result is not that great a user experience so I'm reworking the layout a bit.

Will post a video once I'm happy with it.

Updated sample video links showing the proposed functionality as Anonfiles was shutdown.

Got four likes in the meantime. But the functionality in general does not seem to be widely anticipated?

Issue 1 can be easily solved by using the Audio menu in RetroPie and choosing your default output (Analog Jack/HDMI).

For #2 - The Headphone value can also be chosen in the EmulationStation settings, since it has been updated in June 2020 following the RPI OS changes.

The -dev version has been recently promoted to stable, so both versions of the EmulationStation package are now identical (for the time being, until more things are added to the new dev).

If ES crashes, the log will not be of much help, but a gdb trace (backtrace) might be helpful to see where exactly (in the code) the crash occurs. If you can reliably reproduce the crash, then it might be worth using gdb and capture the trace:

gdb -q /opt/retropie/supplementary/emulationstation-dev/emulationstation - ex run # if there's any crash, gdb will report it and show a prompt thread apply all bt

What's the point of enabling it if there's no corresponding functionality in EmulationStation ?

This would be a pre-requisite to allow extra functions as currently 12 buttons are used to control ES and there are no "spare" buttons.

provided [hotkey] doesn't trump an existing input

Yes, hotkey can have three states: Absent, present or mapped to Select.

Case hotkey is mapped to Select button:
The Select is used for Start Screensaver, choose next item in screensaver media or bringing up the Options dialog in a gamelist to my knowledge. These events are consumed before the systemcarousel and gamelist logic and do not reach the later components in the GUI stack where hotkey would be processed (e.g. scroll a game's description with hotkey held and joy up/down pressed as one possible ES enhancement).

Case dedicated hotkey button:
Each GuiComponent would decide if it would act on hotkey input. In turn this also means a hotkey-button-combo can only be processed by one gui component when there are multiple gui components displayed.

@steve12 no.

Ok it is kinda working, it seems I need to do a lot of editing to the github files to make it work nicely with the original retropie install as various default directories are different in this alternative emulationstation.
This isnt as straight forward as I thought it would be lol

@mitu said in EmulationStation Marquee Bug (with work-around):

EDIT: Try the Magazine Madness theme, it has support for marquees in Detailed view.

You're correct @mitu. Just tried in both Detailed and Automatic views and without videos referenced, the marquees do indeed appear.

For each theme I used that exhibits the problem, the marquee section is under <view name = "video">. Updating the themes, including Carbon, by moving the marquee section under <view name = "Detailed"> works (and would seem to be a more common scenario).

Seems that many themes used Carbon as a baseline and have marquee under the video view section. Easy to fix (or change, if it was what the author intended).

Thank you, as always.

@dankcushions said in Pi 4b black screen issues:

@luisdent like i said, show us your config file and we can diagnose. there's an extra few lines that helps on some monitors:

hdmi_max_pixel_freq:0=200000000 hdmi_max_pixel_freq:1=200000000

in addition to a working 1080p mode, which for you may be

hdmi_group=2 hdmi_mode=82

ps, can you not SSH in to diagnose via another PC on the network?

Not sure which fixed it, but this made it work properly. It flickers a screen with the terminal/command cursor a few times quickly but i see it and then it displays the appropriate screen following that. So far i've gone in and out of config screens and reboots and it appears to be working now.

Thanks!!!

Now to fix the performance issues ;-) or i should say optimize. it runs fairly well. :)

@mitu it never seemed to kill the instance that I ran it from, but it did give ES a stroke, so I won't do it anymore :)

I guys are following the discussion :)
Whit my bad english it's already difficult to made an example........

Damn... when i made the video whit GB and CATRAP for the other my thread I could show you the example of this too :)

I also had to post the gamelist.xml but it just passed my mind ... really sorry ...

awesome

Thanks both.

This XML element is not mandatory, so it can be left out and it will evaluated to false if a theme checks this value. If it is there it has to be explicitly set 1 (or semantically equivalent) to be effective. This is why I perceive it as redundant and picked the term.

Never mind, let's keep the implementation as-is.