Re: [MMUSIC] Remarks from today

Ted Hardie <ted.ietf@gmail.com> Sat, 16 April 2011 00:35 UTC

Return-Path: <ted.ietf@gmail.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 9F8A8E067E for <mmusic@ietfc.amsl.com>; Fri, 15 Apr 2011 17:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.02
X-Spam-Level:
X-Spam-Status: No, score=-3.02 tagged_above=-999 required=5 tests=[AWL=0.578, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 YQdqaZ+uuapZ for <mmusic@ietfc.amsl.com>; Fri, 15 Apr 2011 17:35:49 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfc.amsl.com (Postfix) with ESMTP id 10681E0665 for <mmusic@ietf.org>; Fri, 15 Apr 2011 17:35:48 -0700 (PDT)
Received: by pzk30 with SMTP id 30so1517679pzk.31 for <mmusic@ietf.org>; Fri, 15 Apr 2011 17:35:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cZkG4l6ZY1Fi1FBxvidOBJ6xmIyDz2zhyPiem+ZEE58=; b=HQ8FhHoY6nr2/FSsfg/OnuP87+sCYfUTfVa5q+fXUy5Qh9lwpmninH1ZdJGCjNzOxG k+TLPA+l8M0ZYt1sydcbpOmEovegyHairb+vzXZl6RoUrcwozPiZzbMY6Je0JMGEN6Bf Fzqi4n3nKy2M+zH6m/HhL8dgdrpebGuGcRJa8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=AzFrvJ/qXKyR+EHZwsqco4sXE1pKjtbxUDwd63L8zFyZwYppUMUbU8d54CEYpb6K2d OnjYbV1C1maMxyZfVp7gxuMJBpih2O+d3UJfU+qMRC+2rX1CbmwUrc70WJV+HXeQo1Gy 1n+dny7frvkTkDQ2PuzOHpZFMsxdnkx8wPylo=
MIME-Version: 1.0
Received: by 10.68.40.38 with SMTP id u6mr2790645pbk.371.1302914148019; Fri, 15 Apr 2011 17:35:48 -0700 (PDT)
Received: by 10.68.50.202 with HTTP; Fri, 15 Apr 2011 17:35:47 -0700 (PDT)
In-Reply-To: <46A1DF3F04371240B504290A071B4DB6012C4B09@SZXEML501-MBS.china.huawei.com>
References: <46A1DF3F04371240B504290A071B4DB6012B2389@szxeml501-mbx.china.huawei.com> <19861.51136.463433.972475@irtcluster12.cs.columbia.edu> <46A1DF3F04371240B504290A071B4DB6012C2EFF@SZXEML501-MBS.china.huawei.com> <BANLkTikFyudyfqS90R3rL+ZTZJ2sgBayzw@mail.gmail.com> <46A1DF3F04371240B504290A071B4DB6012C3A46@SZXEML501-MBS.china.huawei.com> <BANLkTi=FuMJYvUN1dnzw0MxQWokcynnZUg@mail.gmail.com> <46A1DF3F04371240B504290A071B4DB6012C43B9@SZXEML501-MBS.china.huawei.com> <BANLkTi==gPXY+=rOa_n3R0wWjtdy-jP3yA@mail.gmail.com> <46A1DF3F04371240B504290A071B4DB6012C4B09@SZXEML501-MBS.china.huawei.com>
Date: Fri, 15 Apr 2011 17:35:47 -0700
Message-ID: <BANLkTi=S+Lfq1Aat3tVHxwE36H+_BwTAEw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
Content-Type: multipart/alternative; boundary="bcaec539634ef72f8904a0fe56d8"
Cc: "lennox@cs.columbia.edu" <lennox@cs.columbia.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Remarks from today
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: Sat, 16 Apr 2011 00:35:50 -0000

Hi,

Some further comments in-line.

On Thu, Apr 14, 2011 at 11:21 PM, Bert Greevenbosch <
Bert.Greevenbosch@huawei.com> wrote:

>  Hi Ted,
>
>
>
> My suspicion is that there are probably practical limits to some system's
> ability to either upsample or interpolate.  Would it make sense to add
> something to the 3dFormat line to indicate what the resulting per-view rate
> will be?  So that
>
> a=3dFormat:FP SbS
>
> had an additional parameter:
>
> a=3dFormat:FP SbS 30Hz
>
>  We could also consider using the SDP attribute "framerate" (RFC 4566).
> This attribute would give the frame rate of the 2D channel stream, but we
> can write in the draft that in the frame sequential case the frame rate per
> view is half of it.
>

The relevant text from RFC 4566 is:

a=framerate:<frame rate>

         This gives the maximum video frame rate in frames/sec.  It is
         intended as a recommendation for the encoding of video data.
         Decimal representations of fractional values using the notation
         "<integer>.<fraction>" are allowed.  It is a media-level
         attribute, defined only for video media, and it is not
         dependent on charset.

While I think it could be re-used here, it seems to me to make more sense to
use a separate indicator.  This is partly because it is more for the
decoder/upsampler/interpolation check (Can I upsample this to something
reasonable?  If not, don't select this choice).  And it's partly because I
worry a bit about the interaction with existing code.



>  Or do you want to indicate the target shutter glass frequency?
>
>
>

No, I think you're right that it's more likely that things will get adjusted
to a standard shutter speed by upsampling than they will change the shutter
speed.

regards,

Ted Hardie


> Best regards,
>
> Bert
>
>
>
>
>
> *From:* Ted Hardie [mailto:ted.ietf@gmail.com]
> *Sent:* 15 April 2011 02:49
>
> *To:* Bert Greevenbosch
> *Cc:* lennox@cs.columbia.edu; mmusic@ietf.org
> *Subject:* Re: [MMUSIC] Remarks from today
>
>
>
> On Wed, Apr 13, 2011 at 10:44 PM, Bert Greevenbosch <
> Bert.Greevenbosch@huawei.com> wrote:
>
>  I agree, the 30Hz (per view) case would give a flickering effect. Since
> normal TVs have a frequency of 60Hz or more, for a similar quality with
> shutter glasses the frame rate should be 120Hz (=60 Hz/view) or more.
>
>
>
> But the receiver can also upsample the received signal to a higher display
> rate. For example, if it receives the following frame sequence at 30Hz/view:
>
>
>
> L1,R1,L2,R2,L3,R3,...,
>
>
>
> then it could display at 60Hz/view:
>
>
>
> L1,R1,L1,R1,L2,R2,L2,R2,L3,R3,L3,R3,....
>
>
>
> The receiver can also use some interpolation technique to generate the
> frames between L*k* and L(*k*+1).
>
>
>
> I think that in praxis the receiving device will process the received
> stream to make it fit the display system. This allows different
> types/standards of shutter glasses to be used, independent on the format in
> which the 3D stream was received. It also allows other display types such as
> polarisation or autostereoscopic displays.
>
>
>
>
> My suspicion is that there are probably practical limits to some system's
> ability to either upsample or interpolate.  Would it make sense to add
> something to the 3dFormat line to indicate what the resulting per-view rate
> will be?  So that
>
> a=3dFormat:FP SbS
>
> had an additional parameter:
>
> a=3dFormat:FP SbS 30Hz
>
>
>    *>I know only know one manufacturer's system at all well, and my
> understanding is that the timing signals which synchronize them are really
> matching the frame start times to the shuttering, but don't adjust the frame
> rates.  Are there glasses which can modify the rate substantially as well?
> *
>
>
>
> Can you please explain a bit more about the system you are referring too,
> especially about not modifying the frame rate? Do you mean the frame rate
> between the TV screen and the signalling device (that transmits the signal
> to the shutter glasses) or the frame rate of the video stream as it is
> received before it is decoded (by the codec)?
>
>
>
>
> I probably should have said "shuttering rate", sorry.  I mean that it
> matches the shutters to the alternating left and right view, but that the
> shuttering rate is consistent (resulting in 60Hz per view, in this case).
>
> regards,
>
> Ted Hardie
>