[MMUSIC] 答复: About measurement unit for ParallaxInfo

huiyu <huiyu@huawei.com> Thu, 21 April 2011 02:34 UTC

Return-Path: <huiyu@huawei.com>
X-Original-To: mmusic@ietfc.amsl.com
Delivered-To: mmusic@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 36C08E07EF for <mmusic@ietfc.amsl.com>; Wed, 20 Apr 2011 19:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.044
X-Spam-Level:
X-Spam-Status: No, score=-0.044 tagged_above=-999 required=5 tests=[AWL=-0.741, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYlrAYKw1E7U for <mmusic@ietfc.amsl.com>; Wed, 20 Apr 2011 19:34:06 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfc.amsl.com (Postfix) with ESMTP id D8318E06DB for <mmusic@ietf.org>; Wed, 20 Apr 2011 19:34:04 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJZ00897DORCO@szxga03-in.huawei.com> for mmusic@ietf.org; Thu, 21 Apr 2011 10:31:40 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJZ008EFDORX1@szxga03-in.huawei.com> for mmusic@ietf.org; Thu, 21 Apr 2011 10:31:39 +0800 (CST)
Received: from h45037b ([10.138.73.44]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LJZ002MSDOQBW@szxml06-in.huawei.com> for mmusic@ietf.org; Thu, 21 Apr 2011 10:31:39 +0800 (CST)
Date: Thu, 21 Apr 2011 10:31:30 +0800
From: huiyu <huiyu@huawei.com>
In-reply-to: <BANLkTik8p7K4FfTewNLBi9W5SpWr2x+ZRw@mail.gmail.com>
To: 'Stephen Botzko' <stephen.botzko@gmail.com>
Message-id: <000301cbffcc$390f8200$ab2e8600$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_NWINz4tJ0Vp+aM7VfPhv3w)"
Content-language: zh-cn
Thread-index: Acv/RxbFlRsN55rwQ0iyLhAiAnSWZwAffDDg
References: <46A1DF3F04371240B504290A071B4DB6012C561F@SZXEML501-MBS.china.huawei.com> <BANLkTimETj13R-hNquZqa94d9UdSOJDx9A@mail.gmail.com> <001101cbff1e$2914ec90$7b3ec5b0$@com> <BANLkTik8p7K4FfTewNLBi9W5SpWr2x+ZRw@mail.gmail.com>
Cc: mmusic@ietf.org
Subject: [MMUSIC] 答复: About measurement unit for ParallaxInfo
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: Thu, 21 Apr 2011 02:34:08 -0000

Hi Stephen,

 

Thanks for your advice.

 

I think the two methods are all reasonable.

But in fact whether selecting 11520 pixels as the reference screen width or
signalling  the reference screen width  in SDP  "ParallaxInfo" attribute
line, 

the resulting [PARALLAX ] value  may be a fraction and need to  be
appropriately rounded to the nearest integer value in some cases.

 

we select  11520  pixels as the reference screen width.

Mainly Concerning that the standardized number is adopted by some  standard
such as DVB ,SMPTE.

so we think it should be consistent with  these standard ,though it leads to
a fraction of  in some cases.

 

Best regards,

Huiyu

 

发件人: Stephen Botzko [mailto:stephen.botzko@gmail.com] 
发送时间: 2011年4月20日 18:29
收件人: huiyu
抄送: mmusic@ietf.org; Bert Greevenbosch
主题: Re: [MMUSIC] About measurement unit for ParallaxInfo

 

I agree that having an implicit reference screen width of 11,520 pixels
resolves the problem.  This essentially defines the signaled value as a
fraction of the screen size (using somewhat unusual but carefully chosen
units). 

An alternative would be to explicitly signal the reference screen width.
The only advantage I see to the alternative approach is that it allows an
exact representation for other screen widths (such as 1024 for computer
screens or 800 for mobile devices).  Though this advantage is limited to
cases there the text is intended for a narrow range of devices.

Regards,
Stephen Botzko

2011/4/20 huiyu <huiyu@huawei.com>

Hi,all

 

The SDP  "ParallaxInfo" attribute  is  actually computed relative to  a
reference screen, which has a  fixed screen resolution .

The  reference screen  has  a   screen resolution of 11520 horizontal pixels
.

The number has been standardized by the SMPTE .

 

The SDP  "ParallaxInfo" attribute indicates the parallax in units of pixels
related to  reference screen with 11,520 horizontal pixels.

 

The transformation from the reference parallax in pixels to the actual
parallax in pixels for different display sizes shall be as follows:

PARALLAX= parallax/[11520/ W_pix]

 

PARALLAX  means the parallax in the actual screen in units of pixels.

W_pix means  the horizontal pixels  of the actual screen solution.

parallax is  the 'parallax' value in the SDP  "ParallaxInfo" attribute line
in units of pixels.

 

Because there may be master spatial resolutions for which [PARALLAX ] cannot
be readily derived by dividing by an integer. so the resulting [PARALLAX ]
value shall be appropriately rounded to the nearest integer value."  Here
‘[11520/ W_pix]’ means  the resulting value  shall  be rounded to the
nearest integer.

 

 

As for 11520, SMPTE  provide the following reasoning:

The reason for this particular reference display value is that the native
parallax Value of the three most popular standards for horizontal resolution
can be readily derived from the display value by dividing by an integer, as
follows:

o       1920 horizontal pixels = 11,520 / 6

o       1440 horizontal pixels = 11,520 / 8

o       1280 horizontal pixels = 11,520 / 9

 

 

 

The following illustrates the processing of  deducing the transformation.

 

In MPEG-C part 3, ISO/IEC 23002-3,the formula P/P_ref=W/W_ref demonstrates
the transformation of parallax from  a reference screen to a actual screen,

although it is just approximate. 

 

 The unit of all parameters can be 'cm'. 

  'W_ref' means the horizontal screen size of the reference screen.

  'w' means the horizontal screen size of the actual screen.

  'P_ref'  means the parallax  in the reference screen.

  'P'  means the parallax  in the actual screen.

 

According to the physical size of each pixel  in screen, we can change the
unit of 'cm' to the unit of 'pixel' .

  the parallax of the reference screen in units of pixels can be expressed
as P_refpix,

  the horizontal screen size  of the reference screen in units of pixels can
be expressed as W_refpix,  

  the parallax in the actual screen in units of pixels can be expressed as
P_pix,

  the horizontal screen size  of the actual screen in units of pixels can be
expressed as W_pix,

  

  so it has :

   W_refpix/P_refpix=W_ref/P_ref;

   W_pix/P_pix=W/P;

 

   According to  the above formulas,  it has:   P_pix= P_refpix/( W_refpix /
W_pix) .

 

   Correspondingly, 

   the value of W_refpix is 11520, 

   P_refpix is  the 'parallax' value in the SDP  "ParallaxInfo" attribute
line  . 

   the value of W_pix is the horizontal  pixels of actual screen  solution.

   then  P_pix  is the actual parallax in actual screen, it can also be
transformed to cm  according to the physical size of each pixel.

 

So this formula P_pix= P_refpix/( W_refpix / W_pix)  corresponds to the
previous transformation formula.

   In summary, we reference the  SMPTE standard , and choose 11520  as the
horizontal pixels  of the reference screen solution ,

and define  the transformation.    we will add some text clarifying the
transformation of parallax.

 

 

Best regards,

HuiYu

 

 

 

发件人: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] 代表
Stephen Botzko
发送时间: 2011年4月19日 18:17
收件人: Bert Greevenbosch
抄送: mmusic@ietf.org
主题: Re: [MMUSIC] About measurement unit for ParallaxInfo

 

Thx for the formula / followup.

The screen resolution is not known though.  With H.264 all you know is the
profile/level.

Regards,
Stephen Botzko

On Tue, Apr 19, 2011 at 3:29 AM, Bert Greevenbosch
<Bert.Greevenbosch@huawei.com> wrote:

Hi all,

During the Prague meeting, there was a question about the measurement unit
of the "ParallaxInfo" attribute. Currently, this unit is pixels, but I was
asked if it would make sense to use another unit, for example cm, to cater
for different screen sizes and resolutions.

As many before me, I did some calculations. The results match similar
calculations in MPEG-C part 3, ISO/IEC 23002-3. It turns out that the
parallax P is a hyperbolic function of the depth Z (where Z=0 corresponds to
the position of the screen itself). The function P(Z) has a zero at screen
depth, a vertical asymptote at the viewing distance and a horizontal
asymptote of the distance between the eyes.

Near to the screen, P(Z) can be approximated by a line, that goes trough
(Z=0,P=0). It has the form

(1)     P(Z) ~= A*Z,

where A depends on the x- and z-positions of the left and right eyes. (In
the calculations, I have neglected y, leading to a small bias.)

Since formula (1) is linear, near to the screen, multiplying the parallax by
a certain factor results in increasing the depth by approximately the same
factor. This is desirable, since if in one representation the horizontal and
vertical distances are twice as big as in another, it is natural that the
depth is twice as big as well.

If we have a fixed screen resolution in pixels, e.g. 1280x720 pixels, then
the parallax in pixels will be smaller on a small screen than on a big
screen. But since the rest of the video is equally smaller, through (1) the
complete picture remains in sync (assuming the depth range is not too
large).

So I think the unit "pixels" is appropriate for the ParallaxInfo attribute.
We might want to add some text clarifying that the parallax suits the pixel
width and height of the video.

Any opinions on this?

Best regards,
Bert
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic