Re: [rtcweb] MTI motion JPEG
Leon Geyser <lgeyser@gmail.com> Sat, 30 November 2013 20:50 UTC
Return-Path: <lgeyser@gmail.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 E82C31AE291 for <rtcweb@ietfa.amsl.com>; Sat, 30 Nov 2013 12:50:28 -0800 (PST)
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, SPF_PASS=-0.001] 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 eKPOIxxz0eLx for <rtcweb@ietfa.amsl.com>; Sat, 30 Nov 2013 12:50:26 -0800 (PST)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 53C251AE1B4 for <rtcweb@ietf.org>; Sat, 30 Nov 2013 12:50:26 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id n7so7484792lam.16 for <rtcweb@ietf.org>; Sat, 30 Nov 2013 12:50:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S8uqH8vYE2OmjWeei4vaz9IMtcqmzZEc4bDD/LQ+tzk=; b=in78T04bhFXf+4hDaVYFss/ilL+fOIbsNbbCPP7iSEfZixtbe2wCUVmn1SUFqMs+M/ +FzL2fxLm/z3FTAXjpmI7DyJrw5UCyFdspQnhl9lhFGSEd/lJoEIdmJWPKkHASc1IXv+ oe56QY72x+PzbI+nakSWATDHJRvTOQkBS57P5aBPrhKVSzLTHpfSZRAtxCWDjKQ+0A6m PWI2olSPafOFDfU9AYz+zaLRFFuGt1KJu86CYkKU/blFhdrEUqAuu14f95+nRcDL6+YV NGSEKrJVw/3md7ce4QVK+f7Qo9bwzDhNgn9ia21Wex1PlvwU81eu2OZ0gW7WPA4icvS4 yY2g==
MIME-Version: 1.0
X-Received: by 10.152.22.4 with SMTP id z4mr40066509lae.14.1385844623926; Sat, 30 Nov 2013 12:50:23 -0800 (PST)
Received: by 10.114.28.7 with HTTP; Sat, 30 Nov 2013 12:50:23 -0800 (PST)
In-Reply-To: <529A4EA3.9010003@googlemail.com>
References: <529935FD.7090409@thaumas.net> <529A4EA3.9010003@googlemail.com>
Date: Sat, 30 Nov 2013 22:50:23 +0200
Message-ID: <CAGgHUiQTyp2SjJ=7UGkcdUuCturgNGr6h-TAZd0rhTgtw3JOLw@mail.gmail.com>
From: Leon Geyser <lgeyser@gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="089e0158b8e285ea7b04ec6b1898"
Subject: Re: [rtcweb] MTI motion JPEG
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: Sat, 30 Nov 2013 20:50:29 -0000
I don't mind MJPEG at high bitrates like 1Mbit/s, but at 256Kbps I struggled to get something acceptable out of ffmpeg's MJPEG encoder. I have a 256Kbps connection btw :) On 30 November 2013 22:46, Maik Merten <maikmerten@googlemail.com> wrote: > Actually that may work. Toying around with mjpeg I found that, for > instance, CIF video can be transmitted with somewhat usable quality at full > framerate at slightly over one mbit/s. Usable quality at around half a > mbit/s can be achieved by decreasing the framerate. Perceived picture > quality can be increased by postprocessing (deblocking, deringing) or the > decoding technique described in "William B. Pennebaker, Joan L. Mitchell - > JPEG: Still Image Data Compression Standard, 1993". I would also assume > that support for the arithmetic encoder could be mandated by now, > increasing coding efficiency. > > So this makes for a lousy video codec, but at least it's fast, > "everywhere", presumably free of additional IPR risk, and flexible > regarding frame size. I can also be used to occasionally push high-quality > pictures (think slide shows), a use case H.261 included a hack for (4CIF) > but would be better handled by MJPEG anyways. > > > Maik > > > Am 30.11.2013 01:49, schrieb Ralph Giles: > > I'd like propose motion JPEG as the manditory-to-implement video codec, >> per RFC 2435 or similar. >> >> Yes, I'm serious. I didn't propose this earlier to avoid splitting the >> vote at the last meeting. >> >> Our goal here is to to avoid negotiation failure. We don't have >> concensus for either h.264 or VP8, but no one is happy with the >> performance of the older formats we've been discussing. >> >> Since we can't have acceptable performance in our fallback we should >> instead optimize for minimum complexity. We all have to ship this and >> hope it's never used in practice. >> >> While not as trivial as G.711 audio, mjpeg+rtp is simpler to implement >> than the more recent obsolete codecs we've been discussing. JPEG decode >> is already universally supported for still images. As the simplest >> compressed format it has advantages for testing and legacy >> interoperation, just like G.711. It works fine over a LAN and for the >> WAN...well, you can have a couple of blurry frames a minute if you like >> that better than nothing at all. >> >> -r >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb >> >> > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >
- Re: [rtcweb] MTI motion JPEG Basil Mohamed Gohar
- Re: [rtcweb] MTI motion JPEG Harald Alvestrand
- Re: [rtcweb] MTI motion JPEG Maik Merten
- Re: [rtcweb] MTI motion JPEG Maik Merten
- Re: [rtcweb] MTI motion JPEG Maik Merten
- [rtcweb] MTI motion JPEG Ralph Giles
- Re: [rtcweb] MTI motion JPEG cowwoc
- Re: [rtcweb] MTI motion JPEG Maik Merten
- Re: [rtcweb] MTI motion JPEG Maik Merten
- Re: [rtcweb] MTI motion JPEG Leon Geyser
- Re: [rtcweb] MTI motion JPEG Basil Mohamed Gohar