IETF Logo Mail Archive

Re: [rtcweb] MTI Video Codec: a novel proposal

cowwoc <cowwoc@bbs.darktech.org> Mon, 10 November 2014 18:29 UTC

Return-Path: <cowwoc@bbs.darktech.org>
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 B3ABA1A82E2 for <rtcweb@ietfa.amsl.com>; Mon, 10 Nov 2014 10:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 xFKstFnJGRNu for <rtcweb@ietfa.amsl.com>; Mon, 10 Nov 2014 10:29:42 -0800 (PST)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F342E1A9102 for <rtcweb@ietf.org>; Mon, 10 Nov 2014 10:27:22 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id x19so9525360ier.5 for <rtcweb@ietf.org>; Mon, 10 Nov 2014 10:27:22 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vPvXmMLhpLXY5yz3BJON6y8pMXIqq6U0WnRt1OaVdww=; b=kTFoCGIj8gcVldTbclscpSra8wfimuY13Z2JuW50VTv2oVJZmoaJUMxK3JO2XxC92m DqTtOF0faKE0c7pLQUyQxMp1OwRBgLO2JkqWEMTOCnt3zvc+MCORzpFhQpy+lmkYC7/N ST726DMFVSP3/E9GR5cYv0hny3aE/pXWbYaxlfIlreLxTu6hP3x7GiRBlPcRE6pkKwcx XXwxnZzbZwsofqUOUmEENGDn8yLY6jemgDNxWWHSSer+Q5O+x/bvKlaJQ8Z98SmdTCGM NBjDTO1Ts/SH1qHzGXbQ1WWGjfX2E7Otrq8ItCtTSJp0RdqhpxZjulY4375+cnOMzaVl VX0A==
X-Gm-Message-State: ALoCoQnGQoMpx/JOfwPbvYU3MtrVTQcIM7FC1/EQ+AXWjrThR8S2NjzYFU9KOq8Qpymt9Q9Zg694
X-Received: by 10.50.134.9 with SMTP id pg9mr26822879igb.28.1415644042328; Mon, 10 Nov 2014 10:27:22 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id w7sm5098691igl.7.2014.11.10.10.27.21 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Nov 2014 10:27:21 -0800 (PST)
Message-ID: <54610389.7060103@bbs.darktech.org>
Date: Mon, 10 Nov 2014 13:27:21 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <54601E19.8080203@nostrum.com> <6689CD42-C046-45DE-9871-16538A799810@phonefromhere.com> <5460ECFE.4000900@gmail.com> <C1BE48EE-726C-42FC-B6B7-11BEFDD175DE@phonefromhere.com>
In-Reply-To: <C1BE48EE-726C-42FC-B6B7-11BEFDD175DE@phonefromhere.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/xagQHS7_hmqDCIy3NLuOeazZ4GI
Subject: Re: [rtcweb] MTI Video Codec: a novel proposal
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: Mon, 10 Nov 2014 18:29:44 -0000

On 10/11/2014 12:40 PM, Tim Panton wrote:
> The realities I’m thinking of are the ones facing someone building a
> video enabled pet phone (for example). I can get H264 hardware very
> cheaply (eg a raspberry Pi) and have it communicate with an ios App
> or firefox on a laptop without any license (as far as I can tell).
> Getting the same setup to work with VP8 will consume significantly
> more battery power at both ends.
>
> I wish this were not the case, but that’s the reality I see.

I was/am under the impression that this reality will change over the 
coming year as devices roll out with hardware VP8 support.

According to http://wiki.webmproject.org/hardware/devices Raspberry Pi 
already supports hardware decoding. The assumption is that they are 
working on hardware encoding in a future release.

Gili

v2.23.0 | Report a Bug | By Email