Re: [rtcweb] Plan for MTI video codec?

Randell Jesup <randell-ietf@jesup.org> Fri, 24 October 2014 05:11 UTC

Return-Path: <randell-ietf@jesup.org>
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 04AA61A88A9 for <rtcweb@ietfa.amsl.com>; Thu, 23 Oct 2014 22:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_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 8jwyzvLLwFX7 for <rtcweb@ietfa.amsl.com>; Thu, 23 Oct 2014 22:11:22 -0700 (PDT)
Received: from relay.mailchannels.net (aso-006-i443.relay.mailchannels.net [23.91.64.124]) by ietfa.amsl.com (Postfix) with ESMTP id C32C81A8883 for <rtcweb@ietf.org>; Thu, 23 Oct 2014 22:11:21 -0700 (PDT)
X-Sender-Id: wwwh|x-authuser|randell@jesup.org
Received: from r2-chicago.webserversystems.com (ip-10-204-4-183.us-west-2.compute.internal [10.204.4.183]) by relay.mailchannels.net (Postfix) with ESMTPA id 403DF27908D for <rtcweb@ietf.org>; Fri, 24 Oct 2014 05:11:19 +0000 (UTC)
X-Sender-Id: wwwh|x-authuser|randell@jesup.org
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [10.248.11.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.3.2); Fri, 24 Oct 2014 05:11:19 GMT
X-MC-Relay: Neutral
X-MailChannels-SenderId: wwwh|x-authuser|randell@jesup.org
X-MailChannels-Auth-Id: wwwh
X-MC-Loop-Signature: 1414127479528:2378389398
X-MC-Ingress-Time: 1414127479528
Received: from pool-71-175-4-200.phlapa.fios.verizon.net ([71.175.4.200]:62779 helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <randell-ietf@jesup.org>) id 1XhX9i-0005pr-2O for rtcweb@ietf.org; Fri, 24 Oct 2014 00:11:18 -0500
Message-ID: <5449DF6C.9060301@jesup.org>
Date: Fri, 24 Oct 2014 01:11:08 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAGTXFp-HVJDwd86207PNM2QVYO4Z_K4WF-KarnRs1fb7nvy4zA@mail.gmail.com> <CAGTXFp8O-7ACksk3v3f=KjCkcDb4e8G=t-e=EJ1503vt7TkpCQ@mail.gmail.com> <CAGTXFp867AMUZ_fEKxG9uAoR1H1AirVHi3-ayJ=KTQk9L+C7+g@mail.gmail.com> <CA+9kkMAZufR7gUrwkS7Tf5GOfg+ZtsZWGcn-8YLCvnmYnTgfFw@mail.gmail.com> <544035DE.8000606@matthew.at> <CABkgnnUNgWaauS6-nZ5fcExjsMPy4ZGPXaahduzA39=iqh9+fQ@mail.gmail.com> <D5D11F2B-9E32-4932-A601-F1D7FD50C706@gmail.com> <544117FB.6050706@alvestrand.no> <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com> <CA+23+fGWnWd0QEeCmZ=6BmJkPrUVW6cZ0jwmXA+fM88=_+_NWw@mail.gmail.com> <CAOW+2dugTtfLhk0VuJOk7OPEonGBApMjY93EZocH90RbX6X22w@mail.gmail.com> <54442128.6070009@alvestrand.no> <CAOW+2dt8j2VwmpeQ3qaCNOKNgrGz95Sp_ROq=FO9sNm7M2EX2w@mail.gmail.com> <E36D1A4AE0B6AA4091F1728D584A6AD2400622F1@ORSMSX158.amr.corp.intel.com> <CAOJ7v-13gaoqXQOH6KD9fK9C_fKSpoO4HpfNEmVanh0hTRpn9A@mail.gmail.com> <E36D1A4AE0B6AA4091F1728D584A6AD2400699DE@fmsmsx118.amr.corp.intel.com>
In-Reply-To: <E36D1A4AE0B6AA4091F1728D584A6AD2400699DE@fmsmsx118.amr.corp.intel.com>
Content-Type: multipart/alternative; boundary="------------060700060709010505080802"
X-AuthUser: randell@jesup.org
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/XHBhpHzvv-C3aFItx1rP4U2dJG8
Subject: Re: [rtcweb] Plan for MTI video codec?
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: Fri, 24 Oct 2014 05:11:25 -0000

On 10/20/2014 3:09 AM, Cavigioli, Chris wrote:
>
> No, not 2 discussions ... but 2 MTI codecs.
>
> Given:
>
> -Industry is polarized c. 40% VP8 vs. c. 40% H.264
>
> -Unlikely this will change
>
> -Every single mobile device (100%) of the billions out there running a 
> mobile OS (iOS, Android, Windows, BB OS, etc) will already support 
> H.264, AMR-xx since those are MTI for 3GPP and for the OS
>
> Then:
>
> -Why not support both:  VP8, Opus = web; H.264, AMR/AMR-WB = LTE
>
> -Every single mobile device and OS already deals with H.264+AMR 
> licensing for many years.
>
> -Being royalty free, incrementally adding VP8 and Opus shouldn't be a 
> major additional impact
>

I should note that many H.264 HW implementations (or the software 
driving them) in mobile devices are NOT usable for WebRTC (or for video 
communication in general).  The bugs I've seen..... <shudder>.  You can 
certify specific sets of hardware or base chipset code, but until they 
actually get tested *well* in interactive, error-recovery, variable 
bandwidth use you have no clue if they'll work.  (And without such 
testing, generally the answer would be 'no').  Can you say "IDR to 
change bitrate"?  Learn.... OMX has *many* options, most of which are 
not supported on a given implementation, which makes generic use 
'interesting' when you go past the well-traveled (and still rocky) 
decode path.

So if Mozilla distributes Firefox to Android devices, what are we to 
do?  We can't simply assume the encoder/decoder will work for WebRTC at 
this point.  Even getting streaming video decode to leverage HW decoders 
was a massive pain with whitelists, blacklists, evil device-specific 
hacks, etc.  It has gotten better over time - but not great.

I'll note that for WebRTC we currently support OpenH264 on desktop, and 
HW H.264 on specific FxOS devices/chipsets/versions (the default for 
FxOS WebRTC OMX H.264 support is false).  As of today we support only 
VP8 on Android.

And I'll echo Bernard's comments about AMR and licensing/open APIs.

<gripe> When did people forget how to edit out irrelevant repetition of 
old messages?  Ah, yes, when everyone started top-replying.... </gripe>  
Makes searching archives much less fun.  :-/


-- 
Randell Jesup -- rjesup a t mozilla d o t com