There is a chance that this sound card works now:
Posts by Da Flex
-
-
valdan Please test LE version 9.2.8 on RPi3B+. If I remember correctly, that version is working.
-
-
OK, I've been tested your files in the right order, with and without Goom visualization. 5s crossfade activated in music settings.
All three files are played without a crash. When "Earth, Wind & Fire" starts to fade out, I hear a short interruption, but that's all.
So I guess it's an x86-specific issue of the Kodi player. Your options:
- re-encode everything to 44.1kHz
- don't use the crossfade option in music settings
- write an x86-specific bug report at Kodi forum
-
Sounds good. BTW: RPi with HAT needs a special case.
-
This is tricky. Maybe a Docker container works:
-
My current 5.1 surround system has optic audio input.
How would one get proper surround sound from the RPi4 (I found one almost free
)My setup is RPi --HDMI--> TV --TOSLINK--> AVR.
If your TV has no TOSLINK output, buy an HDMI audio extractor. You can use the second RPi4 HDMI output (HDMI-1) for that.
-
Please describe the process of your MP3 playback for song 1-3.
I want to reproduce the bug on my RPi3B+ by playing:
- 44.1kHz
- 48kHz
- 44.1kHz
Not sure whether it's a bug in Kodi player or FFMPEG.
-
Samba on Fritzbox is super slow. Most Raspberry Pi devices will provide better performance.
-
From where dou you get the information in the log, that the crash is related to FFMPEG.
That's not a fact, just a theory. Kodi crashes by "segmentation fault", so I guess the FFMPEG error "[mp3float] Header missing" leads to wrong memory management. The other errors in the log are more common, and well known.
If you can separate an MP3, which generates the error, try to play it as a loop, until it crashes the system. That's the MP3 we need to reproduce the bug. It's probably copyright protected, so I guess we have to share the file in private mode. Don't post it here.
-
Crashlog : https://paste.libreelec.tv/alert-impala.log
Still the same FFMPEG error.
I will try the downloaded "Hungry Lucy" over night because this is not my favorite music to hear ...
Yes, please. I want to see a clean MP3 playback.
If it happens again with Kodi samples, then FFMPEG could be the problem.
-
Sorry, no reply from our internal dev channel. I can see a difference between both crash logs.
LE 12: Program terminated with signal SIGBUS, Bus error.
LE 13: Program terminated with signal SIGSEGV, Segmentation fault.
Now I found something new, which is related to FFMPEG (LE 12 and LE 13 crash logs):
Code2025-02-23 18:14:41.045 T:1229 error <general>: ffmpeg[0x149a2d00]: [mp3float] Header missingMy theory is that some of your MP3s are encoded wrongly, and result in system crashes.
You can get correctly encoded MP3 files from the Kodi sample library.
Please try some of the correctly encoded MP3 files, and report back.
-
What filesystem for a large storage then many people use? Since I am a Linux guy, I need best compatibility with it.
For compatibility most people use exFAT. That file system is readable on Windows, MacOS and Linux.
-
In my system autostart.sh is in /storage/.config: is it the good place?
Yes, that's the one and only place.
-
BTW, why did you single out that one warning line about waiting for a buffer? What does that tell you?
It happens multiple times in the log. I've seen that often with bad cables, but usually as a longer sequence.
Let's wait for the experts now. The log also provides more complicated messages.
-
Nope. No GUI error messages with the latest DAZN update. It's trying to load the stream, but still fails.
-
Then it could be a USB issue. Try the latest LE 13 nightly. If the issue remains, post a link to a log:
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Code
2025-02-23 16:28:01.529 T:1431 warning <general>: OutputPicture - timeout waiting for bufferMake sure your HDMI cables are conform to HDMI 2.0 or 2.1 standard. Cable issues can produce random errors (depending on electromagnetic surrounding), so you're probably not hallucinating.
