From: Robert Huitl <bluez-devel@huitl.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] a2dpd and mplayer - any chance to get it working? [resent]
Date: Mon, 15 Jan 2007 20:10:54 +0100 [thread overview]
Message-ID: <200701152010.54996.bluez-devel@huitl.de> (raw)
Hi,
I was wondering whether it is possible to make the a2dp alsa plugin supply
correct audio timing to applications like MPlayer. Right now, MPlayer does
not work with a2dpd because it relies on the audio driver to report accurate
audio timing information (or something like that).
If a2dpd could measure the delay introduced on the wireless transport, it
might be possible to supply timing information to media players. The player
could then sync the video to the audio data, so there should be no delay at
all between audio and video playback.
Is there something I am missing?
What changes to the alsa plugin would be necessary?
Even if the delay can't be determined exactly, we could just fake that
information MPlayer is missing, so that a2dpd at least worked together with
MPlayer (with a small delay, maybe)?
Regards,
Robert
-------------------------------------------------------------------------
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 reply other threads:[~2007-01-15 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 19:10 Robert Huitl [this message]
2007-01-15 19:50 ` [Bluez-devel] a2dpd and mplayer - any chance to get it working? [resent] Brad Midgley
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=200701152010.54996.bluez-devel@huitl.de \
--to=bluez-devel@huitl.de \
--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