Re: [rtcweb] resolutions in draft-cbran-rtcweb-codec-01
Ralph Giles <giles@thaumas.net> Fri, 18 November 2011 01:30 UTC
Return-Path: <giles@thaumas.net>
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 4537611E8094 for <rtcweb@ietfa.amsl.com>; Thu, 17 Nov 2011 17:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.927
X-Spam-Level:
X-Spam-Status: No, score=-2.927 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 BXv8vgDQTvG6 for <rtcweb@ietfa.amsl.com>; Thu, 17 Nov 2011 17:30:06 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A8BE911E80BA for <rtcweb@ietf.org>; Thu, 17 Nov 2011 17:30:06 -0800 (PST)
Received: by vcbfl15 with SMTP id fl15so3105044vcb.31 for <rtcweb@ietf.org>; Thu, 17 Nov 2011 17:30:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.24.210 with SMTP id w18mr1228379vdf.21.1321579806121; Thu, 17 Nov 2011 17:30:06 -0800 (PST)
Received: by 10.220.225.5 with HTTP; Thu, 17 Nov 2011 17:30:06 -0800 (PST)
X-Originating-IP: [66.183.19.247]
In-Reply-To: <CAB+e8F5LCyu_9TBkB7DkxjZNbkzGK-u3j+qg9uNui-47NbJDuQ@mail.gmail.com>
References: <4ec47dd1.1610640a.2346.ffffcfdb@mx.google.com> <CAB+e8F5LCyu_9TBkB7DkxjZNbkzGK-u3j+qg9uNui-47NbJDuQ@mail.gmail.com>
Date: Thu, 17 Nov 2011 17:30:06 -0800
Message-ID: <CAEW_Rkv1fo6VAtRvbTS8gwfs1FaHkfd=QXJg8Q+yLK+wg-dQsg@mail.gmail.com>
From: Ralph Giles <giles@thaumas.net>
To: Aron Rosenberg <arosenberg@logitech.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: 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: Fri, 18 Nov 2011 01:30:07 -0000
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. > 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. -r
- [rtcweb] resolutions in draft-cbran-rtcweb-codec-… Roni Even
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Roni Even
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… Cary Bran (Standards Mailer)
- [rtcweb] Video resolution SHOULDs (Re: resolution… Harald Alvestrand
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Stephan Wenger
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Harald Alvestrand
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Roni Even
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… James M. Polk
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… Aron Rosenberg
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… Ralph Giles
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… James M. Polk
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Ralph Giles
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Harald Alvestrand
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Harald Alvestrand
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… Bran, Cary
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… Bran, Cary
- Re: [rtcweb] resolutions in draft-cbran-rtcweb-co… Ralph Giles
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Bran, Cary
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Ralph Giles
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… James M. Polk
- [rtcweb] Interlace (Re: Video resolution SHOULDs … Harald Alvestrand
- Re: [rtcweb] Interlace (Re: Video resolution SHOU… Stephen Botzko
- Re: [rtcweb] Interlace (Re: Video resolution SHOU… Ralph Giles
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Ralph Giles
- Re: [rtcweb] Video resolution SHOULDs (Re: resolu… Stephen Botzko