public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Choppy sound with a2dp and mplayer
Date: Fri, 23 Nov 2007 11:01:08 -0700	[thread overview]
Message-ID: <d89ddf300711231001q12190488p712e69a42885a3d8@mail.gmail.com> (raw)
In-Reply-To: <9a119b3c0711230758v7fa8a53eub2532227762542bd@mail.gmail.com>

Kristof

It may also be an issue for us right now if mplayer does its video
decoding in the same thread as the  audio processing. Trying another
player and/or the gstreamer plugin in your setup would tell us more.

Brad

On Nov 23, 2007 8:58 AM, Csillag Krist=F3f <csillag.kristof@gmail.com> wrot=
e:
> Hi all!
>
> I am using bluez 3.22.
>
> I have successfully configured the audio system with
> my stereo Bluetooth headset, and a2dp & avrcp work now.
>
> I have an ALSA device named "headset", and when an
> applications (xmms, audacious, etc.) send sound to it,
> it appears on my headset. So good, so far.
>
> However, when I try to use it with mplayer, I get choppy
> output. Playback is smooth for a few seconds, but then
> it breaks up. I can not find any error/warning messages
> in the output of mplayer.
>
> I have made several tests. Here are the results:
>
> 1. Q: mplayer x.avi -ao alsa:device=3Dheadset
>    A: choppy
>
> 2: Q: mplayer x.avi -dumpaudio
>       mplayer stream.dump -ao alsa:device=3Dheadset
>    A: fluent
>
> 3: Q: mplayer x.avi -ao alsa:device=3Dheadset -vc null -vo null
>    A: choppy
>
> So, mplayer _can_ play the sound track of the file via the bt headset,
> without any problems. However, if the video stream is there in the file,
> even if it's not decoded at all, audio collapses.
>
> Because of this, I guess this must be some timing/caching issue.
> Do you agree? If no, what else? If yes, how can I make mplayer cache
> more audio while playing?
>
> (I have already configured hcid to be always master and no rswitch, but
> this did not help.)
>
> Any idea?
>
> Thank you for your help:
>
>     Kristof Csillag
>
> -------------------------------------------------------------------------
> 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-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>



-- =

Brad

-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-11-23 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23 15:58 [Bluez-users] Choppy sound with a2dp and mplayer Csillag Kristóf
2007-11-23 18:01 ` Brad Midgley [this message]

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=d89ddf300711231001q12190488p712e69a42885a3d8@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