Linux bluetooth development
 help / color / mirror / Atom feed
From: Sjoerd Simons <sjoerd@air.luon.net>
To: Jonathan Paisley <jp-www@dcs.gla.ac.uk>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [ANNOUNCE] ALSA Bluetooth Headset Driver
Date: Fri, 26 Sep 2003 11:59:00 +0200	[thread overview]
Message-ID: <20030926095900.GB1280@air.luon.net> (raw)
In-Reply-To: <Pine.LNX.4.54.999.0309260958140.1399@brava.dcs.gla.ac.uk>

On Fri, Sep 26, 2003 at 09:59:43AM +0100, Jonathan Paisley wrote:
> Thanks for the info. I'm surprised that the latency is so bad. I didn't
> experience similar problems during my testing (although I haven't tested
> it with gnomemeeting yet). Can you try any other software to see what the
> latency is like?
> 
> If you turn on the loopback mode in an ALSA mixer, do you experience
> similar latencies (loopback means the audio received is sent straight back
> to the headset).

Sorry my measuring was flawed.. Apperently the h323 latency was caused
by something else and cat /dev/dspX > /dev/dspY always causes a
latency (pulling brown paper bag over head :( )

  Sjoerd
-- 
Don't have good ideas if you aren't willing to be responsible for them.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2003-09-26  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15  0:21 [Bluez-devel] [ANNOUNCE] ALSA Bluetooth Headset Driver jp-www
2003-09-15 14:30 ` James Courtier-Dutton
2003-09-15 14:51   ` jp-www
2003-09-26  8:51 ` Sjoerd Simons
2003-09-26  8:59   ` Jonathan Paisley
2003-09-26  9:59     ` Sjoerd Simons [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=20030926095900.GB1280@air.luon.net \
    --to=sjoerd@air.luon.net \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jp-www@dcs.gla.ac.uk \
    /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