Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about splash videos length / Auto-stop #1210

Open
worstcase-scenario opened this issue Jul 15, 2023 · 3 comments
Open

Question about splash videos length / Auto-stop #1210

worstcase-scenario opened this issue Jul 15, 2023 · 3 comments

Comments

@worstcase-scenario
Copy link

worstcase-scenario commented Jul 15, 2023

Hello, I have a small issue/question and hope that someone can help me with it:

I wanted to have an individual loading/splash-video running before starting games from each system, did that and it works great (by putting the .mp4-files into the /roms/splash-directory).

But as far as I experienced it, EmuElec always plays the WHOLE splash video to the end before starting the game - even though the internal "pre-loading" time is already done (I know that because I have checked the loading time without having a video but just a splash-screen).

Is there any way that EmuElec can automatically stop playing the splash video when finished loading and go on to start the emulation?

Or do I just have to deal with it by having only like ten second long splash videos or so?

But then, the problem in some cases is that the video just ends and EmuElec is still loading the game in the background. Hmm. Would be great if the video could be on repeat at least…

Looking forward for any suggestions or answers! Thanks in advance!

@Langerz82
Copy link
Collaborator

As explained you would need a hook into retroarch or modify retroarch to execute a kill command to the splash video process. Retroarch only starts loading the rom once the process has started.

@shantigilbert
Copy link
Collaborator

With the current implementation this is not really possible, at least not in a simple way. The splash screen is a separate process than the emulator itself. What happens is something like this: The Launcher (ES) calls a script, this script in turn sets any of the custom settings, screen ratio, sound, resolution, bezels, etc, etc, then in the end it calls the splash screen, since we use the frame buffer for display, only one thing can be shown at a time, so we need to finish the splash screen before the script continues and then we call anything else (in this case Retroarch), otherwise the splash screen would go into the background, but the display will try to load 2 things at the time and it will look all scrambled/mixed.

So in other words, the splash screen is a lie, it is NOT pre-loading the game in the background, the game starts loading only after the video/splash finishes.

Unfortunately there is no real easy way to have multiple emulators/ports/etc control a splash screen. I guess a custom splash loader than would block the display until the emulator is loaded completely then ends the splash is doable...in theory, in practice its a whole different story, and not something in the plans or to do list.

@worstcase-scenario
Copy link
Author

Thank you very much for your explanation!
It all makes sense. I guess the only question/option would be if the splash screen format could be a .gif? Is that possible?
This way it could show an animated picture (like a rotating hour glass, for example) to fake a video...
But this whole feature is really not that important, it was just an aesthetic idea. You guys have so many more important technical issues to solve... thank you again for your incredible work! It's very much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants