VIDEO SCREENSAVER - Black Screen with OMX on and Controls Not working

DreamcastKid

@2play said in VIDEO SCREENSAVER - Black Screen with OMX on and Controls Not working:

An external subs error with the omx

Subtitles aka. Display Game Title / System Name overlay with OMX on, does not work in the lastest Retropie images. (works fine in 4.5, broke in 4.6)

If you select to display the Game/System overlay text on the Video Screensaver with OMX on ... you will get a Black Screen.

Options:

(1) Disable display game title/system overlay text

or

(2) Disable OMX

Simrose

@dreamcastkid

Pi4 2gb
Official psu
Latest official retropie installed
Fully updated

I have similar problem. I disabled onscreen game info text and omx works, video screen saver displays videos correctly but you can't launch any game.
When pressing any button it just goes straight back to emulation station

I had not used this feature for a few months but it was working when I did before.
Thanks
Sim

2Play

@mitu thank you. I have searched here but didnt find anything current.
apologies if i missed something

2Play

@dreamcastkid Any idea on the controls not working to start the game any longer.
to me it looks not rpie setup script but ES binary related.
and last 2 versions have same behavior. both i got frm core packages binary update
so its all default
os updated official Dec

mitu

@2play said in VIDEO SCREENSAVER - Black Screen with OMX on and Controls Not working:

@mitu thank you. I have searched here but didnt find anything current.

You didn't add any info about your system.

2Play

@mitu you are correct

First test
Linux 5.4.83-v7l+
RetroPie Setup 4.7.2
OS Latest Updates Raspbian Buster 10
ES 2.9.3rp & ES 2.9.6rp
Model : Raspberry Pi 4 Model B Rev 1.1 2GB
CPU Hardware : BCM2711 - Model name: Cortex-A72

Second Test Today:
Linux 5.10.7-v7l+
RetroPie Setup 4.7.2
OS Latest Updates Raspbian Buster 10
ES 2.9.6rp
Model : Raspberry Pi 4 Model B Rev 1.1 2GB
CPU Hardware : BCM2711 - Model name: Cortex-A72

mitu

@2play said in VIDEO SCREENSAVER - Black Screen with OMX on and Controls Not working:

Model : Raspberry Pi 4 Model B Rev 1.1 2GB

omxplayer doesn't support subtitles on the Pi4, you either have to disable it if you want subtitles or disable subtitles to keep omxplayer.

2Play

Noted but none knows why start a game stopped working from video screen saver in my understanding correct?

mitu

The game start is bound to start - for both images and video screensavers. For videos it might have been possible to use any button, but right now they're both using the same key.
More details in the discussion here.

2Play

@mitu gm from here
the link goes to "Error loading new systems"

Unfo the game wont start from the video screensaver .
the only button working is SELECT as per my initial post that simply goes to next random video. any other button including start goes back to ES

i have to figure out what the culprit is. i dont know if i can find any info in the ES log but il check

any other tips id like to thank you in advance.
Thank you @mitu for your expertise and help

2Play

@mitu
I have tested an older backup I had prior 5.4.xx.
It has 4.19.118 kernel.
START button works fine on video screensaver.

Of course black screen on pi4 is as we talked above (not concerned)

I dont know what might have changed with newer 5 kernel setup. I ll test a clean RPie base and report back.

2Play

updated below...

2Play

@mitu @pjft
My only problem is that START button does not trigger the rom to start.

My understanding is that you have this compiled in ES
I have removed ES and added from binary.

I can see one of the requirements is VLC now.
I removed VLC and ES.
Installed from BINARY and both installed ok

START still cant trigger the ROM. Any ideas what might have been broken?

pjft

@2play Unless something with SDL is causing it to register buttons differently, thus detecting <something different> before the start button it expects.

I thought I had answered this in another thread, but there is an option in the ES menu to actually enable or disable this behavior ("enable screensaver controls", I believe). Check whether that's enabled.

Other than this, I'm out of options. Nothing changed in ES.

EDIT: what controller are you using, and is it plugged or bluetooth? Does this happen with other controllers - or even a plain usb keyboard?

2Play

@pjft Thank you
i do have them enabled in ES
Tried both my USB BT KB, normal USB KB. and a 3rd party PS3 alike wired controller. A friend tried with ps4 but same
Ill check the SDL as I keep compiling things on my base to test things

But i think you gave a me a hint to check couple things

2Play

@pjft
Quick update on this.
I had a working image and after latest full upgrade OS applied yesterday, feature is broken (game wont start from video screensaver with START).

Linux 5.10.17-v7l+ armv7l GNU/Linux - Raspbian GNU/Linux 10 (buster)
Model : Raspberry Pi 4 Model B Rev 1.1

its very weird.
Here is a pastebin of what i managed to gather on packs changed

https://pastebin.com/RCCbB5sK

pjft

@2play I'm quite at a loss here, but can you share the ES log as well, and potentially even running it with --debug (or. whatever the command is to get debug logging)?

What type of controller are you using, does it move to the next game during screensaver if you press "right", is it only start that doesn't work?

2Play

@pjft
tx for reply
just burned back an older backup.
Linux 5.4.83 based was ok and still ok. I think up to 5.10.11
It broke when upped to 5.10.17 as per my last

I have a third party PS alike controller (esperanza - Microntec USB)
Yes it moves right left to next video.
But mostly I use a 2.4G Mini Wireless Keyboard with Touchpad Backlight you know these small ones to be used with media boxes

ill upgrade the OS again on above and see again. ill try to export full process

Reverting after OS upgrade and I will run ES with --degub option

2Play

@pjft
Im out of words...
I burned my backup, did full distro upgrade (updated last pastebin above)
reboot
Tested video scr and worked ok!
Exit to CLi, run with emulationstation --debug
tested again and works ok.
Here is the pastebin with related events called ok!

https://pastebin.com/D23jS7Vd

I dont know what to say as I did nothing more.

If happens i ll run again with --debug and post if of any help

Thank you again for your time and above reply

2Play

@pjft
As im trying to find what has caused this behavior i revisited the "broken" system.
Updated from binary ES,
Reset controller configuration
Reboot wiht ES degub enabled

Remapped my keyboard and started screensaver.
Am i right to say that START value doesnt post 1 just 0

Mar 24 12:23:23 lvl2: 	  Mapping [Key Down] -> Down
Mar 24 12:23:23 lvl2: 	  Mapping [Key Left] -> Left
Mar 24 12:23:24 lvl2: 	  Mapping [Key Right] -> Right
Mar 24 12:23:25 lvl2: 	  Mapping [Key F6] -> Start
Mar 24 12:23:26 lvl2: 	  Mapping [Key F5] -> Select
Mar 24 12:23:27 lvl2: 	  Mapping [Key Z] -> A
Mar 24 12:23:28 lvl2: 	  Mapping [Key X] -> B
Mar 24 12:23:28 lvl2: 	  Mapping [Key A] -> X
Mar 24 12:23:29 lvl2: 	  Mapping [Key S] -> Y
Mar 24 12:24:00 lvl3: 	fireEvent: config-changed  
Mar 24 12:24:00 lvl3: 	fireEvent: controls-changed  
Mar 24 12:24:00 lvl2: 		/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh
Mar 24 12:24:01 lvl3: 	UIModeController::logInput( Keyboard ):Key Z, isMappedTo= a, , value=0
Mar 24 12:24:02 lvl3: 	UIModeController::logInput( Keyboard ):Key Right, isMappedTo= right, , value=1
Mar 24 12:24:03 lvl3: 	UIModeController::logInput( Keyboard ):Key Right, isMappedTo= right, , value=0
Mar 24 12:24:03 lvl3: 	UIModeController::logInput( Keyboard ):Key Left, isMappedTo= left, , value=1
Mar 24 12:24:03 lvl3: 	UIModeController::logInput( Keyboard ):Key Left, isMappedTo= left, , value=0
Mar 24 12:24:04 lvl3: 	UIModeController::logInput( Keyboard ):Key F5, isMappedTo= select, , value=1
Mar 24 12:24:05 lvl3: 	UIModeController::logInput( Keyboard ):Key F5, isMappedTo= select, , value=0
Mar 24 12:24:05 lvl3: 	fireEvent: screensaver-start  
Mar 24 12:24:19 lvl3: 	fireEvent: screensaver-stop  
Mar 24 12:24:19 lvl3: 	UIModeController::logInput( Keyboard ):Key F6, isMappedTo= start, , value=0
Mar 24 12:25:19 lvl3: 	UIModeController::logInput( Keyboard ):Key F5, isMappedTo= select, , value=1
Mar 24 12:25:19 lvl3: 	UIModeController::logInput( Keyboard ):Key F5, isMappedTo= select, , value=0
Mar 24 12:25:19 lvl3: 	fireEvent: screensaver-start  
Mar 24 12:28:46 lvl3: 	fireEvent: screensaver-stop  
Mar 24 12:28:46 lvl3: 	UIModeController::logInput( Keyboard ):Key F6, isMappedTo= start, , value=0
Mar 24 12:31:47 lvl3: 	fireEvent: screensaver-start  
Mar 24 12:32:55 lvl3: 	fireEvent: screensaver-stop  
Mar 24 12:32:55 lvl3: 	UIModeController::logInput( Keyboard ):Key F6, isMappedTo= start, , value=0
Mar 24 12:35:56 lvl3: 	fireEvent: screensaver-start  
Mar 24 12:39:59 lvl3: 	fireEvent: screensaver-stop  
Mar 24 12:40:00 lvl3: 	UIModeController::logInput( Keyboard ):Key Left, isMappedTo= left, , value=0
Mar 24 12:40:27 lvl3: 	UIModeController::logInput( Keyboard ):Key F5, isMappedTo= select, , value=1
Mar 24 12:40:27 lvl3: 	UIModeController::logInput( Keyboard ):Key F5, isMappedTo= select, , value=0
Mar 24 12:40:27 lvl3: 	fireEvent: screensaver-start  
Mar 24 12:40:43 lvl3: 	fireEvent: screensaver-stop  
Mar 24 12:40:43 lvl3: 	UIModeController::logInput( Keyboard ):Key F6, isMappedTo= start, , value=0

and controller setup and test:

Mar 24 12:50:26 lvl2: 	  Mapping [Hat 0 up] -> Up
Mar 24 12:50:26 lvl2: 	  Mapping [Hat 0 down] -> Down
Mar 24 12:50:27 lvl2: 	  Mapping [Hat 0 left] -> Left
Mar 24 12:50:27 lvl2: 	  Mapping [Hat 0 right] -> Right
Mar 24 12:50:28 lvl2: 	  Mapping [Button 9] -> Start
Mar 24 12:50:29 lvl2: 	  Mapping [Button 8] -> Select
Mar 24 12:50:31 lvl2: 	  Mapping [Button 2] -> A
Mar 24 12:50:32 lvl2: 	  Mapping [Button 1] -> B
Mar 24 12:50:32 lvl2: 	  Mapping [Button 3] -> X
Mar 24 12:50:33 lvl2: 	  Mapping [Button 0] -> Y
Mar 24 12:50:33 lvl2: 	  Mapping [Button 4] -> LeftShoulder
Mar 24 12:50:34 lvl2: 	  Mapping [Button 5] -> RightShoulder
Mar 24 12:50:34 lvl2: 	  Mapping [Button 6] -> LeftTrigger
Mar 24 12:50:35 lvl2: 	  Mapping [Button 7] -> RightTrigger
Mar 24 12:50:36 lvl2: 	  Mapping [Button 10] -> LeftThumb
Mar 24 12:50:36 lvl2: 	  Mapping [Button 11] -> RightThumb
Mar 24 12:50:37 lvl2: 	  Mapping [Axis 1-] -> LeftAnalogUp
Mar 24 12:50:38 lvl2: 	  Mapping [Axis 1+] -> LeftAnalogDown
Mar 24 12:50:38 lvl2: 	  Mapping [Axis 0-] -> LeftAnalogLeft
Mar 24 12:50:39 lvl2: 	  Mapping [Axis 0+] -> LeftAnalogRight
Mar 24 12:50:40 lvl2: 	  Mapping [Axis 3-] -> RightAnalogUp
Mar 24 12:50:40 lvl2: 	  Mapping [Axis 3+] -> RightAnalogDown
Mar 24 12:50:41 lvl2: 	  Mapping [Axis 2-] -> RightAnalogLeft
Mar 24 12:50:42 lvl2: 	  Mapping [Axis 2+] -> RightAnalogRight
Mar 24 12:50:42 lvl2: 	  Mapping [Axis 2-] -> HotKeyEnable
Mar 24 12:50:55 lvl2: 	  Mapping [Axis 1-] -> LeftAnalogUp
Mar 24 12:50:57 lvl2: 	  Mapping [Axis 1+] -> LeftAnalogDown
Mar 24 12:51:00 lvl2: 	  Mapping [Axis 0-] -> LeftAnalogLeft
Mar 24 12:51:02 lvl2: 	  Mapping [Axis 0+] -> LeftAnalogRight
Mar 24 12:51:05 lvl2: 	  Mapping [Axis 3-] -> RightAnalogUp
Mar 24 12:51:08 lvl2: 	  Mapping [Axis 3+] -> RightAnalogDown
Mar 24 12:51:16 lvl2: 	  Mapping [Axis 2-] -> RightAnalogLeft
Mar 24 12:51:19 lvl2: 	  Mapping [Axis 2+] -> RightAnalogRight
Mar 24 12:51:26 lvl3: 	fireEvent: config-changed  
Mar 24 12:51:26 lvl3: 	fireEvent: controls-changed  
Mar 24 12:51:26 lvl2: 		/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh
Mar 24 12:51:38 lvl3: 	UIModeController::logInput( Microntek              USB Joystick           ):Button 1, isMappedTo= b, , value=0
Mar 24 12:51:39 lvl3: 	UIModeController::logInput( Microntek              USB Joystick           ):Button 8, isMappedTo= select, , value=1
Mar 24 12:51:39 lvl3: 	UIModeController::logInput( Microntek              USB Joystick           ):Button 8, isMappedTo= select, , value=0
Mar 24 12:51:39 lvl3: 	fireEvent: screensaver-start  
Mar 24 12:51:43 lvl3: 	fireEvent: screensaver-stop  
Mar 24 12:51:43 lvl3: 	UIModeController::logInput( Microntek              USB Joystick           ):Button 9, isMappedTo= start, , value=0

There should be a file that I can check...right?