Re: [rtcweb] x264 vs OpenH264 (Was: On the topic of MTI video codecs)
Emil Ivov <emcho@jitsi.org> Fri, 01 November 2013 16:52 UTC
Return-Path: <emcho@sip-communicator.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 9920F11E821C for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 09:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level:
X-Spam-Status: No, score=-2.741 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 fKhRB+lPjMys for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 09:52:07 -0700 (PDT)
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) by ietfa.amsl.com (Postfix) with ESMTP id 45E1211E8117 for <rtcweb@ietf.org>; Fri, 1 Nov 2013 09:52:07 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb4so4488584pbc.36 for <rtcweb@ietf.org>; Fri, 01 Nov 2013 09:52:06 -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=xLxrOqrU+vWhsutO2hJKLm2QDGqT/Kar6XAcy8tzqIU=; b=mwwdlXOBMgU5pooybinygXrmXdu4EJockNA/Jwc+soOOasr6eXK4gjwg7AXwimm4ni HRgrRrBi+GKEr076PylD5e53yrsVv43mg7G4RzV/trdFt8QRX9YSQP7366rldtje6ezG egpGEki8tPEMO1UyYfIQegzX4mZRXHXqI4amqYPfhI9KIpMnrg+xxg7TyFFdJFCjfo1n /eh+tTEMXIvEIFhIQp9Hqndfts+pXFIlEXSYB1fSImWcuAikjuLPs1Qo9oSncAL4oUmS la43xSL8sKKkDd1BJG9JYC1a5mdO83hnIM8W5jNsYLrt0nIjvz+7dM005VExAWudUM0j ARkQ==
X-Gm-Message-State: ALoCoQleKYzY4rKhyp66a9htWURcj8EDnH2OaHtDOuiDPOca6rKCZLLIVYo1RpjsqvxiOx4Ru3F4
X-Received: by 10.66.169.172 with SMTP id af12mr4217131pac.23.1383324726617; Fri, 01 Nov 2013 09:52:06 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [2607:f8b0:400e:c02::233]) by mx.google.com with ESMTPSA id lm2sm14154274pab.2.2013.11.01.09.52.06 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Nov 2013 09:52:06 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id y10so4058593pdj.24 for <rtcweb@ietf.org>; Fri, 01 Nov 2013 09:52:06 -0700 (PDT)
X-Received: by 10.66.118.204 with SMTP id ko12mr2446284pab.184.1383324726080; Fri, 01 Nov 2013 09:52:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.191.163 with HTTP; Fri, 1 Nov 2013 09:51:44 -0700 (PDT)
In-Reply-To: <14789922-BEC6-460B-ABB0-092D63237BBF@edvina.net>
References: <CAPvvaaLwacOgQq5O8t0bMCJJfKTHbJM9RnawgXLJpKiADtsi2Q@mail.gmail.com> <14789922-BEC6-460B-ABB0-092D63237BBF@edvina.net>
From: Emil Ivov <emcho@jitsi.org>
Date: Fri, 01 Nov 2013 17:51:44 +0100
Message-ID: <CAPvvaaJ5rTgt1MTNYUEBhhd-t4HNeRkjS4uuTegmJftTLGYcCA@mail.gmail.com>
To: "Olle E. Johansson" <oej@edvina.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] x264 vs OpenH264 (Was: On the topic of MTI video codecs)
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: Fri, 01 Nov 2013 16:52:11 -0000
Hey Olle, On Fri, Nov 1, 2013 at 5:36 PM, Olle E. Johansson <oej@edvina.net> wrote: > > On 01 Nov 2013, at 17:19, Emil Ivov <emcho@jitsi.org> wrote: > >> On Fri, Nov 1, 2013 at 4:56 PM, Cullen Jennings <fluffy@iii.ca> wrote: >>> >>> On Nov 1, 2013, at 9:14 AM, Emil Ivov <emcho@jitsi.org> wrote: >>> >>>> On Fri, Nov 1, 2013 at 3:27 PM, DRAGE, Keith (Keith) >>>> <keith.drage@alcatel-lucent.com> wrote: >>>>> >>>>> That ownership means they are also take responsibility for any of the liabilities arising >>>>> from defective code they so distribute. I see no reason why Cisco would want to do >>>>> that under anything but a controlled evironment, which would have its own set of >>>>> non-trivial costs. >>>> >>>> They could have the same by distributing x264 binaries that they have >>>> compiled by themselves. >>>> >>>> One of the things in the Cisco grand, that sound a bit incoherent to >>>> me is their declared will on building a healthy open source community >>>> around their implementation. Specifically, what baffles me is that >>>> there is already a very well oiled implementation that does a lot more >>>> than just baseline. That implementation already has a vibrant >>>> community, significant popularity and, again, it sounds like it would >>>> be considerably superior to what Cisco are planning on rolling out in >>>> OpenH264. >>>> >>>> In addition to wondering at the pure waste of resources (with a casual >>>> reference to NIH), potential contributors could legitimately ask "why >>>> would we contribute to your project when you made the exact opposite >>>> choice when faced with the decision?". >>>> >>>> Emil >>> >>> We considered just using x264 (I like x264 myself) that but Mozilla told us it would not work for them because it is GPL. >> >> It would be nice for Mozilla to comment then. They wouldn't have been >> required to statically link against it or even distribute it. It is >> already possible to use GPL plug-ins with Firefox, so why is x264 an >> insurmountable problem? >> > Emil. If you take x264 and link into Jitsi you will have to pay license fees to MPEG-LA. > > If you let the Jitsi users download the codec binary from Cisco and use the plugin API which will > be defined by the OpenH264 community you don't have to pay any license fees. Cisco will. My question was: why not have users download x264 binaries from Cisco. Basically, nothing changes from the current Cisco suggestion, except for where the source code comes from. Emil -- https://jitsi.org
- [rtcweb] x264 vs OpenH264 (Was: On the topic of M… Emil Ivov
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … cowwoc
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Max Jonas Werner
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Olle E. Johansson
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Emil Ivov
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Richard Barnes
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Daniel-Constantin Mierla
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Martin Thomson
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Emil Ivov
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Richard Barnes
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Emil Ivov
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Olle E. Johansson
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Lorenzo Miniero
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Lorenzo Miniero
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Richard Barnes
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Daniel-Constantin Mierla
- Re: [rtcweb] x264 vs OpenH264 (Was: On the topic … Martin Thomson