[herbfargus]

Sudo raspi-config

Choose expand filesystem

Reboot

[herbfargus]

I just bought my pi2 from mcmelectronics (the main distributor for the Raspberri Pi Foundation) cost me $45 with shipping to the US. cheaper than amazon and only took 3 weeks or so. Even though some games still lag it was well worth the upgrade.

[herbfargus]

There are two versions of the 2.6 image. one for the raspberry pi B+ and one for the Raspberry Pi 2 Model B. You’re probably smarter than me but just in case you made the same mistake I did- this is the sd image that works for the Pi 2

https://www.petrockblock.com/retropie/retropie-downloads/download-info/retropie-sd-card-image-for-rpi-version-2/

[herbfargus]

@ yogg

Why yes there is- if you said you are using the method from the first post and your code for the asplashcreen file looks something like this:

/usr/bin/omxplayer -o hdmi /home/pi/RetroPie-Setup/supplementary/splashscreens/video/mushberryintro.mp4 &

delete the “&” and it will allow the movie to play the whole way through before emulationstation starts: so your changed code will look something like this:

/usr/bin/omxplayer -o hdmi /home/pi/RetroPie-Setup/supplementary/splashscreens/video/mushberryintro.mp4

If you are using the second method for image 2.6 the “&” you need to remove is a bit lower in this bit of code:

case "$1" in
  start|"")
    do_start &
    ;;

if you want the movie to play through before emulationstation loads remove the “&” so it looks like this:

case "$1" in
  start|"")
    do_start
    ;;

[herbfargus]

Beautiful :) I’m glad it all worked out, it was totally worth it + I learned a ton. I’ll keep you posted on splash videos I make.

[herbfargus]

Looks right. If that doesn’t work you might have mess with the kernel to remove the raspberry pi logo which can be a little more complicated.

[herbfargus]

FINALLY!!! Ha ha thanks for being patient with me. Add logo.nologo to remove the raspberry pi logo

[herbfargus]

0rionas- you are a genius. The older build in my case didn’t have audio on .mp4 files I tested but .avi files worked out. thank you, you saved me a lot of headaches.

another alternative to the code you provided, is provided by Free5sty1e, and it will enable you to select splashscreens through the setup script so you can switch between video and static image splashscreens as well.

\#! /bin/sh
### BEGIN INIT INFO
# Provides:          asplashscreen
# Required-Start:
# Required-Stop:
# Default-Start:     S
# Default-Stop:
# Short-Description: Show custom splashscreen
# Description:       Show custom splashscreen
### END INIT INFO

do_start () {

    while read splashline; do
        echo Playing splash video or image $splashline
        isMovie=$(echo $splashline | grep -o ".mov\|.mp4\|.mkv\|.3gp\|.mpg")
        if [ -z "$isMovie" ]; then
            /usr/bin/fbi -T 1 -once -t 10 -noverbose -a $splashline
            sleep 12
        else
            omxplayer $splashline
        fi
    done </etc/splashscreen.list
    exit 0
}

case "$1" in
  start|"")
    do_start &
    ;;
  restart|reload|force-reload)
    echo "Error: argument '$1' not supported" >&2
    exit 3
    ;;
  stop)
    # No-op
    ;;
  status)
    exit 0
    ;;
  *)
    echo "Usage: asplashscreen [start|stop]" >&2
    exit 3
    ;;
esac

:

[herbfargus]

OK- here’s the plan. forget everything I’ve said. I’ve decided we’ve wasted enough time with the DBUS issue- that is a firmware problem that needs to be solved with the developers or raspbian/omxplayer. In the mean time I’ve come up with a foolproof (i promise this time) solution. ok here we go:

first off if you don’t want to start off with a new build, you need to uninstall omxplayer (otherwise you can just start with a fresh sd image):
sudo apt-get remove omxplayer

then you’ll follow the steps taken from someone smarter than me:( i.e. 0rionas)

mkdir media
cd media
sudo wget http://omxplayer.sconde.net/builds/omxplayer_0.3.4~git20140212~bf48901_armhf.deb
sudo dpkg -i omxplayer_0.3.4~git20140212~bf48901_armhf.deb
sudo apt-mark hold omxplayer

then instead of his next steps that don’t take into account the set up script, we go back to the original script from free5ty1e:
this is the asplashscreen you modify:
/home/pi/RetroPie-Setup/supplementary/asplashscreen/asplashcreen

#! /bin/sh
### BEGIN INIT INFO
# Provides:          asplashscreen
# Required-Start:
# Required-Stop:
# Default-Start:     S
# Default-Stop:
# Short-Description: Show custom splashscreen
# Description:       Show custom splashscreen
### END INIT INFO

do_start () {

    while read splashline; do
        echo Playing splash video or image $splashline
        isMovie=$(echo $splashline | grep -o ".mov\|.mp4\|.mkv\|.3gp\|.mpg")
        if [ -z "$isMovie" ]; then
            /usr/bin/fbi -T 1 -once -t 10 -noverbose -a $splashline
            sleep 12
        else
            omxplayer $splashline
        fi
    done </etc/splashscreen.list
    exit 0
}

case "$1" in
  start|"")
    do_start &
    ;;
  restart|reload|force-reload)
    echo "Error: argument '$1' not supported" >&2
    exit 3
    ;;
  stop)
    # No-op
    ;;
  status)
    exit 0
    ;;
  *)
    echo "Usage: asplashscreen [start|stop]" >&2
    exit 3
    ;;
esac

:

you leave the splashenable.sh scriptmodule at the original defaults- you don’t do anything to it. (this is the file if you didn’t keep backups before you changed it:
https://github.com/retropie/RetroPie-Setup/blob/master/scriptmodules/supplementary/splashenable.sh)

then go into the setup script, enable splashcreens, choose your video splashscreen- reboot.

(for some reason with this older build .mp4 files didn’t play sound on mine- but .avi worked perfectly. .mov and .mkv might work as well but i have not tested them)

sorry for my inexperience in linux and leading you on a wild goosechase. this method will work.

[herbfargus]

[removed]

[herbfargus]

As the software is constantly being updated, there will always be something going on and always another update to do, but it isn’t necessary to reimage your sd everytime there is an update.
The way you update is

cd RetroPie-Setup
sudo ./retropie_setup.sh

then you update the setup script and then you can select install from binary or install from source for each emulator (binary is much faster but may not be as updated, building from source takes a long time but you get the latest updates)

[herbfargus]

This is what I used for mine. I just used win32diskimager to put it on my microsd card and it booted up fine.
https://www.petrockblock.com/retropie/retropie-downloads/download-info/retropie-sd-card-image-for-rpi-version-1/

you’ll have to add the roms into their respective rom folder for each emulator you want to show up in emulationstation.

[herbfargus]

you’ll press F10 i think or maybe F5 while you are in a game to configure your controller.

[herbfargus]

[redacted- what ROO said]

once you have configured your wifi adapter like roo outlined-

sudo /etc/init.d/networking restart

or

sudo /etc/init.d/networking stop
 sudo /etc/init.d/networking start

or
sudo reboot

Now your wifi should be running- no gui needed.

[herbfargus]

if anyone else wants the link to my working files, here they are:

https://drive.google.com/open?id=0B2TMeZ6iEFvHSzFsQlpNdFZOazg&authuser=0

remove or backup your current asplashscreen files and replace them with the nsplashscreen file I provided. You will copy it to these two locations:

/home/pi/RetroPie-Setup/supplementary/asplashscreen
/etc/init.d

remove or backup the current splashenable.sh and add the splashenable.sh I provided to:

/home/pi/RetroPie-Setup/scriptmodules/supplementary

then you’ll go into the setup script, enable splashcreens and then choose your splashscreen and then reboot

[herbfargus]

I’m on a raspberry pi B+ with using the 2.6 image. I would recommend updating to the 2.6 image. some of the file structure may have changed. https://www.petrockblock.com/retropie/retropie-downloads/download-info/retropie-sd-card-image-for-rpi-version-1/

[herbfargus]

pm me and I will send you the exact files i have working on my pi.

[herbfargus]

The best way I’ve found I to log into winscp as root instead of pi and then you can just rename it like you would any file name.

or if you are in the command line make sure to use sudo first.

[herbfargus]

OK! QUICK AND DIRTY HACK!

I was able to get it to work but it takes a little configuration in 3 file locations:
/home/pi/RetroPie-Setup/scriptmodules/supplementary/splashenable.sh
you’ll change every instance inside of the file that says “asplashscreen” to “jsplashscreen” (except the instance that refers to a folder directory rather than a file)

rp_module_id="splashenable"
rp_module_desc="Enable/disable Splashscreen"
rp_module_menus="3+"
rp_module_flags="nobin"

function set_enableSplashscreenAtStart()
{
    clear
    printHeading "Enabling custom splashscreen on boot."

    getDepends fbi

    chmod +x "$scriptdir/supplementary/asplashscreen/jsplashscreen"
    cp "$scriptdir/supplementary/asplashscreen/jsplashscreen" "/etc/init.d/"

    find $scriptdir/supplementary/splashscreens/retropieproject2014/ -type f > /etc/splashscreen.list

    # This command installs the init.d script so it automatically starts on boot
    update-rc.d jsplashscreen defaults

    # not-so-elegant hack for later re-enabling the splashscreen
    update-rc.d jsplashscreen enable

#     # ===========================================
#     # TODO Alternatively use plymouth. However, this does not work completely. So there is still some work to be done here ...
#     # instructions at https://github.com/notro/fbtft/wiki/FBTFT-shield-image#bootsplash
#     apt-get install -y plymouth-drm

#     echo "export FRAMEBUFFER=/dev/fb1" | tee /etc/initramfs-tools/conf.d/fb1

#     if [[ ! -f /boot/$(uname -r) ]]; then
#         update-initramfs -c -k $(uname -r)
#     else
#         update-initramfs -u -k $(uname -r)
#     fi
#     imgname=$(echo "update-initramfs: Generating /boot/initrd.img-3.12.20+" | sed "s|update-initramfs: Generating /boot/||g")
#     echo "initramfs=$imgname" >> /boot/config.txt

#     echo "splash quiet plymouth.ignore-serial-consoles $(cat /boot/cmdline.txt)" > tempcmdline.txt
#     cp /boot/cmdline.txt /boot/cmdline.txt.bak
#     mv tempcmdline.txt /boot/cmdline.txt

#     mkdir -p "/usr/share/plymouth/themes/retropie"
#     cat > "/usr/share/plymouth/themes/retropie/retropie.plymouth" << _EOF_
# [Plymouth Theme]
# Name=RetroPie Theme
# Description=RetroPie Theme
# ModuleName=script

# [script]
# ImageDir=/usr/share/plymouth/themes/retropie
# ScriptFile=/usr/share/plymouth/themes/retropie/retropie.script
# _EOF_

#     cat > "/usr/share/plymouth/themes/retropie/retropie.script" << _EOF_
# # only PNG is supported
# pi_image = Image("splashscreen.png");

# screen_ratio = Window.GetHeight() / Window.GetWidth();
# pi_image_ratio = pi_image.GetHeight() / pi_image.GetWidth();

# if (screen_ratio > pi_image_ratio)
#   {  # Screen ratio is taller than image ratio, we will match the screen width
#      scale_factor =  Window.GetWidth() / pi_image.GetWidth();
#   }
# else
#   {  # Screen ratio is wider than image ratio, we will match the screen height
#      scale_factor =  Window.GetHeight() / pi_image.GetHeight();
#   }

# scaled_pi_image = pi_image.Scale(pi_image.GetWidth()  * scale_factor, pi_image.GetHeight() * scale_factor);
# pi_sprite = Sprite(scaled_pi_image);

# # Place in the centre
# pi_sprite.SetX(Window.GetWidth()  / 2 - scaled_pi_image.GetWidth () / 2);
# pi_sprite.SetY(Window.GetHeight() / 2 - scaled_pi_image.GetHeight() / 2);
# _EOF_

#     plymouth-set-default-theme -R retropie
#     # =============================
}

function set_disableSplashscreenAtStart()
{
    clear
    printHeading "Disabling custom splashscreen on boot."

    update-rc.d jsplashscreen disable

    # # TODO plymouth command. Not used yet ...
    # sed -i 's|splash quiet plymouth.ignore-serial-consoles ||g' /boot/cmdline.txt
}

function configure_splashenable() {
    cmd=(dialog --backtitle "$__backtitle" --menu "Choose the desired boot behaviour." 22 86 16)
    options=(1 "Disable custom splashscreen on boot."
             2 "Enable custom splashscreen on boot")
    choices=$("${cmd[@]}" "${options[@]}" 2>&1 >/dev/tty)
    if [[ -n "$choices" ]]; then
        case $choices in
            1) set_disableSplashscreenAtStart
               dialog --backtitle "$__backtitle" --msgbox "Disabled custom splashscreen on boot." 22 76
                            ;;
            2) set_enableSplashscreenAtStart
               dialog --backtitle "$__backtitle" --msgbox "Enabled custom splashscreen on boot." 22 76
                            ;;
        esac
    fi
}

/home/pi/RetroPie-Setup/supplementary/asplashscreen/asplashscreen
– rename to: /home/pi/RetroPie-Setup/supplementary/asplashscreen/jsplashscreen
then replace every reference in the newly renamed file of “asplashscreen” to “jsplashscreen”

#! /bin/sh
### BEGIN INIT INFO
# Provides:          jsplashscreen
# Required-Start:    dbus
# Required-Stop:
# Default-Start:     S
# Default-Stop:
# Short-Description: Show custom splashscreen
# Description:       Show custom splashscreen
### END INIT INFO

do_start () {

    while read splashline; do
        echo Playing splash video or image $splashline
        isMovie=$(echo $splashline | grep -o ".mov\|.mp4\|.mkv\|.3gp\|.mpg")
        if [ -z "$isMovie" ]; then
            /usr/bin/fbi -T 1 -once -t 10 -noverbose -a $splashline
            sleep 12
        else
            omxplayer $splashline
        fi
    done </etc/splashscreen.list
    exit 0
}

case "$1" in
  start|"")
    do_start &
    ;;
  restart|reload|force-reload)
    echo "Error: argument '$1' not supported" >&2
    exit 3
    ;;
  stop)
    # No-op
    ;;
  status)
    exit 0
    ;;
  *)
    echo "Usage: jsplashscreen [start|stop]" >&2
    exit 3
    ;;
esac

:

/etc/init.d/asplashscreen
-Rename to /etc/init.d/jsplashscreen
This will the exact same file as the code above- so just repeat the same steps

now place the video you want as your splash in this directory:
/home/pi/RetroPie-Setup/supplementary/splashscreens/video

install omxplayer (if you haven’t already)
sudo apt-get install omxplayer

then enable splashcreen in the setup script and then choose the splashcreen you added (the folder named “video”):

cd RetroPie-Setup
sudo ./retropie_setup.sh

choose option #3 setup
choose option #325 and enable the splashscreen
choose option #326 and select the folder that you added (in my case it was the folder named "video") 

sudo reboot.

Now your video should play. This should be the only time you should have to change these configurations. In the future you can just change your splashcreens through the setup script.

@mike – if this doesn’t work…. well it better ha ha.

note- the video may take 10-15 seconds to start from the boot sequence. you may also have to try other letters than J depending on how long your video is= i realised when i chose shorter videos I ran into the dbus error again so I had to go down a few letters to N.

[herbfargus]

@lightthief

I’ve yet to figure at how to hide the text between games (that may be specific to each emulator). I’ve usually leave it so I know what the error is if a ROM doesn’t work.

@ Mike Manley:

Another thing you could check is the video encoding. The recommended encoding for omxplayer is H264 MPEG4. (But if my video on mine works it should work on yours too)

***Update: I have tested this method with a fresh install of 2.6 and it does not work. I get a dbus error upon boot. It is an issue with omxplayer and newer firmware, not the asplashcreen code.
(mplayer does currently work but it is very sluggish)

If it still doesn’t work you may want to just start from a fresh 2.6 image. I’m currently developing a blog as I configure my 2.6 image on my raspberry pi B+, I’m doing it step by step so anyone can follow it. When I get it up and working I’ll post the link. If I’m really ambitious I may create some YouTube videos.

[herbfargus]

Ha ha my goodness. Which image are you using? Are you on a B+ or Pi 2? Are you using an hdmi cable or the 3.5 mm jack?My pi 2 will be here any day now and I’m going to load the 2.6 image starting right from the beginning just to make sure it works. I’ve read up on the dbus error issue and that may have come from using rpi-update (its seems to have been a recent issue with omxplayer) or updated firmware. as far as I understand it the error originates from loading too quickly before the other required services for omxplayer to work start.
[REDACTED]
see here for a solution:
http://www.raspberrypi.org/forums/viewtopic.php?t=97693&p=679064

Mplayer works with the current code (if you change omxplayer to mplayer):

sudo apt-get install mplayer

but it is much more sluggish than omxplayer

[herbfargus]

It’s not a dumb question, it took me forever this week to figure that very thing out. So by the very nature of splashscreens running they do consume some of your processing power and can slow down boot times a bit (to be honest in my case it never slowed it down more than 10 seconds or so), but you can also have programs running in the background. In the above script at the end of the line there is a “&” which basically tells the underlying programs to run while the splashscreen is running, if you remove that, your splash screen video can be 20 minutes long and then once it finishes, emulationstation will open up, otherwise if you leave that “&” there, once emulationstation loads, it will cut your video off and load up (which I wanted it to do for mine so that worked out great).

[herbfargus]

This also looks like more like what you are talking about. looks like its already been done:

Splashscreen Randomizer

p.s those intro videos are pretty alright. makes my attempts look juvenile ha ha

granted though in comparison to hyperspin, emulationstation looks a whole lot classier. Aloshi and Nils did a really good job.

[herbfargus]

This script should ideally do what you are thinking of. You might have to make some modifications but it gives the general idea. Give it a go and let me know what you come up with.

https://github.com/retropie/RetroPie-Setup/pull/668

[herbfargus]

Alright so I’ve been thinking about this pretty much all day and I’ve come up with a few things (BTW your video is fantastic- much cooler than mine)

So. A wonderful person named free5ty1e came up with an alternate code that quite frankly is much better than mine. I tested it today and it works swimmingly (I’m currently on the 2.4 beta image but I’m going to try and start fresh from the 2.6 image this weekend just to make sure it works there too.)

Here’s what I did: Just to eliminate any issues I located two files:
sudo nano /etc/init.d/asplashscreen
sudo nano /home/pi/RetroPie-Setup/supplementary/asplashscreen/asplashcreen

and changed their code to look like this:

#! /bin/sh
### BEGIN INIT INFO
# Provides:          asplashscreen
# Required-Start:
# Required-Stop:
# Default-Start:     S
# Default-Stop:
# Short-Description: Show custom splashscreen
# Description:       Show custom splashscreen
### END INIT INFO

do_start () {

    while read splashline; do
        echo Playing splash video or image $splashline
        isMovie=$(echo $splashline | grep -o ".mov\|.mp4\|.mkv\|.3gp\|.mpg")
        if [ -z "$isMovie" ]; then
            /usr/bin/fbi -T 1 -once -t 10 -noverbose -a $splashline
            sleep 12
        else
            omxplayer $splashline
        fi
    done </etc/splashscreen.list
    exit 0
}

case "$1" in
  start|"")
    do_start &
    ;;
  restart|reload|force-reload)
    echo "Error: argument '$1' not supported" >&2
    exit 3
    ;;
  stop)
    # No-op
    ;;
  status)
    exit 0
    ;;
  *)
    echo "Usage: asplashscreen [start|stop]" >&2
    exit 3
    ;;
esac

:

Then you go into the setup script:

cd RetroPie-Setup
sudo ./retropie_setup.sh

then select #3 Setup
go to #325 Enable/Disable splash screen
Choose Enable splash Screen
then choose #326 select splashscreen
Then scroll down and select the folder you added named video
sudo reboot

and hopefully…. when it reboots your video will play.

The beautiful thing about this updated script is you shouldn’t have to go into all of your configs everytime you want to change a video, you should just be able to change it in the setup script just like you would a static image (and if you want to go back to using images instead of videos its no problem at all)

[herbfargus]

There will always be a little bit of time from the time you power your pi on to when the video initialises since it has to load the boot sequence and the video player. I outlined how to hide all of the boot text in the post above. (I tested it last night and it was a solid black screen with no text at all until the video started.) The video plays within the first 10 seconds of booting.

BTW splash screen images are already a default feature in retropie- you can choose from a bunch in the set up script or add your own as well.

[herbfargus]

no problem, I wondered the same thing when it happened to me :)

[herbfargus]

That isn’t a loading symbol, usually that signifies that your power supply is insufficient. For example I had a good power supply with no issues, and then I tested another cheap one from china and all the sudden that magical rainbow box showed up… Make sure your power supply is at least 5v 2A. I bought one from kootek on amazon that works well, as does another I got from Canakit.

[herbfargus]

links are here:

Mushberry Video Splashscreen

Ok, so not quite as swanky as it could be but it does beat a static image. I’m still working on a few other ideas. (I can piece things together from other people’s work but it’s a fine line of copyrights and such so I’m trying to make things as original as I can to avoid legalities while respecting the hard work other people have done.)

I’ve found the best option for me was to find all the games I really like playing, do a screen capture while I play on my laptop and then squish them all together into a montage with remixed video game music in the background. That way you can customise it your childhood gaming experience while also getting it to boot with the right time scale for your pi.

[herbfargus]

Ok after much deliberation I found out my problem: I forgot an “&” in the asplashcreen script (which evidently is what tells the computer to run programs while your video plays)- so to walk anyone else through it:

Getting a video splash screen up and running:

sudo apt-get install omxplayer

Add your video using winscp (I just created a folder in the /home/pi/RetroPie-Setup/supplementary/splashscreens called video and I stuck my .mp4 video in there i.e. /home/pi/RetroPie-Setup/supplementary/splashscreens/video/myvideo.mp4)

sudo nano /etc/init.d/asplashcreen

Comment Out:

#    line=$(head -n 1 /etc/splashscreen.list)
#   isMovie=$(echo $line | grep -o "*.mkv")
#  if [ -z "$isMovie" ]; then
#   /usr/bin/fbi -T 2 -once -t 20 -noverbose -a -l /etc/splashscreen.list &
#else
# mplayer $line &
#fi

add:

/usr/bin/omxplayer -o hdmi /home/pi/RetroPie-Setup/supplementary/splashscreens/final/myvideo.mp4 &

Reboot and you are golden. I made my intro video 40 seconds and it ends right at the start of the emulationstation splash screen.

alternate options to clean up the boot text:

in /boot/cmdline.txt make it look like this:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty3 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait loglevel=3 quiet

you can also add logo.nologo to make the raspberry pi logo disappear (i like to keep it because I at least know my pi is working that way.)

EDIT see here for updated code: https://www.petrockblock.com/forums/topic/mushberry-video-splashscreen/

[herbfargus]

The fact that the only thing you see is the raspberry pi logo means that you edited the cmdline text right otherwise you would see all of the scrolling text. I take it it still boots up into emulationstation but doesn’t start the video? (Which BTW maybe I should have added a caveat to maybe not change the boot text until the video just in case it didn’t work so you could read the error it puts out) Anyhow if the video is not playing that means either
-omxplayer wasn’t installed correctly
-the path to the video specified in the asplashcreen file is incorrect (hopefully its this one- easy to fix) really your video can be placed anywhere, just make sure that you have the right path listed in the asplashcreen file.
– or I’m an idiot and gave you flawed intsructions… (Most likely)

Verify your asplashcreen file and then if that’s in order see If you can revert the cmdtxt changes and see what error it spits out.

to eliminate any discrepancies here is my full working asplashcreen.

#! /bin/sh
### BEGIN INIT INFO
# Provides:          asplashscreen
# Required-Start:
# Required-Stop:
# Default-Start:     S
# Default-Stop:
# Short-Description: Show custom splashscreen
# Description:       Show custom splashscreen
### END INIT INFO

do_start () {

/usr/bin/omxplayer -o hdmi /home/pi/RetroPie-Setup/supplementary/splashscreens/video/mushberryintro.mp4 &

#    line=$(head -n 1 /etc/splashscreen.list)
#   isMovie=$(echo $line | grep -o "*.mpg")
#  if [ -z "$isMovie" ]; then
#   /usr/bin/fbi -T 2 -once -t 20 -noverbose -a -l /etc/splashscreen.list &
#else
# mplayer $line &
#fi

exit 0
}

case "$1" in
  start|"")
    do_start
    ;;
  restart|reload|force-reload)
    echo "Error: argument '$1' not supported" >&2
    exit 3
    ;;
  stop)
    # No-op
    ;;
  status)
    exit 0
    ;;
  *)
    echo "Usage: asplashscreen [start|stop]" >&2
    exit 3
    ;;
esac

:

[herbfargus]

Which image are you using? The 2.4 image didn’t have it enabled by default so you’d have to go into the setup script:

CD RetroPie-Setup
Sudo ./retropie_setup.sh
Update script
Reboot
From the setup script select usbromservice and enable/update that and see if it changes anything.

I’ve only transferred ROMs with a flash drive not an external hard drive but I don’t know if that makes a difference.

You could also look in the ROMs folder on your external hard drive and see if it copyed it in there or rename the ROMs folder to something else and see if that changes anything.

[herbfargus]

@robertybob

Yes, by commenting out those lines it does override the static image splash screen I’m sure there is a way to just add it to the asplashscreen file while allowing the static screens to still Be an option but I don’t know enough code to make that work in the asplashcreen file so it was just a quicker fix for me to replace it with what I know worked (but you can always just revert it if you want your static image back).

-BTW if someone knows how to make omxplayer work in the asplashcreen file while still giving the option for using static images with fbi- (for example being able to choose a video splash screen from the setup script like we are able to choose static images) I’m all ears (I’m not sure if thats what they were going for with the mplayer command in the script but i couldnt figure it out)

*** EDIT the above issues are solved with the script in post 88050 below (big thanks to free5y1e)

I left it at 8 seconds because it allows people to expand it depending on their preferences and their specific boot times (raspi2 boots faster and the amount of roms people have might affect loading times for emulationstation as well). What I ended up doing for my particular setup- I took a bunch of videos of gameplay from each emulator, mashed them together and threw a Zelda remix for the audio and it ended up being about 40 seconds (which was the original boot time on my pi from boot to the emulation station loading screen). If you want a longer video intro without the emulationstation splash screen cutting into it, just remove the “&” in the line here:

/usr/bin/omxplayer -o hdmi /home/pi/RetroPie-Setup/supplementary/splashscreens/video/mushberryintro.mp4 &

I also have modified versions of the video (instead of saying your childhood in a box I have one that just says loading and then I repeated the video a bunch so it looked like a scrolling loading screen.) If you would like the one that says loading I can add that link too. I’m also open to new slogan ideas. if anyone wants the same layout with different colours or a different slogan let me know and I’ll try and make it in my free time.

[herbfargus]

Hey thanks for the tip! I don’t know why I didn’t do this before… Makes my life easier for sure.
I use an app for android called raspi ssh which does essentially the same thing.

[herbfargus]

I’m not sure if this is still an issue with the 2.5 image but in order for me to get a full screen on my 42″ 1080p vizio television I first had to get rid of the black borders by changing the boot/config.txt by deleting the “#” in the line that says #disable_overscan=1 I then changed my video settings in the emulators to CEA 4 (720p) by pressing m when I started a rom. Then as Roo stated, to get that final full screen effect I changed the settings on my tv from “normal” to “stretch” and it worked beautifully. (except some of the vertical scrolling shooters in mame as their aspect ratio was never going to stretch on any kind of wide screen) Just remember to switch the stretch setting back to normal when you go into emulationstation as it might inhibit your view of the list of games.

Floob made a couple videos that, though they are about the 2.4 image, the video options should still apply to image 2.5

[Author]

Posts