Re: [rtcweb] H.264 CBP (was: Video codec selection - way forward)

[Eric Rescorla <[e-mail]>]

It was CBP.

I think there's some debate about the relative performance characteristics,
with
general agreement that H.264 CBP and VP8 are in the same neighborhood
and also general agreement that performance is not the important factor.

-Ekr



On Fri, Nov 22, 2013 at 11:30 PM, cowwoc <[e-mail]> wrote:

>
> +1
>
> In the original VP8 vs H.264 discussion, what H.264 profile was under
> discussion?
>
> If it was not H.264 CBP, do we need to revisit the comparison? Do the two
> profiles use the same bandwidth, CPU and produce the same quality?
>
> Thanks,
> Gili
>
> On 21/11/2013 2:27 PM, Maik Merten wrote:
>
>> Btw, should any occurrence of "H.264" in the current list of options be
>> substituted with "H.264 CBP"? Perhaps it is best to be very clear on the
>> profile which should be implemented.
>>
>> Thanks,
>>
>> Maik
>>
>> Am 21.11.2013 20:20, schrieb David Singer:
>>
>>> Chairs
>>>
>>> can we add this as an option to the formal list, so we get formal
>>> feedback on its acceptability, please?
>>>
>>> “Like option ??, pick at least two of {VP8, H.264 CBP, H.263}”
>>>
>>>
>>> I think this may be the best (maybe only) way to tease out how much risk
>>> people perceive.
>>>
>>> Many thanks
>>>
>>> On Nov 21, 2013, at 9:22 , Maik Merten <[e-mail]>
>>> wrote:
>>>
>>>  Cleary H.263 is preferable from an engineering standpoint (as is, e.g.,
>>>> MPEG-1 Part 2): better performance, more deployments. The central question
>>>> is, however, if those can actually be implemented without some sort of
>>>> licensing.
>>>>
>>>> If they can: Aweseome! However, this may not be determinable without a
>>>> review by people who are knowledgeable in the field of IPR, i.e., "actual
>>>> lawyers". I understand that H.263 is not yet old enough to automatically be
>>>> considered "safe" (and neither is MPEG-1 Part 2, although it is closer).
>>>>
>>>> Best regards,
>>>>
>>>> Maik
>>>>
>>>> Am 20.11.2013 20:42, schrieb David Singer:
>>>>
>>>>> I think we should think hard about H.263 instead of H.261 as the third
>>>>> fallback.  Why?
>>>>>
>>>>> http://www.itu.int/rec/T-REC-H.263/
>>>>>
>>>>>
>>>>>
>>>>> H.263 was first published in March 1996, so it's 17 years old.  The
>>>>> restrictions (e.g. on picture size) are no WORSE than H.261.  Yes, more
>>>>> recent amendments deal with this (and a plethora of other issues), so we’d
>>>>> need to settle on which of those are mandatory (the usual profiling
>>>>> discussion).
>>>>>
>>>>> There are 34 records in the patent database against H.261, mostly from
>>>>> 1989 but one as recent as 2005 (though that is a re-file).  That's 2.2
>>>>> (reciprocity), as was one other I checked.
>>>>>
>>>>> Rather surprisingly, there are only 31 against H.263!  The most recent
>>>>> is 2011, and is also option 2.  Most are 1997-2001.
>>>>>
>>>>>
>>>>> On this quick glance, H.263 appears no worse than H.261. IANAL (as I
>>>>> am sure you have all noticed).
>>>>>
>>>>>
>>>>> H.263 is much more widely supported and mandated.  It has been
>>>>> mandated in the 3GPP specs for years (for lots of services, including
>>>>> videoconf), and is effectively the fallback codec today in the industry, as
>>>>> I understand.  It was ubiquitous in video telephony for years, and I
>>>>> suspect many of those systems still ship it.
>>>>>
>>>>> So, would “MUST implement at least two of (H.264, VP8, H.263)” work?
>>>>>
>>>>> (I am asking the question, not even answering on behalf of my company,
>>>>> yet.  Let’s get the issues on the table.)
>>>>>
>>>>>
>>>>> David Singer
>>>>> Multimedia and Software Standards, Apple Inc.
>>>>>
>>>>> _______________________________________________
>>>>> rtcweb mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>>>
>>>>>
>>>> _______________________________________________
>>>> rtcweb mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>>
>>>
>>> David Singer
>>> Multimedia and Software Standards, Apple Inc.
>>>
>>> _______________________________________________
>>> rtcweb mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>
>>>
>> _______________________________________________
>> rtcweb mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>