Re: [MMUSIC] The 3D drafts
"Pedro Capelastegui" <capelastegui@dit.upm.es> Fri, 10 February 2012 12:33 UTC
Return-Path: <capelastegui@dit.upm.es>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAE2421F8597 for <mmusic@ietfa.amsl.com>; Fri, 10 Feb 2012 04:33:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 yKS4QKDdm77Q for <mmusic@ietfa.amsl.com>; Fri, 10 Feb 2012 04:33:12 -0800 (PST)
Received: from mail.dit.upm.es (mail.dit.upm.es [IPv6:2001:720:1500:42:215:c5ff:fef6:86e4]) by ietfa.amsl.com (Postfix) with ESMTP id EBAD421F856A for <mmusic@ietf.org>; Fri, 10 Feb 2012 04:33:11 -0800 (PST)
Received: from correo.dit.upm.es (correo.dit.upm.es [IPv6:2001:720:1500:42:250:56ff:fea2:7367]) by mail.dit.upm.es (8.14.2/8.14.2) with ESMTP id q1ACWss5031631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 10 Feb 2012 13:32:54 +0100
Received: from delta (delta.dit.upm.es [138.4.7.204]) (authenticated bits=0) by correo.dit.upm.es (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q1ACWf4f018165 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 10 Feb 2012 13:32:43 +0100
From: Pedro Capelastegui <capelastegui@dit.upm.es>
To: 'Bert Greevenbosch' <Bert.Greevenbosch@huawei.com>, 'IETF - MMUSIC' <mmusic@ietf.org>
References: <46A1DF3F04371240B504290A071B4DB623252FF8@szxeml509-mbs.china.huawei.com>
In-Reply-To: <46A1DF3F04371240B504290A071B4DB623252FF8@szxeml509-mbs.china.huawei.com>
Date: Fri, 10 Feb 2012 13:32:55 +0100
Message-ID: <000001cce7f0$1e5e5e10$5b1b1a30$@dit.upm.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CCE7F8.8025D350"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFRyta7TmVXwvE3HuLTDxRY731ujJcsSAKw
Content-Language: es
Subject: Re: [MMUSIC] The 3D drafts
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 12:33:15 -0000
Hi Bert, After taking another look at the 3d format draft, I have found a few additional issues. They are summarized below: 1) Encoding of auxiliary stream: In the video plus auxiliary stream schemes using a single stream (i.e. LD, LP, CD, and CP), no encoding information is provided for the auxiliary stream. 2) Ambiguous negotiation for scenarios with multiple 3D streams: There is no clear way for an offerer to indicate when multiple 3D streams (e.g. to show in multiple displays) are offered, as opposed to a single 3D stream with several possible configurations. 3) Support for H264/MVC streams: The H264/MVC codec is very well suited for 3d video applications. It uses some encoding formats that are not supported by the current draft but could be added without much effort. Ill cover each topic in a separate mail. Here is some discussion on point 1), auxiliary stream encoding. Auxiliary video streams such as depth maps or parallax can be encoded, just like any other video stream. In the Signal 3d format draft, the encoding for these streams can be described and negotiated normally when they are transmitted as separate RTP streams. However, this is no longer true when depth or parallax maps are encapsulated with a regular view as a single RTP stream, as defined in ISO 23002-3. This corresponds to the formats 2DA CD, 2DA CP , 2DA LD and 2DA LP in the draft. It could be assumed that, since no encoding information is provided for these streams, they can use the same encoding used for the video view they are encapsulated with. As an example, consider the following stream: m=video 49170 RTP/AVP 99 a=rtpmap:99 H264/90000 a=3dFormat:2DA CD The above lines describe a video stream representing a central view, with a depth map included in the same RTP stream as auxiliary data. The central view is encoded in H264, but the depth map encoding is undefined. We could solve this by stating in the draft that, when no encoding is specified for an auxiliary stream, it uses the same configuration as the same view. Thus, the depth map in the example would also use H264. I think this works well as a default assumption. However, it does not cover all possible scenarios, as the auxiliary stream CAN use a different format than the base view. In fact, that will likely be the best performing configuration, since depth maps have different properties than regular video streams, and codecs like H264 dont perform particularly well with them. To address this, we would need a way to express the media format for auxiliary streams. At the very least, this would involve including the information normally expressed in a=rtpmap and a=fmtp attributes. One possible way to do this would be to add the values of these attributes (for the auxiliary map) as optional parameters in the a=3dformat attribute. In the previous example, this could look as follows: m=video 49170 RTP/AVP 99 a=rtpmap:99 H264/90000 a=3dFormat:2DA CD aux-map:H264/90000 aux-fmtp:( ) A limitation of this approach is that it just describes a single encoding for the auxiliary map. Ideally, a solution should allow the offerer to suggest multiple configurations from which the answerer can choose one, as with any media stream in the offer/answer model. For this, we could define a new attribute, like a=3daux, and include in it a payload type number, the value of a=rtpmap for the auxiliary stream, and the value of a=fmtp for that stream. It could look as follows: m=video 49170 RTP/AVP 99 100 a=3dFormat:2DA CD a=rtpmap:99 H264/90000 a=3daux: 99 H263/90000 aux-fmtp:( ) a=rtpmap:100 H264/90000 a=3daux: 100 H264/90000 aux-fmtp:( ) In this example, the offerer is providing two possible configurations: - PT 99: Central view encoded in H.264, depth map encoded in H.263 - PT 100: Central view and depth map encoded in H.264 In addition, there may be other SDP fields or attributes that have to be taken into account while signalling these auxiliary streams. Best regards, Pedro From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Bert Greevenbosch Sent: Monday, February 06, 2012 1:32 AM To: IETF - MMUSIC Subject: [MMUSIC] The 3D drafts Hi all, I was wondering, if everybody is happy with the current versions of the 3D drafts, or are there still open issues? I look forward to your comments. Best regards, Bert http://datatracker.ietf.org/doc/draft-ietf-mmusic-parallax-attribute/ http://datatracker.ietf.org/doc/draft-ietf-mmusic-signal-3d-format/ _____ No se encontraron virus en este mensaje. Comprobado por AVG - www.avg.com Versión: 10.0.1424 / Base de datos de virus: 2112/4791 - Fecha de publicación: 02/05/12
- [MMUSIC] The 3D drafts Bert Greevenbosch
- Re: [MMUSIC] The 3D drafts Pedro Capelastegui
- Re: [MMUSIC] The 3D drafts Pedro Capelastegui
- Re: [MMUSIC] The 3D drafts Paul Kyzivat
- Re: [MMUSIC] The 3D drafts Bert Greevenbosch
- Re: [MMUSIC] The 3D drafts Pedro Capelastegui
- Re: [MMUSIC] The 3D drafts Bert Greevenbosch
- Re: [MMUSIC] The 3D drafts capelastegui