IETF Logo Mail Archive

Re: [rtcweb] RTCWEB needs an Internet Codec

John Leslie <john@jlc.net> Thu, 06 September 2012 16:51 UTC

Return-Path: <john@jlc.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B85E521F8744 for <rtcweb@ietfa.amsl.com>; Thu, 6 Sep 2012 09:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-VcGuG3Yy08 for <rtcweb@ietfa.amsl.com>; Thu, 6 Sep 2012 09:51:43 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 77DC321F8722 for <rtcweb@ietf.org>; Thu, 6 Sep 2012 09:51:43 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id ED1F633C26; Thu, 6 Sep 2012 12:51:42 -0400 (EDT)
Date: Thu, 06 Sep 2012 12:51:42 -0400
From: John Leslie <john@jlc.net>
To: Ron <ron@debian.org>
Message-ID: <20120906165142.GF79075@verdi>
References: <p06240608cc66e4862829@[99.111.97.136]> <00a701cd89fc$e681e9d0$b385bd70$@us> <p06240601cc6aa58a7171@[99.111.97.136]> <504571BC.9020103@librevideo.org> <5045CA2B.2070406@gmail.com> <5045F343.9030107@alvestrand.no> <50460FF1.30708@freedesktop.org> <20120904210055.GN23434@audi.shelbyville.oz> <p06240609cc6d8e39fb6c@[99.111.97.136]> <20120906020039.GP23434@audi.shelbyville.oz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20120906020039.GP23434@audi.shelbyville.oz>
User-Agent: Mutt/1.4.1i
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWEB needs an Internet Codec
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Sep 2012 16:51:53 -0000

Ron <ron@debian.org> wrote:
> 
> The libopus reference implementation source can be freely download
> by anyone, at any time, and redistributed at will by any party with
> no other "burden" placed upon them to do anything else.

   See:

www.opus-codec.org/downloads/

(the libopus.sourceforge.net is quite unrelated).

http://downloads.xiph.org/releases/opus/opus-1.0.0-rc.tar.gz

is the release-candidate. Note:
] 
] The codec is still under development, in the final stages preparing
] the first production release.

   I find this very encouraging, but not quite enough to justify MTI
today.

   Note also:

https://developer.mozilla.org/en-US/docs/Media_formats_supported_by_the_audio_and_video_elements#Ogg_Opus

which shows some level of support already in Mozilla (but not Chrome,
Explorer, Opera, or Safari)

   Here is a case where "Google's position is" could actually be
helpful -- were they to announce Opus support in Chrome...

--
John Leslie <john@jlc.net>

v2.23.0 | Report a Bug | By Email