Re: [codec] AD Evaluation of draft-ietf-codec-oggopus-09

"Ben Campbell" <ben@nostrum.com> Mon, 21 December 2015 21:31 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CE61ACD89; Mon, 21 Dec 2015 13:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 aLmkD6l9uOzu; Mon, 21 Dec 2015 13:31:09 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DB761ACD81; Mon, 21 Dec 2015 13:31:09 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id tBLLV8hA075635 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 21 Dec 2015 15:31:08 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: Ben Campbell <ben@nostrum.com>
To: "Timothy B. Terriberry" <tterribe@xiph.org>
Date: Mon, 21 Dec 2015 15:31:07 -0600
Message-ID: <02FE33D2-476B-4CD5-927C-63BC3D4D4D25@nostrum.com>
In-Reply-To: <566B4B47.9010809@xiph.org>
References: <86ACD2D0-02B6-473E-9E35-B9980166D9A0@nostrum.com> <566B4B47.9010809@xiph.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/codec/ZFe6GApTHQk3AHDdkUnOqifoPb0>
Cc: codec@ietf.org, draft-ietf-codec-oggopus.all@ietf.org
Subject: Re: [codec] AD Evaluation of draft-ietf-codec-oggopus-09
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 21 Dec 2015 21:31:10 -0000

Hi,

Here are my comments to your responses to my editorial comments. As 
before, I removed sections that do not seem to need further comment.

Thanks!

Ben.

On 11 Dec 2015, at 16:16, Timothy B. Terriberry wrote:

[...]

> Editorial
>> =========

[...]

>
>
>> - 5, steps 2 and 3:
>> These steps in combination seem to say “ decode at the highest 
>> available
>> supported rate that the hardware can handle.” If so, the wording 
>> could
>> be simplified.
>
>
> It is a little bit more complicated. There are two rates here: one 
> used for decoding, and one used for playback. The difference between 
> steps 2 and 3 is that in step 3, the hardware's highest available 
> sample rate is not one of the rates supported by Opus decoding. For 
> example, if the highest available sample rate the hardware can handle 
> is 32 kHz, then this is not a "supported rate" (i.e., not supported by 
> Opus decoding), so step 2 does not apply and step 3 does. Step 3 says 
> to decode at the next highest "supported rate", which would be 48 kHz, 
> and then resample to a rate the hardware can handle (in this case 32 
> kHz).
>
> I don't think that's equivalent to your summary of the two steps.

I think I see. The point is that you decode rate still does not match 
the hardware rate, thus the resampling? OTOH, I now find myself confused 
by "next highest supported rate above this". Does "this" refer to the 
"hardware’s highest available sample rate"? So the decode rate is 
always equal to or higher than the hardware playback rate?

[...]
>
>
>> -10, last paragraph:
>>
>> Updates, or extends? If the former, the draft needs an “Updates RFC
>> 5334” field in the initial heading.

I didn't see a response to this one.