All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: bluetooth plugin "jittery" and "sticky"
Date: Thu, 27 Apr 2006 08:20:03 -0600	[thread overview]
Message-ID: <4450D313.7020501@xmission.com> (raw)
In-Reply-To: <s5hpsj3xplt.wl%tiwai@suse.de>

Takashi

>> We finally got around to working on the stereo (a2dp) bluetooth alsa
>> plugin. It's mostly working in the cvs version of the project "btsco" at
>> http://bluetooth-alsa.sf.net.
> 
> Hm, it's a bit too ambiguous to say something.  Could you elaborate
> what do you mean xmms jitters?  The time springs or just the audio
> matters?

The time display in xmms goes back and forth between two values. It
counts like 02,01,02,01,02,03,02,03,02,03 so it does actually go
forward. The audio sounds fine. It's just the display doesn't look right
and xmms locks up at the end of a song.

I think it's in our .transfer callback, a2dp_transfer. I had two
versions contributed. The other version, a2dp_transfer2, randomly locks
up xmms but when it works, the time display looks ok and xmms can switch
between songs without problems.

We have to enforce timing of packets sent to the headset in the
.transfer cb. Is there a plugin out there I can look at that also has to
deal with timing? We're not sure how to best enforce it... see
http://bluetooth-alsa.sf.net/pcm_a2dp.c

Brad


-------------------------------------------------------
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 easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-04-27 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26  9:09 bluetooth plugin "jittery" and "sticky" Brad Midgley
2006-04-27 10:46 ` Takashi Iwai
2006-04-27 14:20   ` 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=4450D313.7020501@xmission.com \
    --to=bmidgley@xmission.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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.