From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2play
Date: Tue, 16 Jan 2007 21:36:35 -0700 [thread overview]
Message-ID: <45ADA7D3.3030404@xmission.com> (raw)
In-Reply-To: <D8CE9CFA707C894180BAC8CDD154F8460AE3EC0D@msiexch01.marvell.com>
Quinton
> I am trying out the a2play in head version btsco package, basically it
> works great except that seems it=92s very sensitive to system event, if I
> leave the my notebook there playing without doing anything, I can listen
> hours music without any problem, however, if I try to something on the
> same pc, like edit some file or browse the internet, audio will be
> stopped, message like
> =
> Read 3321c0 1080 times / sec
fwiw, I found a2play timing is very sensitive to the use of X using the
closed-source nvidia driver. They must be doing something wacky like
masking interrupts for long periods.
the "real" driver using a2dpd is better at timing. I just applied Steve
Romanow's suggestion for the d-bus compile problem in case that helps.
Brad
-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-17 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 2:18 [Bluez-devel] a2play Quinton Yuan
2007-01-17 4:36 ` Brad Midgley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 20:12 Shawn Rutledge
2005-03-24 18:38 Shawn Rutledge
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=45ADA7D3.3030404@xmission.com \
--to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.