From: Simon Vogl <vogl@soft.uni-linz.ac.at>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] sco links
Date: Wed, 03 Mar 2004 15:18:39 +0100 [thread overview]
Message-ID: <4045E93F.4040900@soft.uni-linz.ac.at> (raw)
hi,
can anyone help me with my sco link? in about 50% of cases, the audio dat=
a
has an offset of one byte, resulting in terrible noise. I think I saw a
flag in a packet header somewhere that indicates the number of bytes to s=
kip
until the audio data starts -- I looked through the bt specs several time=
s now
but can't find it again. Anyone has a clue for this?
Simon
--=20
_______________________________________________________________________
Dr. Simon Vogl
Institut f=C3=BCr Pervasive Computing, Johannes Kepler Universit=C3=A4t L=
inz
Altenberger Stra=C3=9Fe 69, A-4040 Linz, Austria
Tel: +43 732 2468-8517, Fax: +43 732 2468-8426
mailto: vogl@soft.uni-linz.ac.at, http://www.soft.uni-linz.ac.at/
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-03-03 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 14:18 Simon Vogl [this message]
2004-03-03 15:11 ` [Bluez-devel] sco links James Courtier-Dutton
2004-03-03 16:17 ` Fred Schättgen
2004-03-03 16:32 ` Simon Vogl
2004-03-03 16:53 ` Fred Schättgen
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=4045E93F.4040900@soft.uni-linz.ac.at \
--to=vogl@soft.uni-linz.ac.at \
--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