[Milhouse]

LibreELEC:~ # md5sum /storage/.cache/splash.h264 2>/dev/null
629eb3f5a2927cee49893fee8745bb42 /storage/.cache/splash.h264
LibreELEC:~ # time /usr/bin/hello_video.bin /storage/.cache/splash.h264
Command exited with non-zero status 254
real 0m 0.01s
user 0m 0.00s
sys 0m 0.00s

Strange. It's the exact same size as the LE splash video, but it's not the same - your video file is corrupt.

When the video file is downloaded it is written to a temporary file name, then the contents is checked against an md5 hash which should mean it is not possible to download a corrupt video file. The correct hash is:

Code:

rpi22:~ # md5sum /storage/.cache/splash.h264
fad45affade4b2f1eff3080d64f8e75d  /storage/.cache/splash.h264

So I'm not sure where this video file came from, but it's corrupt (or has become corrupt?) in which case delete it and download a new uncorrupted video file:

Code:

rm /storage/.cache/splash.h264
rm -f /storage/.config/splash.disable
systemctl start kodi-splash

Once you see the "Splash video download" successful notification appear in Kodi, reboot to see the splash video on the next boot.

@popcornmix: I've just created a completely bogus video file which seems to "hang" hello_video.bin:

Code:

dd if=/dev/zero of=/storage/corrupt.h264 bs=1M count=1
/usr/bin/hello_video.bin /storage/corrupt.h264

Just an FYI really, as we shouldn't be downloading corrupted video files (in theory), and this is only an experimental feature.