Re: [rtcweb] Reference implementation of software codecs

Maik Merten <maikmerten@googlemail.com> Mon, 18 November 2013 19:12 UTC

Return-Path: <maikmerten@googlemail.com>
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 847871ADF6B for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 11:12:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_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 SJd-xnoDwX1e for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 11:12:32 -0800 (PST)
Received: from mail-bk0-x232.google.com (mail-bk0-x232.google.com [IPv6:2a00:1450:4008:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1B45B1AC4A3 for <rtcweb@ietf.org>; Mon, 18 Nov 2013 11:12:31 -0800 (PST)
Received: by mail-bk0-f50.google.com with SMTP id e11so1318748bkh.23 for <rtcweb@ietf.org>; Mon, 18 Nov 2013 11:12:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=P4gyLRV3cSh3UPT3ByOrpMar7QNEotRfblRn6NB3Kz8=; b=y7TU5hMB/d+MN83WsXkI6EcPB+pRH2mKYFQQivgrh9pLPbNUuCCCOaGsEGWTC5gNB8 gyW3WgFnebQV2OHDAwXuqEKmOD1XtDXl2pCbzeb+0MDWG6DIuoZ5hBv3dpv4GmVuryIC kXayKUwlvXnzCJl6e8IQQwTVQ8prmQvd9WUM1ld7t1I1J4lYxkc5PABdtvUC5e+G86qq VkLmzQ5Rz1yhDHHw4En//cqiP3wew3snfr4vrxGN+sKSpqAT7V1NrS4DnTAl1hU+4eS0 KCHY+R1e4mKeRiLDoIfA06KVPEPMugB+mNPsdkLsYl1FqBxU+OVaeRF7giOOa54uTGXq Akmw==
X-Received: by 10.205.22.71 with SMTP id qv7mr13455593bkb.20.1384801945819; Mon, 18 Nov 2013 11:12:25 -0800 (PST)
Received: from [192.168.2.101] (dslb-188-101-189-061.pools.arcor-ip.net. [188.101.189.61]) by mx.google.com with ESMTPSA id pk7sm17709321bkb.2.2013.11.18.11.12.23 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 18 Nov 2013 11:12:24 -0800 (PST)
Message-ID: <528A6696.8060404@googlemail.com>
Date: Mon, 18 Nov 2013 20:12:22 +0100
From: Maik Merten <maikmerten@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <5283DFDC.4010906@ericsson.com> <528A0BD8.1070409@ericsson.com> <528A4408.50105@bbs.darktech.org> <528A4B07.7010104@googlemail.com> <528A5087.1020304@bbs.darktech.org>
In-Reply-To: <528A5087.1020304@bbs.darktech.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Reference implementation of software codecs
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: Mon, 18 Nov 2013 19:12:34 -0000

FWIW, I think I found a BSD-stlye H.261 implementation, which appears to 
include contributions from Cisco:

http://mpeg4ip.cvs.sourceforge.net/viewvc/mpeg4ip/mpeg4ip/server/mp4live/h261/encoder-h261.cpp?revision=1.12&view=markup

A BSD-style implementation thus wouldn't have to start from scratch, 
albeit some extensive massaging may be needed to plug it into a WebRTC 
context.


Maik


Am 18.11.2013 18:38, schrieb cowwoc:
>
> Okay, so I believe this is an open issue. I've changed the topic to
> avoid hijacking the old thread.
>
> Gili
>
> On 18/11/2013 12:14 PM, Maik Merten wrote:
>> Regarding H.261, apart from ffmpeg there's also a maintained
>> implementation over at
>>
>> http://sourceforge.net/p/opalvoip/code/29319/tree/opal/trunk/plugins/video/H.261-vic/h261vic.cxx
>>
>>
>> which is covered by the Mozilla Public License 1.0
>> (http://www.mozilla.org/MPL/1.0/).
>>
>> "3.7. Larger Works.
>> You may create a Larger Work by combining Covered Code with other code
>> not governed by the terms of this License and distribute the Larger
>> Work as a single product. In such a case, You must make sure the
>> requirements of this License are fulfilled for the Covered Code."
>>
>> The H.261 *en*coder of that project looks rather primitive (only
>> generating I-frames), but the *de*coder should be feature-complete.
>> Perhaps that's something to build upon.
>>
>> I would also suspect that complete and battle-tested implementations
>> gather dust at some vendors of telco stuff, but nobody seems to have
>> open sourced one.
>>
>>
>>
>> Maik
>>
>>
>> Am 18.11.2013 17:44, schrieb cowwoc:
>>>
>>> Looks good! I'd like to get a clarification which affects multiple
>>> options, but #10 most of all.
>>>
>>> Does the WG commit to providing reference implementations that supports
>>> VP8, H.264, H.261 with a commercially-friendly license? I am talking
>>> strictly about the software license, not the codec IPR. Meaning, libx264
>>> requires a GPL license and ffmpeg requires either a LGPL or GPL license.
>>> I would argue that libx264 is a non-starter for commercial use on any
>>> platform (due to GPL) and ffmpeg is not usable under iOS (since LGPL +
>>> static linking is equivalent to GPL). It is my understanding that the
>>> current WebRTC reference implementation is published under the BSD
>>> license. I am asking for the final reference implementation (supporting
>>> these codecs) to be published under the same license.
>>>
>>> I'm not saying that anyone has to ship a reference implementation
>>> supporting all 3 codecs, but rather that the WG should publish a
>>> reference implementation demonstrating how it can be done and proving
>>> interoperability actually works as expected.
>>>
>>> Thanks,
>>> Gili
>>>
>>> On 18/11/2013 7:45 AM, Magnus Westerlund wrote:
>>>> WG,
>>>>
>>>> The current list of proposed alternative are the following one:
>>>>
>>>>   The following alternatives has been proposed:
>>>>
>>>>    1. All entities MUST support H.264
>>>>    2. All entities MUST support VP8
>>>>    3. All entities MUST support both H.264 and VP8
>>>>    4. Browsers MUST support both H.264 and VP8, other entities MUST
>>>>       support at least one of H.264 and VP8
>>>>    5. All entities MUST support at least one of H.264 and VP8
>>>>    6. All entities MUST support H.261
>>>>    7. There is no MTI video codec
>>>>    8. 5+6, i.e. All entities MUST support H.261 and all entities MUST
>>>>       support at least one of H.264 and VP8
>>>>    9. All entities MUST support Theora.
>>>>   10. All entities SHOULD support both H.264 and VP8. All entities MUST
>>>>       at least implement one of those. Entities that do not support
>>>> both
>>>>       H.264 and VP8 MUST implement H.261.
>>>>
>>>> The deadline to propose additional alternatives are: 27th of November
>>>> 2013
>>>>
>>>> Cheers
>>>>
>>>> Magnus
>>>>
>>>> On 2013-11-13 21:23, Gonzalo Camarillo wrote:
>>>>> Folks,
>>>>>
>>>>> I hope everybody had a safe trip back home after Vancouver.
>>>>>
>>>>> As you all know, we need to make progress regarding the selection
>>>>> of the
>>>>> MTI video codec. The following are some of the alternatives we have on
>>>>> the table:
>>>>>
>>>>>   1. All entities MUST support H.264
>>>>>   2. All entities MUST support VP8
>>>>>   3. All entities MUST support both H.264 and VP8
>>>>>   4. Browsers MUST support both H.264 and VP8
>>>>>   5. All entities MUST support either H.264 or VP8
>>>>>   6. All entities MUST support H.261
>>>>>   7. There is no MTI video codec
>>>>>
>>>>> If you want the group to consider additional alternatives to the ones
>>>>> above, please let the group know within the following *two weeks*. At
>>>>> that point, the chairs will be listing all the received
>>>>> alternatives and
>>>>> proposing a process to select one among them.
>>>>>
>>>>> Please, send your proposals in an email to the list. You do not
>>>>> need to
>>>>> write a draft; just send the text you would like to see in the final
>>>>> document regarding video codecs.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Gonzalo
>>>>> Responsible AD for this WG
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>> _______________________________________________
>> 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