IETF Logo Mail Archive

Re: [rtcweb] Platforms that support H264 (was: Congratuiations on the Cisco announcement - but we still prefer VP8)

Eric Rescorla <ekr@rtfm.com> Sat, 02 November 2013 22:17 UTC

Return-Path: <ekr@rtfm.com>
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 53B6611E8253 for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 15:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 GEaHOtgXtBSu for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 15:17:04 -0700 (PDT)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id C1BBF11E824E for <rtcweb@ietf.org>; Sat, 2 Nov 2013 15:17:03 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id f4so2402638wiw.10 for <rtcweb@ietf.org>; Sat, 02 Nov 2013 15:17:02 -0700 (PDT)
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=qIkqOJhSt4KlIg6vbbm3eBJycQiJIQmRe4oPOBhJ3bY=; b=Ik6varFVfklCe/j0Oy+2qmM5CJYE0fSRxnVFl4ojQrWYa4eWXnLulkNRwBNkJDRRfj T8SruaQqYAN9ZHukxEESxgl8bohSJKhCjwHKAb8WJPX1sXYTN+Gqw4+BPfdGFx1hymH7 9muCFiEnIhgh3CY7CslXt1bITLaByv4Vv+Vk0GcELB2r7TEOoQgSfGt2GSp7uHG/NCDO vbgxThXbWK2/hE4KdSvfXikx/O21DNuHPjHqUCT+eEe0HP7oKTbC7BxnHp0aquSToKeZ YfvGzFFrAQ9UlxSFyJ5y81h9KvXNuakPE5H3Ez4KjLLrCinGWO52x5v9MBxDHtiWH3+s QjjQ==
X-Gm-Message-State: ALoCoQkHLcRcLDWs+j0oaJZi+BtgfvRejiC5zhdGSUz3MEsimseUVcSTd/pqHMwTzkyq049Y4qJ2
X-Received: by 10.180.24.137 with SMTP id u9mr6807575wif.5.1383430622809; Sat, 02 Nov 2013 15:17:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.152.137 with HTTP; Sat, 2 Nov 2013 15:16:22 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:a427:d50c:2c74:28c4]
In-Reply-To: <CAPvvaaK-bKt-zDEq2qibRrm51VbRGAV=95JShKFdCpJszw5Tww@mail.gmail.com>
References: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com> <52740478.6030109@nostrum.com> <CAOJ7v-2+_4QZwc8vEtdwVDWSP-d-z+ggB0u+VM6WnA=f-k4-XA@mail.gmail.com> <BLU404-EAS261C783EDA4575EE1A7E53593F40@phx.gbl> <52750E3C.9060206@bbs.darktech.org> <CABkgnnVR9=oWVzRaRuD701tvZCtp+SO1n6c65hJELLVfB8QcOA@mail.gmail.com> <C21C6AC2-29F8-4DFF-BB48-5E3D625DCD65@phonefromhere.com> <CAPvvaaK-bKt-zDEq2qibRrm51VbRGAV=95JShKFdCpJszw5Tww@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 02 Nov 2013 15:16:22 -0700
Message-ID: <CABcZeBMG1ApkN7u_uyO_9H9se22ixLhaYc6pZsncvc6d+k8rEQ@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: multipart/alternative; boundary="f46d04447f67d828f004ea390ac1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Platforms that support H264 (was: Congratuiations on the Cisco announcement - but we still prefer VP8)
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: Sat, 02 Nov 2013 22:17:08 -0000

If only there was some piece of software that you could download
that provided H.264 encoders for those platforms.

-Ekr



On Sat, Nov 2, 2013 at 10:14 AM, Emil Ivov <emcho@jitsi.org> wrote:

> Same questions for OS X and Windows actually. Last time we checked (which
> was also some time ago) there was no way to get the OS to *encode* H.264
> for you.
>
> --sent from my mobile
> On 2 Nov 2013 17:57, "tim panton" <tim@phonefromhere.com> wrote:
>
>>
>> On 2 Nov 2013, at 15:02, Martin Thomson <martin.thomson@gmail.com> wrote:
>>
>> > On 2 November 2013 07:37, cowwoc <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.
>>
>> Martin, can I ask you to talk with your Skype engineering team and check
>> up on
>> the exact way that works on iOS. Last time I looked, it seemed you
>> couldn’t use the
>> Apple supplied (hardware accelerated) h264 library for realtime
>> encode/decode and
>> it wasn’t at all clear to me that the hardware encoder licence covered
>> any soft implementation of h264 we
>> added.
>>
>> I’d like to caveat that:
>>  1) it was a while ago. 2) I’m not a lawyer. 3) it was a thought
>> experiment.
>> So it would be interesting to get a current view from the trenches.
>>
>> T.
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.23.0 | Report a Bug | By Email