All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] strange results in a2dp alsa plugin
Date: Fri, 18 Nov 2005 09:43:21 -0700	[thread overview]
Message-ID: <437E04A9.7030600@xmission.com> (raw)

Marcel

I am getting some really strange stuff happening in my attempt to do an
a2dp alsa plugin. About 90% of the time, the l2cap connection fails...
but then if it does work, I get a segfault inside the sbc library. When
I put a printf inside the library to figure out what was happening, the
segfault went away (but still no audio)! argh.

Would you have a look? Can you make sure rfcomm transport didn't get broken?

I'm basing my effort on your bluez/utils/alsa in the bluez cvs. My diffs
against it are in:

 http://bluetooth-alsa.sourceforge.net/avdtp.patch

I have made it default to a2dp but the rfcomm transport should work if
you have "use_rfcomm" as a true boolean option inside .asoundrc

My .asoundrc:

pcm.headphone {
        type a2dp
        bdaddr "00:0D:3C:30:32:AD"
}

invoked as:

aplay -B 1000000 -D pcm.headphone /usr/share/sounds/linphone/rings/rock.wav

(fwiw, /usr/share/sounds/linphone/rings/rock.wav is reported as signed
16 bit Little Endian, Rate 44100 Hz, Stereo)

Thanks


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

                 reply	other threads:[~2005-11-18 16:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=437E04A9.7030600@xmission.com \
    --to=bmidgley@xmission.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.