Conectar Raspberry Pi por Bluetooth a unos Altavoces.

Lo he probado y no me funciona con esa configuración y ALSA.

¿Algo a tener en cuenta?

Deberías deshabilitar pulseaudio y listo. Acabo de recibir los altavoces bluetooth y en mi portatil (wheezy) funciona sin problemas como comento. La raspi no detecta nada en el scaneo, asi que supongo que es un problema de alimentación usb (tengo un hub con wifi y un pen). Cuando pueda apagarla probaré con solo el bluetooth.

Un saludo

Hola,
ya lo he probado en la raspi con solo bluetooth y wifi conectados. Funciona perfectamente. Primero desabilito el arranque automático de pulseaudio. Luego he comentado la salida ALSA default y he añadido el default bluetooth que comentaba en el post anterior. Luego he editado /etc/bluetooth/audio.conf, reiniciar bluetooth, asociarse con xsimple-agent, reiniciar ALSA y listo. Para comprobar que funciona:

aplay /usr/share/sounds/alsa/Front_Right.wav

Un saludo

Hi

Sorry for writing in English but my Spanish isn't very good. I followed all the instructions from this topic and at this moment sound is heard in the bluetooth headset when entering for example the command
aplay /usr/share/sounds/alsa/Front_Right.wav

Thank you very much for this.

But I have the following problem, the bluetooth headset is connected but when I run :
pactl list short sinks
1 alsa_output.platform-bcm2835_AUD0.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED

There is no bluez_sink. I am running the a raspbmc version of raspbian but from what I read the bluez_sink should load. I feel I'm really close to making this work and I would apreciate any help or tips you can give me.

Thank you

Soy ingles ...

Hace una semana tuve exito con bt altavoces .... ahora, hay solo una mensaje que dice 'connection refused - error 111'..

Ayudas?

Gracias

Soy ingles ...

Hace una semana tuve exito con bt altavoces .... ahora, hay solo una mensaje que dice 'connection refused - error 111'..

Ayudas?

Gracias

Coloca la configuración y pasos que seguiste aquí para ver si es algún problema derivado de ellos.

Hi

Sorry for writing in English but my Spanish isn't very good. I followed all the instructions from this topic and at this moment sound is heard in the bluetooth headset when entering for example the command
aplay /usr/share/sounds/alsa/Front_Right.wav

Thank you very much for this.

But I have the following problem, the bluetooth headset is connected but when I run :
pactl list short sinks
1 alsa_output.platform-bcm2835_AUD0.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED

There is no bluez_sink. I am running the a raspbmc version of raspbian but from what I read the bluez_sink should load. I feel I'm really close to making this work and I would apreciate any help or tips you can give me.

Thank you

I'm looking at your problem. I will try to answer you as soon as possible.

Hi

Sorry for writing in English but my Spanish isn't very good. I followed all the instructions from this topic and at this moment sound is heard in the bluetooth headset when entering for example the command
aplay /usr/share/sounds/alsa/Front_Right.wav

Thank you very much for this.

But I have the following problem, the bluetooth headset is connected but when I run :
pactl list short sinks
1 alsa_output.platform-bcm2835_AUD0.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED

There is no bluez_sink. I am running the a raspbmc version of raspbian but from what I read the bluez_sink should load. I feel I'm really close to making this work and I would apreciate any help or tips you can give me.

Thank you

Hi Alex,

I have the impression that you are mixing the configuration for both ALSA-only (which I explained) and pulse- methods. They are not compatible: either you use pulse (as explained by LoboBlanco) or ALSA (as explained by me). Please, double check your configurations using only one method (the ALSA one requires you to disable or uninstall pulseaudio).

Cheers

Soy ingles ...

Hace una semana tuve exito con bt altavoces .... ahora, hay solo una mensaje que dice 'connection refused - error 111'..

Ayudas?

Gracias

The most likely source of these kind of problems is misconfiguration of /etc/bluetooth/*.conf. Have a look at some hints posted here: https://bbs.archlinux.org/viewtopic.php?id=141760.
If you can't fix it, just remove all bluez-related packages along with their configuration files, install them back and start from scratch.

sudo apt-get autoremove bluez bluez-alsa bluez-tools --purge

Good luck!

Castalla,
here is other fix you can try:
http://wiki.gentoo.org/wiki/Bluetooth_Headset

I read in another forum you posted that It worked in an older install but It doesn't work in a fresh one. Which are the images?

Cheers

@micerinos et al.

I got bt working again - added Disable=Media. Enable=Socket to /bluetooth/audio.conf.

BUT I have run into an even nastier problem.

If I play using aplay -D btdevice test.wav, then it works fine. However, if I then switch back to play sound via the analogue output, after disconnecting the btdevice, then there is awful 'clicking' on the output.

The only solution to get rid of the default clicking is to reinstall the whole Squeezeplug and Squeezelite image again.

Any ideas?

@micerinos et al.

I got bt working again - added Disable=Media. Enable=Socket to /bluetooth/audio.conf.

BUT I have run into an even nastier problem.

If I play using aplay -D btdevice test.wav, then it works fine. However, if I then switch back to play sound via the analogue output, after disconnecting the btdevice, then there is awful 'clicking' on the output.

The only solution to get rid of the default clicking is to reinstall the whole Squeezeplug and Squeezelite image again.

Any ideas?

Can you post the contents of your /etc/asound.conf in the dysfunctional configuration?

Here it is - xx.xx.xx.xx.xx.xx is correct address

Code: Select all

pcm.!default {
type plug
slave.pcm "hw:0,0"
}

ctl.dmixer {
type hw
card 0
}

 pcm.NAME {
      type plug
      slave {
            pcm {
                type bluetooth
                device XX:XX:XX:XX:XX:XX
                profile "auto"
            }
      }
      hint {
           show on
           description "My bluetooth headset"
      }
   }

   ctl.NAME {
      type bluetooth
   }




and I guess NAME is btdevice. I'll try to test your setup as soon as possible. I haven't used jack output since I received my bluetooth speakers. I may be suffering it without knowing.

In the mean time, you can try reloading alsa modules:
sudo alsa force-reload

Or playing silence with different configurations:
aplay -d 1 /dev/zero
aplay -d 1 -r48000 -fS16_LE /dev/zero

Thanks ...

I'm reimaging using the earlier Squeezeplug 5 - I read something about pulseaudio being part of a raspi update.

Going back to zero point!

If you get a chance to stick some phones into the jack ...???!!!

Quick update:

After hours of reimaging, I seem to have a setup which is woorking - at least it hasn't fallen over yet.

It looks as if the card I was using is corrupted in some way ... sounds crazy but everytime I imaged it and used then the clicking was on audio. A different card (higher spec) seems to be working without problems.

I'll test over the next 24 hrs. and report back.

Thanks for your advice.

Que catastrofo!

Okay, it works (almost) .... but when I switch the bt speaker off, then a few seconds later the whole Pi loses its network connection Only solution is a reboot.

Any ideas?

I've come to a STOP with this ...

It all works for audio BUT switching the bt device off kills the ethernet.

Using wifi I can switch the bt off without a network failure - but reconnecting causes the same network failure.

Is there a solution?