Splashscreen no sound: i2s card not initialized before bootup

[StonedEdge]

Hi guys,

I'm wondering if there is a way to get sound out of my mp4 splashscreen. The sound works just fine in Emulation Station and games, however it doesn't seem to work no matter what I do - I've read through most of the threads here and looks like no one has found a solution for i2s audio cards. I tried editing the asplashscreen.sh to replace the omxplayer device to "alsa" but that didn't seem to fix anything.

Anyone have any broad net solutions to fix this? Is delaying the splashscreen after the boot process even possible? Perhaps not using omxplayer but some other hw-accel video playback tool from the command line?

Kind regards,
Ben

[StonedEdge]

Okay I did get it to work! However, Bluetooth startup usually always fails with the audio clip being decoded. I changed “both” to “alsa:hw:0,0” here (Line 46) https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/splashscreen/asplashscreen.sh.

Would anyone be able to assist in letting me know how to either slow down the boot process (I.e wait until the previous command is fully executed before moving on in the boot process) or perhaps shift the more intensive processes ahead of the video? I’m using RetroPie of course.

[mitu]

@stonededge said in Splashscreen no sound: i2s card not initialized before bootup:

However, Bluetooth startup usually always fails with the audio clip being decoded

Does this mean that if you restart the Bluetooth service(s) after boot, it works ?
Not sure what you mean by 'slow down the boot process'. If you want to re-order the services' start sequence, you can do so by using dependencies between services, which is usually handled by systemd and the unit (service) configuration file.

[StonedEdge]

@mitu Hi! I actually haven’t tried to restart Bluetooth yet after the system is fully booted. Is there something I can enter in the command line to get it to reset? All I can say is that Bluetooth services are successfully started when audio is removed from the splash screen intro (it’s about 10 seconds). When audio is present the Bluetooth services immediately after the sound card fail. Everything else seems to start up.

I’ve just checked the boot script on screen to see the error “failed to configure Bluetooth UART”, can’t remember exactly what it said. This is executed right after the i2s sound card scripts, so I am wondering what the best solution would be. Perhaps switching the boot sequence services as you said would be better, to have Bluetooth initialize well before the video sequence or well afterward as I imagine it’s relatively process intensive compared to other services? I’ll look into this over the weekend but would appreciate any resources if you have any.

[mitu]

@stonededge said in Splashscreen no sound: i2s card not initialized before bootup:

Is there something I can enter in the command line to get it to reset?

You can restart the Bluetooth services by running the following commands:

sudo systemctl restart bthelper
sudo systemctl restart bluetooth

Also, make sure you're using the latest OS packages, the bluetooth service had an issue a few versions ago and it would not initialize correctly the Pi built-in Bluetooth. You haven't offered any details about your setup, so I'm assuming you're using a Pi4 of some sorts.

[StonedEdge]

@mitu I’m using the Compute Module 4 Lite, 2GB ram version with WiFi - latest version of RetroPie buster image.

[StonedEdge]

@mitu Could you please be more specific in terms of what lines need to be changed from what file and folder to modify the order of the service start up? The system folder contains thousands of different files, and I'm quite confused on which one (and its directory) needs to be altered.

I did try to reset bluetooth from the above two command lines you gave me, but this didn't seem to help.

[mitu]

@stonededge said in Splashscreen no sound: i2s card not initialized before bootup:

I did try to reset bluetooth from the above two command lines you gave me, but this didn't seem to help.

In this case the re-ordering of services startup may not be of help. Maybe the I2S configuration has disabled something needed by the bluetooth service ?

An comprehensive document on how systemd's units work and how dependencies can be managed can be found here.