IETF Logo Mail Archive

Re: [rtcweb] FEC for audio?

Peter Thatcher <pthatcher@google.com> Mon, 19 May 2014 19:15 UTC

Return-Path: <pthatcher@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5E01A0104 for <rtcweb@ietfa.amsl.com>; Mon, 19 May 2014 12:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.029
X-Spam-Level:
X-Spam-Status: No, score=-2.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Va9VVPoiKOyO for <rtcweb@ietfa.amsl.com>; Mon, 19 May 2014 12:15:12 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1281A0156 for <rtcweb@ietf.org>; Mon, 19 May 2014 12:15:12 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id md12so6273744pbc.40 for <rtcweb@ietf.org>; Mon, 19 May 2014 12:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6PPMtETHU3y7wRfPUo4rmERM/+jpHmpaXSUVksEax+M=; b=eilRqT2inZZv9DfbzdiYIRTiJjJiapwfLeGpmfPnzi368AkLwB8Yn48ecY5/KJhOVm XJ3YkRc9UlTc8+TwXupM2zHbxNbnS0n3rAyuzPfPhhxIpTEbuFtqezIT+FCPiXcTNiZ5 x4LKSEvEXPRYBpsOCAnF03iMvxbFZD/uKuSrTlFU/NdFbM95mcM2wGkcpuQcCV+/rBQF 1OJVEUC4YfU20A4+phOETZzqQf9CD9I/IKPy1BBf20RCdpj59wfwx2eWIbwjV/cMpgwF t9bwPrQI8QN7qVZA0MGbGuKDeKH8suAkSTeT2zxBHgv7Xs7S3qDMxZYcoARrAAf+WskW RClg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=6PPMtETHU3y7wRfPUo4rmERM/+jpHmpaXSUVksEax+M=; b=btu0OLWbcYuNiKnxW6eqCMtASx+FICXsnXxatx3WBLa3gnC+vZzBC3nZI2tAhn4V2L htT4tuZSzX1mgsNNxtsZTrhbUnfHMV0F4JJP7okj0xA4WliSNQHAzf4CJRtgG6pFQwpZ aFMOIGZnVUMj1uheZpw2jH6hdjNwmJauyTqb78dbj0rqcthvmQTze8kBHAJL/CSqUdYw JLL+EORqWuNce6FzEV4P8KJrJRN9QvvcLD/CUWolMe/lEq7E34kbRkdxKj9w2GWOTjeB Uud/3UxpYgct56EYj0Ajqi9iR0yf/GvmGm/2WXAVfz7NeLcsHAjRndVxP5xu5Ol089Sw JIeA==
X-Gm-Message-State: ALoCoQnQERgBp+N9BS5d37pnj7IhfUI32jBM1y9PosLNMyWNt3NHOpoR2hdUiTNK/rJT0XhbGH1Y
X-Received: by 10.68.173.65 with SMTP id bi1mr45145546pbc.130.1400526912530; Mon, 19 May 2014 12:15:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.163.226 with HTTP; Mon, 19 May 2014 12:14:32 -0700 (PDT)
In-Reply-To: <CAOJ7v-1qEpkWShmw1SQKh4_BLKycF=egu42TS9o9+Smtof36pg@mail.gmail.com>
References: <CAOJ7v-1qEpkWShmw1SQKh4_BLKycF=egu42TS9o9+Smtof36pg@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 19 May 2014 12:14:32 -0700
Message-ID: <CAJrXDUESUa-xm9y22OAVKAw5z=WnkY4-X6XFZOoXwvkMoDnaoQ@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: multipart/alternative; boundary="047d7b3a99d81ec94d04f9c5950a"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/YttSodpuk-SgIrNpoqtsvDhqSqI
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] FEC for audio?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 19:15:14 -0000

If we're already designing and implementing FEC for video, it seems like a
small step to also support it for audio.  I find the use case for
high-bitrate audio use compelling.  As an app, if I want to spend lots of
bits for really high-quality audio, I'd like the option to make sure FEC is
still enabled; I'm perhaps willing to spend the bits on it.

Is there a good reason not to support FEC for audio, if that's what the
application wants?


On Mon, May 19, 2014 at 9:44 AM, Justin Uberti <juberti@google.com> wrote:

> Should we specify generic FEC for audio as well as video? Opus has
> built-in FEC, but it only works for the SILK portion of the payload,
> meaning that in high bitrate situations, it won't do much for you. I don't
> know if it has benefits over generic FEC.
>
> Some application providers have mentioned that FEC helps with audio
> intelligibility on cellular networks, so I think this is important to
> support.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.23.0 | Report a Bug | By Email