Thank you for your donation!


Problem: Audio out via BT unstable
#1
Hi,

I discovered a quite reproducible problem. After some (1-2) hours of audio output via BT the music stops while the time counter is still running and BT connection is still active. Under 4.0 the UI crashed completely, raspi was not even accessible via SSH. Under 4.1 now, the UI stays alive and BT output can be reactivated by selecting default audio output and afterwards BT output again.

Raspi 3B, Moode 4.1, 7" touch, default audio out via HDMI to Harman Kardon AVR, Teufel BT speaker as alternative. 

Since the problem always occurs after some hours of output, I suppose it might be connected to some sort of buffering problem?

Regards
Jörg
Reply
#2
For me, the new 5.49 Bluetooth stack in moOde 4.1 with a Pi-3B+ has been very reliable except wth my old iPad mini which only plays for about a minute then abruptly disconnects. My iPhone 5 on the other hand will play all day, and same for playing to recently acquired ANKER Bluetooth speaker.

YMMV

Btw, a new easier to use Bluetooth Config is almost finished :-) I'll post some screen shots when testing is complete.

-Tim
Reply
#3
(04-14-2018, 03:37 PM)Tim Curtis Wrote: For me, the new 5.49 Bluetooth stack in moOde 4.1 with a Pi-3B+ has been very reliable except wth my old iPad mini which only plays for about a minute then abruptly disconnects. My iPhone 5 on the other hand will play all day, and same for playing to recently acquired ANKER Bluetooth speaker.

YMMV

Btw, a new easier to use Bluetooth Config is almost finished :-) I'll post some screen shots when testing is complete.

-Tim

Hm. It´s not a question of reliability of the connection with Moode as BT sink since this is not my usage scenario. Also, the connection to my speaker does not break. There is simply no music playing after a certain time, while the time counter on the playback tab is still running. Perhaps it could be helpful to take a look into one of the log files. Please advise: Which file and how I could I retrieve / post it from a windows machine via SSH (putty)? Thanks in advance!

Regards
Jörg
Reply
#4
Examine the MPD log. It may show whether the audio stopped because the music source (file or url) could not be accessed or because there was some sort of issue with its output connection to the Bluetooth audio device.

cat /var/log/mpd/log

-Tim
Reply
#5
(04-14-2018, 08:48 PM)Tim Curtis Wrote: Examine the MPD log. It may show whether the audio stopped because the music source (file or url) could not be accessed or because there was some sort of issue with its output connection to the Bluetooth audio device.

cat /var/log/mpd/log

-Tim
This is it:


Code:
Apr 14 15:40 : player: played "http://192.99.35.215:5286/stream/"
Apr 14 15:41 : player: played "http://192.99.35.215:5286/stream/"
Apr 14 15:41 : player: played "http://192.99.35.215:5286/stream/"
[b]ALSA lib ../../../src/asound/bluealsa-pcm.c:199:(io_thread) PCM FIFO write error: Broken pipe[/b]
[b]Apr 14 16:36 : exception: "ALSA bluetooth" [alsa] failed to play: snd_pcm_writei() failed: Broken pipe[/b]
[b]Apr 14 16:36 : exception: Failed to open audio output[/b]
[b]ALSA lib ../../../src/asound/bluealsa-pcm.c:679:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA transport: No such device[/b]
[b]Apr 14 16:36 : exception: Failed to open "ALSA bluetooth" [alsa][/b]
[b]Apr 14 16:36 : exception: nested: Failed to open ALSA device "btstream": No such device[/b]
[b]Apr 14 16:36 : exception: Failed to open "ALSA bluetooth" [alsa][/b]
[b]Apr 14 16:36 : exception: nested: Failed to open ALSA device "btstream": No such device[/b]
[b]ALSA lib ../../../src/asound/bluealsa-pcm.c:679:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA transport: No such device[/b]
[b]Apr 14 16:36 : exception: Failed to open "ALSA bluetooth" [alsa][/b]
[b]Apr 14 16:36 : exception: nested: Failed to open ALSA device "btstream": No such device[/b]
[b]Apr 14 16:36 : exception: Failed to open "ALSA bluetooth" [alsa][/b]
[b]Apr 14 16:36 : exception: nested: Failed to open ALSA device "btstream": No such device[/b]
Apr 14 16:37 : player: played "http://192.99.35.215:5286/stream/"
Apr 14 16:38 : player: played "http://192.99.35.215:5286/stream/"
Apr 14 16:38 : player: played "http://192.99.35.215:5286/stream/"
ALSA lib ../../../src/asound/bluealsa-pcm.c:199:(io_thread) PCM FIFO write error: Broken pipe
Apr 14 22:12 : exception: "ALSA bluetooth" [alsa] failed to play: snd_pcm_writei() failed: Broken pipe
Apr 14 22:12 : exception: Failed to open audio output
Apr 14 22:12 : player: played "http://192.99.35.215:5286/stream/"

This fits: I started to stream a radio station in the early afternoon and about 1 hour later music stopped. Note: Time counter still running in the playback tab, BT connection to the speaker not broken. After changing to default audio out and changing back to BT audio out at 16:37 the music stopped again at 22:12. Same as before: BT connection still alive, time counter running, UI responsive. Currently I´m playing the same stream via default (HDMI) out.

Oops: I just noticed in "Preview Post" that the ":"+"(" signs from the log are interpreted as similey. Don´t know how to fix this...

Regards
Jörg

Edit: log content marked as "code" (found the button Rolleyes )
Reply
#6
Hi,

The errors indicated a broken Bluetooth connection. This is similar to what I see with my old iPad mini that has flakey Bluetooth.

-Tim
Reply
#7
Hm. This is weird, since the "BT connected" sign on my speaker indicates always still "online". And it´s always possible to reconnect by switching audio out to "default" and immediatedly afterwards back to BT. Too much snake oil for me...  Undecided
Reply


Forum Jump: