Re: [rtcweb] VP8 / H.264 conversion without transcoding

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Thu, 21 November 2013 14:27 UTC

Return-Path: <mzanaty@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB091AE18B for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 06:27:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.025
X-Spam-Level:
X-Spam-Status: No, score=-15.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 xEDXs3mZDxEV for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 06:27:36 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id BEAA11AE184 for <rtcweb@ietf.org>; Thu, 21 Nov 2013 06:27:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5218; q=dns/txt; s=iport; t=1385044049; x=1386253649; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Dq7YOgu/qFfLpDmXiqbyfGjxIJ/nrP+E7Qu0Ua9U850=; b=lDJjpA+xjXfHjGI7MTQnUaYpjDI92xNgNTZPBbPEUFCZNaAWNZrzMT2k pHkC5BvHFq/+nA2eo+uQYXDSvbEHBp7/+sczkIy/aqXa3KrIj+7YAilx3 3iPF1D2rvI1CgrvupEqhixaY176Y70WVYFzz26fgL4nywn+SIuW23gAgt o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFABMXjlKtJV2b/2dsb2JhbABZgwc4vQROgSMWdIImAQEEAQEBZQYLEAIBCAQ7BycLFBECBA4Fh28DDw3BDxMEjHKCdQQHgyCBEgOWLYFljFiFOIMogWok
X-IronPort-AV: E=Sophos; i="4.93,744,1378857600"; d="scan'208,217"; a="286590944"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 21 Nov 2013 14:27:29 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rALERS2b009854 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Nov 2013 14:27:28 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.50]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Thu, 21 Nov 2013 08:27:28 -0600
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Bossiel <bossiel@yahoo.fr>
Thread-Topic: [rtcweb] VP8 / H.264 conversion without transcoding
Thread-Index: AQHO5o56hPWXG33d2ki07HUjEvwix5ovvn5j
Date: Thu, 21 Nov 2013 14:27:27 +0000
Message-ID: <5A2BC34D-FE4D-4420-B52F-729087815F37@cisco.com>
References: <528D6C63.7050607@bbs.darktech.org>, <13BED03E-6853-4E49-BCCE-1FFB39571D36@yahoo.fr>
In-Reply-To: <13BED03E-6853-4E49-BCCE-1FFB39571D36@yahoo.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_5A2BC34DFE4D4420B52F729087815F37ciscocom_"
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] VP8 / H.264 conversion without transcoding
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2013 14:27:38 -0000

This probably refers to an intelligent transcoder versus a brute force transcoder. An intelligent transcoder harvests more data during decoding than just the raw output pixels, and uses this extra data to ease encoding. Data like block partitions, motion vectors, intra modes, quantization parameters, etc.

This is common for common conversions, like MPEG2 to H.264. VP8 and H.264 are much closer formats, so this can significantly improve transcoder performance.

However, this is strictly a performance optimization, with no impact on IPR or licensing issues.

Mo


On Nov 21, 2013, at 2:51 AM, "Bossiel" <bossiel@yahoo.fr<mailto:bossiel@yahoo.fr>> wrote:

This could be true if they can also walk on water and change it into wine.
To be serious, no it's not possible.
Mamadou

Sent from my iPhone

On Nov 21, 2013, at 3:13, Gili <cowwoc@bbs.darktech.org<mailto:cowwoc@bbs.darktech.org>> wrote:

Hi,

I'm at the WebRTC World conference. If I understood correctly, Zingaya just demoed what they claim is a VP8 to H.264 bridge that converts the video without transcoding. My interpretation is that they convert the surrounding packet format without re-encoding the actual video. Someone who understands codec internals (I don't) might want to validate this claim, because it could have a significant impact on the MTI debate.

It sounds far fetched, but imagine the possibilities:

  1.  If the video is not being re-encoded, do H.264 royalties apply?
  2.  If the conversion is really cheap, is it feasible to connect a H.264 peer to a VP8 peer and have one of them convert in-line (no MCU)?

Gili

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb