Re: [rtcweb] Platforms that support H264

cowwoc <cowwoc@bbs.darktech.org> Tue, 05 November 2013 06:10 UTC

Return-Path: <cowwoc@bbs.darktech.org>
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 103A611E8176 for <rtcweb@ietfa.amsl.com>; Mon, 4 Nov 2013 22:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.628
X-Spam-Level:
X-Spam-Status: No, score=-4.628 tagged_above=-999 required=5 tests=[AWL=-1.030, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-O51vqrArse for <rtcweb@ietfa.amsl.com>; Mon, 4 Nov 2013 22:10:43 -0800 (PST)
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by ietfa.amsl.com (Postfix) with ESMTP id A0B8B11E8182 for <rtcweb@ietf.org>; Mon, 4 Nov 2013 22:10:39 -0800 (PST)
Received: by mail-ie0-f178.google.com with SMTP id x13so14246575ief.37 for <rtcweb@ietf.org>; Mon, 04 Nov 2013 22:10:38 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=131J8A9PZX7FoGomsKTx0yT67yVx7VBTHhqbjEkGuBQ=; b=ZJazThAsy64B/gO5uIvJpZRhq/DBWscSnpaJnM7CZ181mr6LTBDqARKp2krD2BRpzy e31VnGonIKjrP2yRR2akfO9E+39m691UHjKUGwWBBx8XBUCt6wbS8V7uPZQBZgQKHRqd fpLfTOPQK4LNPwJv92vPqhaqoxiegEkLkHxN67fM9R6jHKCuLwrcNTeSBp60x01/03h3 ae0Dr4mM61neWU/YY71MMg9rH/+WeTUvg+LkTDzAwEpPiV1QRm9x+q5RBJ2GCmH0MmS0 7EYd9niPAH3kUqhVHh3yEOgiiVByr+V3VbCLlbq8j6H/uGLXOdEJqFOmak/Ext/gF71H dnsw==
X-Gm-Message-State: ALoCoQlVFkt4ccHOBMurpwUKd7OC12D5vkN9NsUGMHnFqp89gucrBRTowENlp9PFPqSQ1xqPqjJq
X-Received: by 10.50.45.100 with SMTP id l4mr14563766igm.8.1383631838768; Mon, 04 Nov 2013 22:10:38 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id p5sm6982603igj.10.2013.11.04.22.10.37 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Nov 2013 22:10:37 -0800 (PST)
Message-ID: <52788BDC.90109@bbs.darktech.org>
Date: Tue, 05 Nov 2013 01:10:36 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CE9DC5C8.1B814%mzanaty@cisco.com>
In-Reply-To: <CE9DC5C8.1B814%mzanaty@cisco.com>
Content-Type: multipart/alternative; boundary="------------040205090505000207000304"
Subject: Re: [rtcweb] Platforms that support H264
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: Tue, 05 Nov 2013 06:10:48 -0000

     I'm not sure if you're being sarcastic or not...

     In any case, I had a question regarding BlackBerry 10. Are you 
implying that every BlackBerry 10 phone includes an API for real-time 
encoding/decoding of H.264 video streams? If so, which API is it? I took 
a quick look but couldn't find it.

Thanksm
Gili

On 04/11/2013 9:52 PM, Mo Zanaty (mzanaty) wrote:
> I think you meant *every* phone, tablet, laptop, desktop, set-top, 
> camera...
>
>
> On 11/2/13, 7:41 PM, Kaiduan Xie <kaiduanx@gmail.com 
> <mailto:kaiduanx@gmail.com>> wrote:
>
> Every BlackBerry 10 phone has H.264 hardware encoder/decoder.
>
> /Kaiduan
>
>
> On Sat, Nov 2, 2013 at 6:18 PM, Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>> wrote:
>
>
>
>
>     On Sat, Nov 2, 2013 at 1:01 PM, Gili <cowwoc@bbs.darktech.org
>     <mailto:cowwoc@bbs.darktech.org>> wrote:
>
>         Martin,
>
>             I fully understand why Firefox would be happy but as
>         someone who plan to integrate WebRTC into a non-browser
>         application, especially on iOS, Cisco's solution simply does
>         not work. I appreciate their contribution, but again, it
>         simply doesn't help my use-case.
>
>
>     I haven't seen  you explain how your use case is different from
>     that of
>     a browser. Could you please do so?
>
>     -Ekr
>
>         Gili
>
>
>         On 11/2/2013 11:02 AM, Martin Thomson wrote:
>
>             On 2 November 2013 07:37, cowwoc <cowwoc@bbs.darktech.org
>             <mailto:cowwoc@bbs.darktech.org>> wrote:
>
>                      I can't think of a single platform that supports
>                 real-time H.264
>                 encoding/decoding natively today.
>
>             That's a very strange way to put the question.
>
>             Let me put another spin on it, and please excuse the
>             example...
>
>             Skype runs on more platforms than you might think.  Those
>             platforms
>             can all support H.264 to the extent that Skype requires.
>
>             Cisco's generous offer opens almost the same capability to
>             anyone,
>             with the caveat that some platforms currently remain
>             closed.  Of
>             course, you could let your ideals get in the way of
>             progress.  Me, I'm
>             a pragmatist.  This gift represents a great opportunity
>             for people who
>             actually care about the practical outcomes.
>
>             There's been a lot of mouth-gazing of gift horses on this
>             list of
>             late.  I sure hope that this isn't representative of the real
>             sentiment of the community.  I'd like to think that people
>             are better
>             than that.
>
>             (BTW, I understand and respect Harald's position.  From
>             where he sits,
>             I'm sure that his conclusion makes perfect sense.)
>
>
>         _______________________________________________
>         rtcweb mailing list
>         rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>         https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>     _______________________________________________
>     rtcweb mailing list
>     rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb