From: Fredrik Wendt <fredrik@wendt.se>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] gstreamer + bluetooth-alsa (a2dp) = stalls after song switch
Date: Thu, 20 Sep 2007 11:59:23 +0200 [thread overview]
Message-ID: <1190282363.24745.46.camel@desktop3> (raw)
Hi all.
My first post, I'm not capable of C programming but believe I can assist
with basic error searching (gdb is out of my scope, strace and ltrace I
understand, more or less :)
My issue is that if I use rhythmbox or banshee that both use gstreamer
they get stalled/hang after changing to a new song. It basically just
hangs and a2dpd says something about client error. (Other clients
continue to work.)
xmms only behaves like this when I manually restart playing the same
track again (hit the play button while the song is playing). To me, it
looks like the way gstreamer connects to alsa needs attention? Or is it
alsasink that has issues talking to the a2dpd device?
How should I proceed to find out where things go wrong?
What do you want me to report if noone has reported this (sounds
unlikely to me, but google didn't give me much help otoh) to be of help
to you?
* Ubunty Feisty (latest/up-to-date kernel and packages from Ubuntu
distribution)
* a2dpd built from CVS
(http://bluetooth-alsa.sourceforge.net/build.html), got it at 2007-09-11
06:15 CET.
Thanks in advance,
Fredrik Wendt
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-09-20 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 9:59 Fredrik Wendt [this message]
2007-09-20 10:42 ` [Bluez-devel] gstreamer + bluetooth-alsa (a2dp) = stalls after song switch Fabien Chevalier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1190282363.24745.46.camel@desktop3 \
--to=fredrik@wendt.se \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox