Re: [codec] #16: Multicast?

"Raymond (Juin-Hwey) Chen" <rchen@broadcom.com> Mon, 26 April 2010 21:02 UTC

Return-Path: <rchen@broadcom.com>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 354673A6839 for <codec@core3.amsl.com>; Mon, 26 Apr 2010 14:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.169
X-Spam-Level:
X-Spam-Status: No, score=-0.169 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-WbMfRfh2fm for <codec@core3.amsl.com>; Mon, 26 Apr 2010 14:02:50 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id 018CF3A6B6E for <codec@ietf.org>; Mon, 26 Apr 2010 14:02:47 -0700 (PDT)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 26 Apr 2010 14:02:20 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.31]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Mon, 26 Apr 2010 14:02:20 -0700
From: "Raymond (Juin-Hwey) Chen" <rchen@broadcom.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Mon, 26 Apr 2010 14:02:18 -0700
Thread-Topic: [codec] #16: Multicast?
Thread-Index: AcrkTi/xlw0UOCUaT+WSfKLd+Krg0wBIzQdg
Message-ID: <CB68DF4CFBEF4942881AD37AE1A7E8C74B90136749@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <062.7439ee5d5fd36480e73548f37cb10207@tools.ietf.org> <3E1D8AD1-B28F-41C5-81C6-478A15432224@csperkins.org> <D6C2F445-BE4A-4571-A56D-8712C16887F1@americafree.tv> <C0347188-A2A1-4681-9F1E-0D2ECC4BDB3B@csperkins.org> <u2x6e9223711004210733g823b4777y404b02330c49dec1@mail.gmail.com> <000001cae173$dba012f0$92e038d0$@de> <r2q6e9223711004211010gfdee1a70q972e8239fef10435@mail.gmail.com> <001101cae177$e8aa6780$b9ff3680$@de> <t2t6e9223711004211119i6b107798pa01fc4b1d33debf1@mail.gmail.com> <002d01cae188$a330b2c0$e9921840$@de> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A017@IRVEXCHCCR01.corp.ad.broadcom.com> <20100423011559.20246ayxdicd9vzz@mail.skype.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A291@IRVEXCHCCR01.corp.ad.broadcom.com> <alpine.DEB.1.10.1004251000340.6768@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1004251000340.6768@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67CB20D620S103926853-01-01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] #16: Multicast?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2010 21:02:51 -0000

Hi Mikael,

Thanks for sharing your experience using a BT headset for Skype calls.  I think part of the quality degradation that you experienced was due to the reduction of the audio bandwidth to narrowband (8 kHz sampling, 3.4 kHz bandwidth), and another part of the degradation was due to the audible coding noise of the CVSD codec, a 40-year-old coding technology first proposed in 1970.  

If a high-quality, low-complexity, wider bandwidth IETF codec mode can be implemented in Skype and the Bluetooth headset to avoid the CVSD transcoding (together with wideband upgrade of the transducers and audio path in the BT headset, of course), then not only will you get much better speech quality in your Skype calls than what you have experienced, but also you will get a lower latency.  This is because transcoding between the Skype codec and CVSD not only accumulates the coding distortion of the two codecs, but also accumulates the coding delays.  Although CVSD is a sample-by-sample codec, BT headsets still transmit the CVSD bit-stream in 3.75 ms or 7.5 ms packets, and they can potentially add a one-way delay up to 20 ~ 25 ms through the Bluetooth headset (the exact delay depends on the implementation).

While we were discussing whether a 5 ms packet size can even be considered, for many years Bluetooth headsets have been using an even smaller 3.75 ms packet size.

Best Regards,

Raymond

-----Original Message-----
From: Mikael Abrahamsson [mailto:swmike@swm.pp.se] 
Sent: Sunday, April 25, 2010 1:06 AM
To: Raymond (Juin-Hwey) Chen
Cc: Koen Vos; codec@ietf.org
Subject: Re: [codec] #16: Multicast?

On Sat, 24 Apr 2010, Raymond (Juin-Hwey) Chen wrote:

> (7) Already a lot of people are used to using Bluetooth headsets to make 
> phone calls today.  If they have a choice, many of these people will 
> also want to use Bluetooth headsets to make Internet phone calls, not 
> only through computers, but also through smart phones connected to WiFi 
> or cellular networks.  As more and more states and countries pass laws 
> to ban the use of cell phones that are not in hands-free mode while 
> driving, the number of Bluetooth headset users will only increase with 
> time, and many of them will want to make Internet-based phone calls.

I purchased a BT headset with the anticipation of using it with my 
computer to make Skype calls. I tried it, but the sound quality when doing 
bidirectional audio (whatever that mode is called) is not good enough, it 
worsens the "skype IP" call quality. I agree that the use case is 
interesting, but as long as BT sound quality is what it is, it's really 
only the "low end" type  sound quality we're talking about.

But yes, I make skype IP calls with my Nokia N900 using BT sometimes, so 
the use case example is definitely valid.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se