From: Frederic Dalleau <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dp, sco and kernel version
Date: Thu, 02 Aug 2007 15:04:14 +0200 [thread overview]
Message-ID: <1186059854.3574.2.camel@ubuntu.mpl.access-company.com> (raw)
In-Reply-To: <46B1573A.3080003@gmail.com>
Can you please send me your kernel config file?
And if anybody have (or not) the same problem, they can too saying what
they have.
Cheers,
Frederic
On Thu, 2007-08-02 at 01:02 -0300, Manuel Naranjo wrote:
> I want to help, just tell me what you need and I get it to all for you.
> I work for the company that builds the USB dongle [1], and I'm using the
> hifi headset we sell. So I have plenty access to almost every hardware
> detail. So please let me know what you need, logs, etc, and I get it.
> Thanks,
> Manuel
>
> [1] http://www.aircable.net/host-xr.html
>
> > Your bandwidth seems to be higher than expected,
> > thought we dont know how much is your bitpool.
> >
> > Here using 53 the bandwidth used is about 350 kbps,
> > using a value higher than 64 it starts to give me some
> > buffer problems.
> >
> > On 8/1/07, Manuel Naranjo <naranjo.manuel@gmail.com> wrote:
> >
> >>> Make sure your stream is 44.1khz stereo
> >>>
> >>>
> >> That's the first thing I had checked
> >>
> >>> Do you use the plug plugin?
> >>>
> >>> pcm.!default {
> >>> type plug
> >>> slave.pcm "a2dpdplug"
> >>> }
> >>>
> >>> pcm.a2dpdplug {
> >>> type a2dpd
> >>> }
> >>>
> >>> Also this variant may help :
> >>>
> >>> pcm.a2dpdplug {
> >>> type a2dpd
> >>> rateconstraint 44100
> >>> }
> >>>
> >>>
> >> Sorry but that didn't worked.
> >>
> >> Here's what mplayer is telling me:
> >> alsa-play: trying to reset soundcard
> >> alsa-play: write error: Broken pipe0) 2.3%
> >> alsa-play: trying to reset soundcard
> >> A: 80.9 (01:20.9) of 189.0 (03:09.0) 2.3%
> >>
> >> And this is what a2dpd says about it:
> >> A2DPD[09:42:05.562]: display_daemon_state: [16,16|16,16] playing
> >> connected clients=1 freq=1032 cnt=24833 (1032/0) poll=1048
> >> latency=1185972125 sec.
> >> A2DPD[09:42:05.616]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:05.767]: a2dp_transfer_raw: Bandwith: 79488 (621 kbps) 32,
> >> latency=1185972125 sec.
> >> A2DPD[09:42:05.826]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:05.030]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:06.234]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:06.479]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:06.631]: display_daemon_state: [16,16|16,16] playing
> >> connected clients=1 freq=1144 cnt=25977 (1144/0) poll=1162
> >> latency=1185972126 sec.
> >> A2DPD[09:42:06.672]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:06.836]: a2dp_transfer_raw: Bandwith: 85077 (664 kbps) 32,
> >> latency=1185972126 sec.
> >> A2DPD[09:42:06.895]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:06.103]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:07.307]: a2dp_transfer_raw: send (retry).
> >> A2DPD[09:42:07.508]: a2dp_transfer_raw: send (retry).
> >>
> >> Any ideas what can be wrong?
> >>
> >> Thanks,
> >> Manuel
> >>
> >> -------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems? Stop.
> >> Now Search log events and configuration files using AJAX and a browser.
> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> _______________________________________________
> >> Bluez-devel mailing list
> >> Bluez-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/bluez-devel
> >>
> >>
> >
> >
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-02 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 23:24 [Bluez-devel] a2dp, sco and kernel version Manuel Naranjo
2007-07-31 0:26 ` Brad Midgley
2007-07-31 0:34 ` Manuel Naranjo
2007-07-31 8:31 ` Frederic Dalleau
2007-07-31 8:52 ` Frederic Dalleau
2007-07-31 11:19 ` Manuel Naranjo
2007-07-31 16:29 ` Luiz Augusto von Dentz
2007-07-31 18:22 ` Manuel Naranjo
2007-08-01 7:38 ` Frederic Dalleau
2007-08-01 12:44 ` Manuel Naranjo
2007-08-02 3:22 ` Luiz Augusto von Dentz
2007-08-02 4:02 ` Manuel Naranjo
2007-08-02 13:04 ` Frederic Dalleau [this message]
2007-08-02 13:05 ` Frederic Dalleau
2007-08-02 15:18 ` Manuel Naranjo
2007-08-02 18:53 ` [Bluez-devel] a2dp, sco and kernel version [Possible Solution] Manuel Naranjo
2007-08-02 19:12 ` Brad Midgley
2007-08-02 19:24 ` Manuel Naranjo
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=1186059854.3574.2.camel@ubuntu.mpl.access-company.com \
--to=frederic.dalleau@access-company.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox