From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Successes and failures with btsco/bluez respectively
Date: Wed, 14 Feb 2007 01:30:43 -0700 [thread overview]
Message-ID: <45D2C8B3.8050102@xmission.com> (raw)
In-Reply-To: <9da483cb0702130106s3c76315g2c57fd4f1017ad23@mail.gmail.com>
Mike
fwiw, it may be that something somewhere has regressed. I can't get
totally smooth audio through btsco-0.5 or cvs plugz (a2dpd or a2dpd2).
It doesn't have to be in our driver, especially since my previously
working btsco-0.5 plugin doesn't work right. It could be in the kernel
or bluez or my config. I haven't held things constant with a control
configuration unfortunately :(
My best result is in using my spider set, plugz from cvs, a2dpd plugin,
totem and a .asoundrc with
pcm.!default {
type a2dpd
}
but I'm still getting occasional pauses in the stream. totem using
a2dpd2 resulted in audio playing too fast with gaps of silence.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-14 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 1:56 [Bluez-devel] Successes and failures with btsco/bluez respectively Mike Hodson
2007-02-13 4:03 ` Brad Midgley
2007-02-13 8:24 ` Mitja Pufic
2007-02-13 9:06 ` Mike Hodson
2007-02-14 8:30 ` Brad Midgley [this message]
2007-03-06 4:34 ` Mike Hodson
2007-02-13 8:09 ` [Bluez-devel] RE : " Frederic Dalleau
2007-02-13 10:27 ` Mike Hodson
2007-02-13 13:15 ` Frédéric DALLEAU
2007-02-13 22:25 ` Mike Hodson
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=45D2C8B3.8050102@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.