Re: [codec] Format for the codec specification

Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> Fri, 24 September 2010 23:21 UTC

Return-Path: <jean-marc.valin@usherbrooke.ca>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9582A3A69A8 for <codec@core3.amsl.com>; Fri, 24 Sep 2010 16:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.923
X-Spam-Level:
X-Spam-Status: No, score=-1.923 tagged_above=-999 required=5 tests=[AWL=0.676, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1B8usT4i-VwL for <codec@core3.amsl.com>; Fri, 24 Sep 2010 16:21:12 -0700 (PDT)
Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by core3.amsl.com (Postfix) with ESMTP id 5C40A3A6814 for <codec@ietf.org>; Fri, 24 Sep 2010 16:21:12 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Received: from [192.168.1.14] ([70.81.109.112]) by VL-MR-MRZ20.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0L99003P2Y84BCF0@VL-MR-MRZ20.ip.videotron.ca> for codec@ietf.org; Fri, 24 Sep 2010 19:21:40 -0400 (EDT)
Message-id: <4C9D3288.1000608@usherbrooke.ca>
Date: Fri, 24 Sep 2010 19:21:44 -0400
From: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100915 Thunderbird/3.0.8
To: Roni Even <ron.even.tlv@gmail.com>
References: <C8C24B29.24A5A%stewe@stewe.org> <4C9D0C24.5080302@usherbrooke.ca> <4c9d216e.1021cc0a.658d.51bf@mx.google.com>
In-reply-to: <4c9d216e.1021cc0a.658d.51bf@mx.google.com>
Cc: codec@ietf.org
Subject: Re: [codec] Format for the codec specification
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 23:21:13 -0000

Hi Roni,

Thanks for the correction on the case of G.719. Despite that, my point 
still stands: there *are* codecs for which the decoder is standardized 
without a bit-exact definition. As long as we define the amount of 
deviation permitted, then there is no problem.

Oh, and I do agree that the C code should take precedence over the 
mathematical description.

Cheers,

	Jean-Marc

On 10-09-24 06:06 PM, Roni Even wrote:
> 6.5 Description of the codec
> The description of the coding algorithm of this Recommendation is made in
> terms of bit-exact
> fixed-point mathematical operations. The ANSI-C code indicated in clause 10,
> which constitutes an
> integral part of this Recommendation, reflects this bit-exact, fixed-point
> descriptive approach. The
> mathematical descriptions of the encoder and decoder can be implemented in
> other fashions,
> possibly leading to a codec implementation which does not comply with this
> Recommendation.
> Therefore, the algorithm description of the ANSI-C code of clause 10 shall
> take precedence over the
> mathematical descriptions whenever discrepancies are found. A set of test
> signals, which can be
> used together with the ANSI-C code in order to verify bit-exactness, is
> available as an electronic
> attachment to this Recommendation.
>
>
> Roni Even
>
>
>