public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frédéric DALLEAU" <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dpd and mplayer - any chance to get it working?
Date: Fri, 02 Feb 2007 17:55:01 +0100	[thread overview]
Message-ID: <45C36CE5.90205@access-company.com> (raw)
In-Reply-To: <45BD6370.4050005@xmission.com>

Hi,

I've been trying some things and just uploaded an *a2dpd2* plugin.
Tested the plugin with =

aplay,xmms,amarok,vlc,mocp,kaffeine,mplayer,beep-media-player.
This gave good sound on all except mplayer :( but at least the movie =

speed is now correct. This may be worth a try on another computer.
Not had time to try any gst based player.

reports appreciated.

Fr=E9d=E9ric
PS: Note the type plug/slave.pcm trick is not well supported by =

vlc,mocp,bmp. I used alsa-libs 1.0.13 but this should not be required.

> Frederic is the one who is writing this. He has had some trouble getting
> xmms to play without the sleep() call and it may be related to the pcm
> status.
>   =

>>>  I was wondering about alsa plugins :
>>> xmms relies on alsa timing to play, so in the plugin, there is a sleep()
>>> call, this will wait a little bit until it is time to retievre new data.
>>> But it seems some players (like mplayer) wants to do their own timing o=
r at
>>> least don't want to sleep. They need to use that time to do some decodi=
ng
>>> instead. If you sleep too long, the decoding will be defered and the so=
und
>>> or movie will be broken.
>>>
>>> Is there a rule to distinguish? Or some magic value to sleep?
-- =

Frederic

Without the wind, the grass does not move.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-02-02 16:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15  2:26 [Bluez-devel] a2dpd and mplayer - any chance to get it working? Robert Huitl
2007-01-17  7:03 ` [Bluez-devel] RE : " Frederic Dalleau
2007-01-17 18:05   ` [Bluez-devel] " Robert Huitl
2007-01-17 18:35   ` [Bluez-devel] RE : " Fabien Chevalier
2007-01-17 19:15     ` Brad Midgley
2007-01-18 17:50       ` Fabien Chevalier
2007-01-28 19:30   ` [Bluez-devel] " Robert Huitl
2007-01-29  3:01     ` Brad Midgley
2007-02-02 16:55       ` Frédéric DALLEAU [this message]
2007-02-06 19:25         ` Michael Frey
2007-03-27 10:39         ` Tim Chick
2007-03-27 13:33           ` Frederic Dalleau
2007-03-27 14:01             ` Tim Chick
2007-04-05  8:59               ` [Bluez-devel] Question about poll() - was " Frederic Dalleau
2007-04-06  5:17                 ` Brad Midgley
2007-04-06 16:05               ` [Bluez-devel] " Frederic Dalleau

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=45C36CE5.90205@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