Fast audio fixed, but now SinkService hangs upon connection

asked 2014-09-17 09:51:02 -0700

germanviscuso gravatar image


I successfully built the audio service in a Raspberry Pi (with Raspbian) and when sending music from doubleTwist the music was playing too fast. I found this thread:


so I modified my SConscript accordingly and building was successful. But now every time I connect to the SinkService from the doubleTwist app the service dies with this output:

AllJoyn Library version: v0.0.1
AllJoyn Library build info: AllJoyn Library v0.0.1 (Built Wed Sep 10 21:27:33 UTC 2014 by pi - Git: alljoyn branch: '(no branch)' tag: 'v14.06' (+146 changes) commit ref: d611c623c14fb4d404253f39a4641bee518708b9)
AllJoyn Audio version: v0.0.1
AllJoyn Audio build info: v0.0.1 (Built Mon Sep 15 19:33:41 UTC 2014 by pi - Git: alljoyn branch: '(no branch)' tag: 'v14.06' (+146 changes) commit ref: d611c623c14fb4d404253f39a4641bee518708b9)
Accepting join session request from :Xhnl4U85.2 (opts.proximity=ff, opts.traffic=1, opts.transports=4)
SessionJoined with :Xhnl4U85.2 (id=1015029581)
Link timeout has been set to 40s
  24.280 ****** ERROR ALLJOYN_AUDIO lepDisp     src/posix/ALSADevice.cc:134   |  0x0004
  24.283 ****** ERROR ALLJOYN_AUDIO lepDisp     src/posix/ALSADevice.cc:138   |  0x0004
  24.284 ****** ERROR ALLJOYN_AUDIO lepDisp     src/AudioSinkObject.cc:295    |  0x0001

Any clues about the reason? How could adding a reference to asound cause this?


edit retag flag offensive close merge delete


The AllJoyn Audio Service has just been picked back up as a core service please file a jira(jira.allseen alliance.org) for this problem. Does it also reproduce on a Linux desktop vs RPi?

bspencer ( 2014-09-20 14:42:28 -0700 )edit

Ok, I will. I don't have an x86 based Linux to try so I don't know. Properly supporting the audio service on the RPi makes a lot of sense since it's easy to use the RPi to attach to speakers with minimum size. Best, thx

germanviscuso ( 2014-09-22 12:14:25 -0700 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2014-09-23 13:34:40 -0700

updated 2014-09-23 16:05:28 -0700

This line:

24.280 ****** ERROR ALLJOYN_AUDIO lepDisp     src/posix/ALSADevice.cc:134   |  0x0004

indicates that there is an error in src/posix/ALSADevice.cc at line 134. The error number is 0x0004, which is ER_OS_ERROR. Opening up that file and looking in, it is the call to snd_pcm_hw_params_set_buffer_size that is failing, causing the opening and configuration of the audio device to fail.

A debug build would show the specific error returned by ALSA. Alternatively, you can insert some additional logging to verify that the parameters given to that function are what is expected.

edit flag offensive delete publish link more


@germanviscuso does this answer your question?

tmalsbar ( 2014-10-03 11:43:18 -0700 )edit

Hi. Thanks for your help but I already knew this. I traced the error to that function but a debug build is not giving me further info. Digging into why the ALSA device is not being opened goes beyond me. I was hoping that the AllJoyn team would take a look at this and make sure RPi is supported.

germanviscuso ( 2014-10-03 16:27:14 -0700 )edit

@germanviscuso Can you run a debug build and update the question with the errors returned from ALSA? If the debug build is too large, you can add NDEBUG=undefined to your VARIANT=release build and get the full debug logging messages.

tmalsbar ( 2014-10-06 10:47:16 -0700 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2014-09-17 09:51:02 -0700

Seen: 695 times

Last updated: Sep 23 '14