[avtext] VP9 P bit (was Re: Frame marking & VP9 SVC)
Jonathan Lennox <jonathan@vidyo.com> Wed, 05 July 2017 22:17 UTC
Return-Path: <prvs=33594dbbfe=jonathan@vidyo.com>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 601BB12F3D0; Wed, 5 Jul 2017 15:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level:
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0khDtS6zNoWu; Wed, 5 Jul 2017 15:17:43 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23646127333; Wed, 5 Jul 2017 15:17:43 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v65MGY2u028341; Wed, 5 Jul 2017 18:17:39 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 2be6g43y17-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Wed, 05 Jul 2017 18:17:39 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Wed, 5 Jul 2017 17:17:38 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
CC: Bernard Aboba <bernard.aboba@gmail.com>, Sergio Garcia Murillo <sergio.garcia.murillo@cosmosoftware.io>, "avtext@ietf.org" <avtext@ietf.org>, "payload@ietf.org" <payload@ietf.org>, Alexandre GOUAILLARD <alex.gouaillard@cosmosoftware.io>
Thread-Topic: VP9 P bit (was Re: [avtext] Frame marking & VP9 SVC)
Thread-Index: AQHS9dyCSeJ3RymXI0WSORtztATA3g==
Date: Wed, 05 Jul 2017 22:17:38 +0000
Message-ID: <0F54961F-C28B-4CC3-9F6C-E63C417FB3F0@vidyo.com>
References: <ebdc7854-b390-d0e4-cfd1-d7df9c65aba4@gmail.com> <D4FFF329.6BA66%mzanaty@cisco.com> <0b5c72c6-4f59-daba-f193-282ea10d1f07@gmail.com> <D513D706.6C7F3%mzanaty@cisco.com> <00166BCB-6452-4D72-B5DF-5A456B2304EF@vidyo.com> <9a4994d3-f033-e1da-7884-a55c31789c59@gmail.com> <30944D17-BEB9-4EC6-A97C-0700567563FB@vidyo.com> <918659db-1742-4dd4-6fa3-7d0797aa4582@gmail.com> <50b624f9-4ce7-099e-1730-1b3a0d986e69@cosmosoftware.io> <CAOW+2du7K1Cz2PzG3dddHajW3tS+kkS3BGs_xP_suymssH2pwA@mail.gmail.com> <a58018e7-149f-810a-a0d6-944cb8dbc0e5@cosmosoftware.io> <A3A2CACA-FA2F-4BA2-8209-0F5B556EA732@vidyo.com> <a5bf47e7-153b-f2d7-0c15-bfd8a642cf2f@gmail.com> <CAOW+2duAUsH9_2Lv+W9nU7OBwmod6GOe4D8+7faZUenjjyWtaQ@mail.gmail.com> <9685e097-2255-c439-6c42-c268cac4d48f@gmail.com>
In-Reply-To: <9685e097-2255-c439-6c42-c268cac4d48f@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <358B325A35ED5B41BC31580C8323DE38@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-05_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1707050364
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/5-eApHJiUsoNfIzdMSsC_UuIpOI>
Subject: [avtext] VP9 P bit (was Re: Frame marking & VP9 SVC)
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avtext/>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 22:17:44 -0000
Adding payload@ietf, since details of the VP9 spec itself (as opposed to how it’s used with frame marking) should be discussed there. Please restrict followups as appropriate. > On Jul 5, 2017, at 5:41 PM, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> wrote: > > Regarding the P bit, in prev draft the information was per layer-frame, now with the renaming, it is per picture. Not sure if it is a typo, or it has changed it's meaning, but if so, that would be exactly the inverse of the I bit. This was a typo, yes. Thanks for catching it! I’ll fix it in the next version. (Notice that there’s a lot of other text around that definition that doesn’t make any sense if P is per-picture.) On the reasons for the terminology change: “super frame” already means something (different) in VP9, so reusing the term was problematic. Additionally, what we now call “frame” is exactly what the VP9 codec standard means by “frame”, i.e. a single encoded image.
- [avtext] Frame marking & VP9 SVC Sergio Garcia Murillo
- Re: [avtext] Frame marking & VP9 SVC Mo Zanaty (mzanaty)
- Re: [avtext] Frame marking & VP9 SVC Sergio Garcia Murillo
- Re: [avtext] Frame marking & VP9 SVC Jonathan Lennox
- Re: [avtext] Frame marking & VP9 SVC Bernard Aboba
- Re: [avtext] Frame marking & VP9 SVC Sergio Garcia Murillo
- Re: [avtext] Frame marking & VP9 SVC Bernard Aboba
- Re: [avtext] Frame marking & VP9 SVC Sergio Garcia Murillo
- [avtext] VP9 P bit (was Re: Frame marking & VP9 S… Jonathan Lennox