You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't happen very often, but I guess "too often" to ignore:
The sound stops playing during the night
Any ideas or suggestions to yield a suspect list? I have looked through the systemd logs using journalctl:
journalctl -S yesterday | less
I have used every search term I can think of: blue, alsa, rainstorm, mpg123. Nothing "interesting" shows up.
However, in the cron job I use to start the rainstorm script, I did find this:
Playing MPEG stream 1 of 1: rainstorm.mp3 ...
MPEG 1.0 L III cbr128 44100 j-s
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
Following are my root crontab entries to start rainstorm:
It seems to reduce the noise/static I hear through the BT speaker
Following is the complete rainstormlog.txt from last night (note that time is UTC/GMT). I've been a bit lazy & haven't recorded more date/time stamps, but it appears that the trouble (underrun occurred) started during the "3rd round" playback; mpg123 stopped (Terminated) during the "4th round". And then the alsa error -19 at the 42:39 mark. Which seems strange since no log entry appeared in the systemd journal?!
But PLEASE NOTE: I have found instances of the underrun occurred error in rainstormlog.txt that apparently did not result in a Termination of mpg123. I did run an apt upgrade earlier in the day yesterday that installed a new kernel & new firmware.
Tue 30 Apr 03:05:01 UTC 2024; loop 1, /usr/local/bin/rainstorm
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
Attempting to connect to DF:45:E9:00:BE:8B
[^AESC[0;93m^BCHG^AESC[0m^B] Device DF:45:E9:00:BE:8B Connected: yes
[^AESC[0;92m^BNEW^AESC[0m^B] Endpoint /org/bluez/hci0/dev_DF_45_E9_00_BE_8B/sep1
[^AESC[0;92m^BNEW^AESC[0m^B] Endpoint /org/bluez/hci0/dev_DF_45_E9_00_BE_8B/sep2
[^AESC[0;92m^BNEW^AESC[0m^B] Transport /org/bluez/hci0/dev_DF_45_E9_00_BE_8B/sep1/fd0
Connection successful
Tue 30 Apr 03:05:04 UTC 2024; loop 2, /usr/local/bin/rainstorm
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
version 1.31.2; written and copyright by Michael Hipp and others
free software (LGPL) without any warranty but with best wishes
Directory: /home/pi/
Playing MPEG stream 1 of 1: rainstorm.mp3 ...
MPEG 1.0 L III cbr128 44100 j-s
[73:05] Decoding of rainstorm.mp3 finished.
Playing MPEG stream 1 of 1: rainstorm.mp3 ...
MPEG 1.0 L III cbr128 44100 j-s
[73:05] Decoding of rainstorm.mp3 finished.
Playing MPEG stream 1 of 1: rainstorm.mp3 ...
MPEG 1.0 L III cbr128 44100 j-s
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
[73:05] Decoding of rainstorm.mp3 finished.
Playing MPEG stream 1 of 1: rainstorm.mp3 ...
MPEG 1.0 L III cbr128 44100 j-s
Terminated
mpg123: death by SIGTERM
[src/libout123/modules/alsa.c:write_alsa():242] error: Fatal problem with alsa output, error -19.
[src/libout123/libout123.c:out123_play():700] error: Error in writing audio, wrote only -1 of 2400 (Success?)!
[42:39] Decoding of rainstorm.mp3 finished.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
REF Q&A Discussion: #695
This doesn't happen very often, but I guess "too often" to ignore:
The sound stops playing during the night
Any ideas or suggestions to yield a suspect list? I have looked through the
systemd
logs usingjournalctl
:I have used every search term I can think of:
blue
,alsa
,rainstorm
,mpg123
. Nothing "interesting" shows up.However, in the
cron
job I use to start therainstorm
script, I did find this:Following are my
root crontab
entries to startrainstorm
:I turn wifi OFF because:
Following is the complete
rainstormlog.txt
from last night (note that time is UTC/GMT). I've been a bit lazy & haven't recorded more date/time stamps, but it appears that the trouble (underrun occurred
) started during the "3rd round" playback;mpg123
stopped (Terminated
) during the "4th round". And then thealsa error -19
at the42:39
mark. Which seems strange since no log entry appeared in thesystemd
journal?!But PLEASE NOTE: I have found instances of the
underrun occurred
error inrainstormlog.txt
that apparently did not result in a Termination ofmpg123
. I did run anapt upgrade
earlier in the day yesterday that installed a new kernel & new firmware.Beta Was this translation helpful? Give feedback.
All reactions