@brunog

Two posts for the same problem... I close this one and reply to the other.

Thank you for understanding.

Deux posts pour le même problème... Je ferme celui-ci et réponds à l'autre.

Merci pour votre compréhension.

I have now tried the same scenario, using the same romset and everything, but on a fresh Recalbox installation, and the Mame2015 roms worked fine.

So it seems like for some reason, my Mame2015 core got corrupted or something on my original installation.

I'm currently comparing the differences between my previous install and my fresh install but I haven't been able to spot anything that is Mame2015 related in the deltas.

@wonderrecal777

https://forum.recalbox.com/topic/25561/ps1-splash-screen-or-startup-intro

@zing Ok thank you so much I will take a look on this 🙂

Hello
no support for old version

You need to install recaclbox 7.0.1

Hello @Bkg2k,
Not load of the system in background here 😕 . Right now I checked it again several times with same result. As example in the next case, if I set a custom video in folder bootvideos with this configuration in recalbox.conf
system.splash.length=30
system.splash.select=custom

The system is delayed 30 seconds more in startup. The spashscreen with pacman and the load of emulationstation appears after the video is played.

--
RB7.0 + Raspberry pi 4 4GB

@naitreia I corrected 2 errors in the scripts above, please be sure to copy the code after this post 🙂

Hello
double subject : https://forum.recalbox.com/topic/20082/démarrage-recalbox

Super ich danke dir Herzlich
kenne mich nicht besonders aus im Programmieren habe versucht bei Google eine Lösung zu finden und hatte es dort auch irgendwo gelesen mit den Vier Leerzeichen aber hatte es nicht so richtig verstanden...

nach deiner Antwort und mehrmaligen versuchen hat es endlich geklappt 😄

so muss das aussehen:

0_1555715757826_Script.jpg

Hi, I managed to add a custom startup script and wrote the process in the last message of this thread:
https://forum.recalbox.com/topic/11022/how-to-autostart-a-rom-directly-on-boot/8

Maybe it helps!
Greetings

@Kevin-Mathis

As I posted otherwhere, you need no script for this. As USB are powered up by PI when system starts (all systems) and powered down at shutdown, with the PI always under power. So you just need to connect the relay at an USB power line, by cable or breakout adapter, as you want.

I looked into that.

At startup, on odroid, the S02splash script starts the splash mp4 video, in background process, using ffplay for x seconds (set to 20 by default. see recalbox.conf, system.splash.length parameter).
Meantime the video is running, others startup scripts are running including the S31emulationstation script that display version logo (that is useless as the S02splash script do it after the splash video...) and start emulationstation without to wait the splash mp4 video finish. Making flickering effects.
Said simpler, ffplay output is in conflict with fbv (via showlogo.sh) and emulationstation boot logo as it's displayed in the same time.

Waiting a real fix you can do either of the following trick to display splash video properly:

A simple trick is to not run the splash video in background so the other startup scripts will not run untill the video is finished. Boot process will be longer as nothing else will append the time the video is running.
Open a ssh session on your recalbox then run :
mount -o remount rw, /
cd /etc/init.d
nano S02splash

Edit the file as shown bellow

do_ffmpeg_start () { if ! `which ffplay >/dev/null` || [[ ! -f $video ]] ; then return fi ffplay_opts="-hide_banner -autoexit" ffplay_srt="subtitles=/recalbox/system/resources/splash/recalboxintro.srt:force_style='FontName=/usr/share/fonts/dejavu/DejaVuSans-BoldOblique.ttf,Fontsize=10'" ffplay $ffplay_opts -vf "$ffplay_srt" "$video" >/dev/null 2>&1 & PID=$! count=0 if [[ $videolength -gt -1 ]]; then while [[ ! -f "/tmp/emulationstation.ready" && ! -e "/var/run/kodi.msg" && $count -lt $(($videolength*10)) ]]; do sleep 0.1 ((count++)) done fi do_ffmpeg_stop $PID show_logo & # <-- edit here by adding the "&" }

...

case "$1" in start) if [[ `cat /recalbox/recalbox.arch` == "rpi"* ]] ; then ( do_omx_start ; show_logo ) & else ( wait_for_fb ; do_ffmpeg_start ) #& # <-- edit here by removing or commenting the "&" fi ;; stop) ;; restart|reload) ;; *) esac

Save and close it with STRG + X
You can customize the length of the splash video by editing your /recalbox/share/system/recalbox.conf file, system.splash.length parameter. 12 seconds is a good choice.

--

Another way is to modify S31emulationstation script to wait ffplay finished (or killed) before to start emulationstation. So the others sartup scripts will not wait video completion.
Open an ssh session on your recalbox then run :
mount -o remount rw, /
cd /etc/init.d
nano S31emulationstation

Edit the file as shown bellow

case "$1" in start) enabled="`$systemsetting -command load -key system.es.atstartup`" videoMode="`$systemsetting -command load -key system.es.videomode`" if [ "$enabled" != "0" ];then while [ "$(pidof ffplay)" ]; do #<-- eddit here by adding this sleep 0.1 #<-- eddit here by adding this done #<-- eddit here by adding this /recalbox/scripts/showlogo.sh & # In case the logo has been removed, let's put it back again echo $videoMode | grep -qE "(CEA|DMT) [0-9]{1,2} (HDMI|DVI)" [ $? = "0" ] && tvservice -e "$videoMode" settings_lang="`$systemsetting -command load -key system.language`" recallog "starting emulationstation with lang = $settings_lang" HOME=/recalbox/share/system LANG="${settings_lang}.UTF-8" SDL_VIDEO_GL_DRIVER=/usr/lib/libGLESv2.so SDL_VIDEO_EGL_DRIVER=/usr/lib/libGLESv2.so SDL_NOMOUSE=1 start-stop-daemon -S -q -m -p /var/run/emulationstation.pid --exec /usr/bin/emulationstation & fi ;;

Save and close it with STRG + X

--

In both case, you can still customize the length of the splash video by editing your /recalbox/share/system/recalbox.conf file, system.splash.length parameter.
12 seconds is a good choice.

@revwarguy you can't without some manual actions.

@tolley Try to put the full temp path instead of ~/temp

@cagiraudo ok let me explain it in english, sorry

The bootcode_delay adds a delay before the pi queries the tv's EDID. That's fine

If your pi never moves off your tv, then you can record the tv edid and force it at boot