[maemo-developers] DSP SBC debugging

[From: Simon Pickering]

> I've moved to Diablo as it uses bluez-utils-3.28 which has the same  
> API as version 2.32 on which I based the DSP code. Patching the DSP  
> SBC encoder into bluez-utils 2.38 I can use sbcenc (good sign) so I  
> tried to play music from mplayer using the a2dp tools produced by  
> johnx to set it up.

Sorry about the typos in the version numbers there. That paragraph should
read as follows:

"I've moved to Diablo as it uses bluez-utils-3.28 which has the same  
API as version 3.32 on which I based the DSP code. Patching the DSP  
SBC encoder into bluez-utils 3.28 I can use sbcenc (good sign) so I  
tried to play music from mplayer using the a2dp tools produced by  
johnx to set it up."

> 
> I get the following error message:
> 

<snip>

> DEBUG: _snd_pcm_bluetooth_open: Bluetooth PCM plugin (Playback)
> DEBUG: audioservice_send: sending BT_GETCAPABILITIES_REQ
> DEBUG: audioservice_recv: trying to receive msg from audio service...
> DEBUG: audioservice_recv: Received BT_GETCAPABILITIES_RSP
> alsa-lib: pcm_bluetooth.c:1589:(bluetooth_init) BT_GETCAPABILITIES  
> failed : Input/output error(5)
> alsa-init: playback open error: Input/output error
> Could not open/initialize audio device -> no sound.
> Audio: no sound
> Video: no video
> 
> 
> Exiting... (End of file)
> (none):/home/user/MyDocs/.sounds#

Good news, I also get this error with the standard un-DSP-enabled
bluez-utils-3.28. So it's (probably) not my fault. It would still be
interesting to know why it happens mind you as I'd like to use a2dp. Does
a2dp work for anyone else using Diablo?

Regards,


Simon