Re: [rtcweb] resolutions in draft-cbran-rtcweb-codec-01

"Bran, Cary" <cary.bran.standards@gmail.com> Tue, 29 November 2011 17:57 UTC

Return-Path: <cary.bran.standards@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C7121F8B9B for <rtcweb@ietfa.amsl.com>; Tue, 29 Nov 2011 09:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zyh3rR4u8Zg8 for <rtcweb@ietfa.amsl.com>; Tue, 29 Nov 2011 09:57:17 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8012921F8B64 for <rtcweb@ietf.org>; Tue, 29 Nov 2011 09:57:17 -0800 (PST)
Received: by qadb10 with SMTP id b10so1702974qad.10 for <rtcweb@ietf.org>; Tue, 29 Nov 2011 09:57:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=z5fg2Lbwr3QvLEOU7WRpgkt/YLUJU8YW1hWaWs6NfPY=; b=ucK3U46HOEfxt59l47IKR2tQCsLD0mbmFwuXcr4gWT48D/nuCqFFY5Wr0kmh/tiBYl cpChZLEqwWLA4rHKgzNKlxxfGW0KUjWKPzzpvhSJ3wofjzMfx2LhqFgrAUjFZiyPDQML TnzWXroaJTVXGJ+2GXlX08AYDqiFwvdUjoxdU=
Received: by 10.224.185.199 with SMTP id cp7mr22134306qab.68.1322589436614; Tue, 29 Nov 2011 09:57:16 -0800 (PST)
Received: from [10.0.1.16] (c-98-247-103-106.hsd1.wa.comcast.net. [98.247.103.106]) by mx.google.com with ESMTPS id z1sm38372807qao.1.2011.11.29.09.57.09 (version=SSLv3 cipher=OTHER); Tue, 29 Nov 2011 09:57:13 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.13.0.110805
Date: Tue, 29 Nov 2011 09:57:29 -0800
From: "Bran, Cary" <cary.bran.standards@gmail.com>
To: Ralph Giles <giles@thaumas.net>, Aron Rosenberg <arosenberg@logitech.com>
Message-ID: <CAFA5A8A.57A9%cary.bran.standards@gmail.com>
Thread-Topic: [rtcweb] resolutions in draft-cbran-rtcweb-codec-01
In-Reply-To: <CAEW_Rkv1fo6VAtRvbTS8gwfs1FaHkfd=QXJg8Q+yLK+wg-dQsg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] resolutions in draft-cbran-rtcweb-codec-01
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 29 Nov 2011 17:57:18 -0000

Hi Ralph,


On 11/17/11 5:30 PM, "Ralph Giles" <giles@thaumas.net> wrote:

>On 17 November 2011 17:10, Aron Rosenberg <arosenberg@logitech.com> wrote:
>
>> I would suggest dropping 720x480 as it is neither 16:9 or 4:3 ratio,
>>but a
>> non-standard 3:2 ratio.
>
>720x480 is a standard SD broadcast/DVD-Video resolution. With
>non-square pixels and overscan, it can represent either 4:3 or 16:9.
>Both proposed baseline codecs in this draft support non-square pixels,
>since a lot of video is in this format.
>
>I don't know how useful it is to have this as a SHOULD, but I would
>ask why the corresponding PAL resolution (576 lines) isn't also
>included if this one is considered useful.

I have added this to the 02 version as a SHOULD.
>
>> From a camera perspective 1024x768 and 800x60[0] are
>> not well supported in video modes.
>
>That's true, but these are common VGA screen resolutions. I think it's
>useful to have them for presentations and screencasting. 1024x768 has
>been a standard format for conference presentations for more than a
>decade, and 800x600 is a useful fallback.
>
>As to how this SHOULD should be read, I think the point here is that
>while some devices have fixed formats due to hardware constraints,
>others (like a desktop browser) are quite flexible, so it's helpful to
>have a list of common resolutions implementers can choose to offer in
>the absence of other constraints, and to test against.

Stole a bit of this verbiage and integrated it into the 02 version.

>
> -r
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb