RetroPie on RPi4 2gb, No splash or main menu audio

[VirgoH]

@mitu It gives me a "File "ComicBookSplash-720.mp4" not found." error.

[mitu]

@virgoh The path is the one you posted - maybe this is not the correct name ? You can use Tab to complete the file name by just typing

omxplayer --no-osd -o both -b --layer 10000 ComicBook

and then pressing tab, the correct filename should show up, assuming you only have 1 file named "ComicBook*" in the splashscreen folder.

[VirgoH]

This post is deleted!

[VirgoH]

@mitu It says "-bash: omxplayer: command not found"
Sorry, I had a typo in the command. After correcting that typo it says "/usr/bin/omxplayer.bin: unrecognized option '--n-osd'
Sorry, another typo on my part. The video plays, but no audio.

[mitu]

@mitu said in RetroPie on RPi4 2gb, No splash or main menu audio:

and then pressing tab, the correct filename should show up, assuming you only have 1 file named "ComicBook*" in the splashscreen folder.

Try to re-download the video from https://retropie.org.uk/forum/topic/10724/new-comicbook-video-splashscreen and re-configure the splashscreen to play it.

[VirgoH]

@mitu For clarification, I can re-download it from there, but what do you mean reconfigure it? I never did anything to the previous file.

[VirgoH]

@mitu re-downloading that video and installing it still has the same problem.

[Lucathebazooka]

Probably the theme uninstall the Comic book theme and then see if its working. (some themes don't support Splash screens or main menu audio.)

[mitu]

@virgoh said in RetroPie on RPi4 2gb, No splash or main menu audio:

re-downloading that video and installing it still has the same problem.

Then I don't have any other idea. I assume you're using HDMI for audio output, which omxplayer should be able to use - I tested the command line I posted for testing and it worked fine with the Comic Book splash video.

[VirgoH]

@mitu Yeah, the Splash screen and menu aren't a huge deal, so I don't mind too much, I just wish I could figure it out. At this point I'm hoping it's resolved with a future update.