From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Modify scotest?
Date: Fri, 16 Dec 2005 09:50:51 +0100 [thread overview]
Message-ID: <1134723051.30889.3.camel@localhost> (raw)
In-Reply-To: <43A27DFD.9070007@thomson.net>
Hi Arnaud,
> Using SCO for quality measurement is a good idea if your bluetouth
> device supports trasnparent audio, and if you configure them to use this
> mode. If not, you can still try a configuration like ulaw on air, ulaw
> on HCI (no conversion in theory)
no it is not a good idea. The chip will insert bits/bytes/frames as it
thinks it needs to. The transparent audio is not guaranteed. Read the
posts from the CSR guys for any details.
> In this case, write a tool like scotest that always send FF.FF.FF...FF
> frames (or anything you want) (write the same amount of data that you
> receive). Then juste count zeros bits to detect BER, and 00.00.00...00
> frames for PER.
Get a CSR development kit and get their BCCMD specification and use
their internals to get the BER values.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-16 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 17:10 [Bluez-devel] Modify scotest? Wolfgang Krug
2005-12-15 19:42 ` Marcel Holtmann
2005-12-16 8:42 ` Arnaud Mouiche
2005-12-16 8:50 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-17 7:47 Wolfgang Krug
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=1134723051.30889.3.camel@localhost \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).