Re: [avtext] Frame marking & VP9 SVC

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Wed, 05 July 2017 21:41 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 CA69F12ECB4 for <avtext@ietfa.amsl.com>; Wed, 5 Jul 2017 14:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 g3dkC_bx7WfV for <avtext@ietfa.amsl.com>; Wed, 5 Jul 2017 14:41:24 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA61212EC27 for <avtext@ietf.org>; Wed, 5 Jul 2017 14:41:23 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id k67so2477471wrc.2 for <avtext@ietf.org>; Wed, 05 Jul 2017 14:41:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=3xPn8rVEKVZhOYJThuwAyQk3AaBORselg1azqzU9B7Y=; b=B+w5xl3UZoEuBYzj7aEeTWWqg15fKRNBW60wWrNCfjLeHm3UDVMcs80f3OplPjxauA wcYJfuUq9u6WO48E0wMnQH8PPLM121WjnrMwdt/IyOYsdH1VmR2ryowYwTkLUSCCw74L 2e0VOX0Qf3RUMzYRYMXdWGucy15ba5J6L9d2ssXon0XZ+likIuV/JwtA0WimD+xqsRTM vxFhYYeLlka7Tvay+NsJBZ5vqP4KdrzMFRP1zUS5boC/dz/wwql6zboP6SHjgyjpTw/U IYeSGmEDtrBVTn6YmpI+dwJfaBsQKC5iYxm38+IIRvUiVaIjQog4XlKH7ZguAl61oos/ WCtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=3xPn8rVEKVZhOYJThuwAyQk3AaBORselg1azqzU9B7Y=; b=lL3076RwqirtJnZu7XNk+PP/HGmEXsTQu0Mr4hGSkr5v4RNa4A4vg3o1vQj21Q35R/ ZAUM3A/AbaAX+lKEIomkySvIuUjU9zBGLlXt8iKgE6BjczydFvzU19u7kO7t8mSpOdth 9IZNTy8+rp/S2KERBi7An58iT4lIpTqYeSngoteiIW3Nj8jKV8tPc0jPLHK3jYfFhn+U AvkaxIyXqbfgocPFGxsbpb5MtOx/dAq5I7FS0PimCGQ/GY8d7ZCdpVe8Pt/IVRlyq7Ec mMo5xk3w/bNBnMXjNhFyxvjjqNl2H0NA2FPLHYo62G0R5hHn7HRUf+jIzFnvp3TeMnwy G+QQ==
X-Gm-Message-State: AKS2vOy26oSryRQNNhEm/wdDG3hry0rOS+HfOpbrOfU6fEYTVrL28iFl 2QgPWyT2ir2BNg==
X-Received: by 10.28.51.212 with SMTP id z203mr35391776wmz.103.1499290882261; Wed, 05 Jul 2017 14:41:22 -0700 (PDT)
Received: from [192.168.0.199] (static-96-42-229-77.ipcom.comunitel.net. [77.229.42.96]) by smtp.googlemail.com with ESMTPSA id 3sm114302wrs.18.2017.07.05.14.41.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jul 2017 14:41:16 -0700 (PDT)
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: Jonathan Lennox <jonathan@vidyo.com>, Sergio Garcia Murillo <sergio.garcia.murillo@cosmosoftware.io>, "avtext@ietf.org" <avtext@ietf.org>, Alexandre GOUAILLARD <alex.gouaillard@cosmosoftware.io>
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>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <9685e097-2255-c439-6c42-c268cac4d48f@gmail.com>
Date: Wed, 05 Jul 2017 23:41:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAOW+2duAUsH9_2Lv+W9nU7OBwmod6GOe4D8+7faZUenjjyWtaQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------20C838D3AA976F9032637A64"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/ntfDsjMJjuruDPenp6-w0k0__Rk>
Subject: Re: [avtext] 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 21:41:26 -0000

On 05/07/2017 23:19, Bernard Aboba wrote:
> Sergio said:
>
> "So the question is they can be mapped 1-to-1 to the frame marking I 
> and B bits. If so, just adding that to the draft that the I and B bits 
> on the frame marking extension must be filled with the values of the 
> vp9 P and U bits ( I=!P , B=U), would work."
>
> [BA] It's not obvious to me that the P or U bits can be inferred from 
> existing framemarking bits including the I and B bits.

I agree, it is far from obvious.. :)

The point is that there is no easy way of calculating the B bit on frame 
marking for VP9 (you would need to process the SS to calculate it as you 
have done in the examples, but that info is not provided by the encoder 
neither present on the desc header), so the only close-enough info would 
be the U bit. If we "redefine" it's meaning for VP9 it could work.

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.

Best regards
Sergio