From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Alsa headset with MPlayer
Date: Mon, 15 Oct 2007 20:56:02 -0600 [thread overview]
Message-ID: <d89ddf300710151956p2f67e6edracc1dc88cca7be70@mail.gmail.com> (raw)
In-Reply-To: <47140347.40409@gmail.com>
Hi
The patch is still valid, but you should be trying the audio service
in the current bluez-utils, especially if you have bugs to report,
suggestions, etc. http://wiki.bluez.org/wiki/HOWTO/AudioDevices
Brad
On 10/15/07, Advhertz <advhertz@gmail.com> wrote:
> Hi All,
> I've got workin' fine the BT headset with the last kernel 2.6.23 patched
> with sco-flowcontrol-v4.3.diff included in the plugz bluetooth alsa cvs
> repository and aplay/arecord, xmms, Rhythmbox and Skype too works fine.
> The problem now is mplayer.
>
> As I give the command " mplayer -ao alsa:device=headset " it stucks as here:
>
> Starting playback...
> A: 0.0 (00.0) of 226.0 (03:46.0) ??,?% 98%
>
> and it doesn't start to play.
>
> The headset string is the one I used in my $HOME/.asoundrc file as the
> following:
>
> pcm.headset {
> type plug
> slave {
> pcm "headsetBT"
> rate 8000
> format S16_LE
> channels 1
> }
> }
>
> pcm.headsetBT {
> @args [BDADDR TIMEOUT]
>
> # The Bluetooth device address for target headset, used for
> Audio Gateway (PC) initiated connections
> # Please note that this value is ignored when the connection is
> Headset initiated
> @args.BDADDR {
> type string
> default "XX:XX:XX:XX:XX:XX"
> }
>
> # This value represents how long we will try to reach the
> headset, until we give up.
> # Value is in milliseconds
> @args.TIMEOUT {
> type integer
> default 6000
> }
>
> type sco
> bdaddr $BDADDR
> timeout $TIMEOUT
> }
>
> ctl.headset {
> type sco
> }
>
> Do anyone know anything about it ? MPlayer could work with the bt alsa
> headset, right? Maybe I wrong something?
>
> Let me know please.
>
> Thanks.
>
> Advhertz.
>
> -------------------------------------------------------------------------
> 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-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-10-16 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 0:18 [Bluez-users] Alsa headset with MPlayer Advhertz
2007-10-16 2:56 ` Brad Midgley [this message]
2007-10-16 5:05 ` Advhertz
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=d89ddf300710151956p2f67e6edracc1dc88cca7be70@mail.gmail.com \
--to=bmidgley@gmail.com \
--cc=bluez-users@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