IETF Logo Mail Archive

Re: [video-codec] Charter issues from BoF - one or many

Harald Alvestrand <harald@alvestrand.no> Tue, 15 January 2013 14:54 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CE421F876E for <video-codec@ietfa.amsl.com>; Tue, 15 Jan 2013 06:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.466
X-Spam-Level:
X-Spam-Status: No, score=-110.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Za2+8pXDzC5g for <video-codec@ietfa.amsl.com>; Tue, 15 Jan 2013 06:54:51 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 01D9521F8758 for <video-codec@ietf.org>; Tue, 15 Jan 2013 06:54:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id A895639E176 for <video-codec@ietf.org>; Tue, 15 Jan 2013 15:54:45 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhrCPmsIbff6 for <video-codec@ietf.org>; Tue, 15 Jan 2013 15:54:41 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 943F239E056 for <video-codec@ietf.org>; Tue, 15 Jan 2013 15:54:38 +0100 (CET)
Message-ID: <50F56DAD.6080404@alvestrand.no>
Date: Tue, 15 Jan 2013 15:54:37 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: video-codec@ietf.org
References: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu> <C5E08FE080ACFD4DAE31E4BDBF944EB11337D2DF@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB11337D2DF@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [video-codec] Charter issues from BoF - one or many
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 14:54:52 -0000

On 01/15/2013 05:28 AM, Cullen Jennings (fluffy) wrote:
> On Nov 6, 2012, at 9:26 AM, Timothy B. Terriberry <tterribe@xiph.org> wrote:
>
>>> 6. Decide if you are doing one codec or many.
>> I think we should do one codec.
> I don't think that is realistic if we want this implemented in hardware. There is just too many tradeoffs and we end up with more of a family of codecs with negotiated options.
To me, what distinguishes "one codec" from "many codecs" is that with 
one codec, it's possible to write one decoder that can decode all valid 
bitstreams. (that's not the same thing as "one decoder MUST decode all 
bitstreams, even though that's what we aimed for with VP8 - options, 
features, frame sizes and frame rates all conspire to make some 
bitstreams that not all decoders can handle - at least not in real time).

I think we should do one codec.

v2.23.0 | Report a Bug | By Email