Bluetooth - MPD Error - failed to open ALSA Bluetooth

[Tim Curtis]

I'll see if I can repro with my ANKER speaker.

[TheOldPresbyope]

I have no idea how this stream issue kills the Bluez-alsa code.

Hi Kent,

could it be BT goes to sleep (timed powersave...) because there's no audio incoming from the stream (due to those errors, I mean)? Just wandering wild here, but...

I'd guess that's unlikely since we close and open the a2dp sink whenever we stop and then start the stream from the moOdeUI. However, I'm just wag'ging here too

In 12 hours I'll be on a plane to the West Coast and won't return 'til late next week. Maybe someone will pick this ball up and run with it.

Regards,
Kent

[Tim Curtis]

I have no idea how this stream issue kills the Bluez-alsa code.

Hi Kent,

could it be BT goes to sleep (timed powersave...) because there's no audio incoming from the stream (due to those errors, I mean)? Just wandering wild here, but...

I'd guess that's unlikely since we close and open the a2dp sink whenever we stop and then start the stream from the moOdeUI. However, I'm just wag'ging here too

In 12 hours I'll be on a plane to the West Coast and won't return 'til late next week. Maybe someone will pick this ball up and run with it.

Regards,
Kent

Just a data point but no issues playing BBC 1 Worldwide to ANKER speaker for past half hour.

[willyside]

Good Afternoon,

I have been trying, and mostly succeeding, at getting my SiriusXM subscription working via sxm-player (per the lovely FAQ) on moOde 8.2.5, on a Pi-Zero W. However, I am running into an interesting condition, at least superficially similar to what was discussed earlier in this thread. 

I have a JustBoom DAC Zero installed, and when output is set to local, I can listen to SXM channels through it without problem. However, when I pair and connect a bluetooth headset (OpenMove by AfterShokz), and switch output to Bluetooth, attempting to play the same stream gets me:

"Failed to open "ALSA Bluetooth" (alsa); Error opening ALSA device "_audioout"; snd_pcm_hw_params() failed: Invalid argument"

On the other hand, I have no problem playing other stations (e.g., Ambient Sleeping Pill) using the same bluetooth headset (or, for that matter, local output). 

I realize that use of sxm-player isn't something I have a right to expect to be supported by moOde developers, but I was curious if anyone had any ideas or things I might try. It feels like an issue that could be relevant to how a certain category of stream is sent to a bluetooth output, as opposed to one particular to the streams delivered by sxm-player. 

If it helps, here is the relevant portion of my mpd log for a successful play of Ambient Sleeping Pill to bluetooth output:

Code:

D: bluealsa-pcm.c:895: Getting BlueALSA PCM: PLAYBACK 20:74:CF:A8:F3:A2 a2dp
D: bluealsa-pcm.c:769: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Setting constraints
D: bluealsa-pcm.c:396: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Initializing HW
D: bluealsa-pcm.c:416: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: FIFO buffer size: 4096
D: bluealsa-pcm.c:422: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Selected HW buffer: 6 periods x 16000 bytes <= 96004 bytes
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:477: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Prepared
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:316: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Starting
D: bluealsa-pcm.c:176: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Waiting for first period of frames
D: bluealsa-pcm.c:183: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Starting IO loop: 25

Here is the relevant portion of my mpd log for an unsuccessful play of SiriusXM First Wave to bluetooth output:

Code:

D: bluealsa-pcm.c:895: Getting BlueALSA PCM: PLAYBACK 20:74:CF:A8:F3:A2 a2dp
D: bluealsa-pcm.c:769: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Setting constraints
D: bluealsa-pcm.c:385: /org/bluealsa/hci0/dev_20_74_CF_A8_F3_A2/a2dpsrc/sink: Closing
Feb 22 12:01 : exception: Failed to open "ALSA Bluetooth" (alsa); Error opening ALSA device "_audioout"; snd_pcm_hw_params() failed: Invalid argument
Feb 22 12:01 : exception: Failed to open "ALSA Bluetooth" (alsa); Error opening ALSA device "_audioout"; snd_pcm_hw_params() failed: Invalid argument
Feb 22 12:01 : player: problems opening audio device while playing "http://127.0.0.1:9999/firstwave.m3u8"

And here is the relevant portion of my mpd log for a successful play of SiriusXM First Wave to local output:

Code:

Feb 22 12:02 : player: played "http://127.0.0.1:9999/firstwave.m3u8"

For good measure, here is the relevant portion of my mpd log for a successful play of Ambient Sleeping Pill to local output:

Code:

Feb 22 12:20 : player: played "http://radio.stereoscenic.com/asp-h"

I'm guessing there may be more in the way of log output that could be helpful, though I'm not sure which logs those would be. 

In any case, I'll take any help I can get. 

Regards,
William