IETF Logo Mail Archive

Re: [rtcweb] Screen sharing

Henry Sinnreich <henry.sinnreich@gmail.com> Fri, 02 December 2011 00:31 UTC

Return-Path: <henry.sinnreich@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6DAC1F0C6D for <rtcweb@ietfa.amsl.com>; Thu, 1 Dec 2011 16:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.053
X-Spam-Level:
X-Spam-Status: No, score=-2.053 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2US+dUWTo19 for <rtcweb@ietfa.amsl.com>; Thu, 1 Dec 2011 16:31:38 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 94C5A1F0C3B for <rtcweb@ietf.org>; Thu, 1 Dec 2011 16:31:38 -0800 (PST)
Received: by ggnp4 with SMTP id p4so2895818ggn.31 for <rtcweb@ietf.org>; Thu, 01 Dec 2011 16:31:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type; bh=tdsLTzQl1YL6KLLrFAYaHZ5d3N0fybzWMwFA1pBlc2w=; b=uY2c6izOc+vHQU49cbD9Unyk+1ORVvoRa9QgfEYbOT7zerdzeFS0N7k41KaNIBXpbS GcxruvYKe0SfAXAlfQ4R4/1DLsQZkCc3ZokLFGfX68Qxd6dOPHN8W6jKqCefuE8gpPQ6 JMZlpLPSgiHwcg7i5zc2j0nYA8987ulxbUq1U=
Received: by 10.236.157.1 with SMTP id n1mr15332224yhk.64.1322785898224; Thu, 01 Dec 2011 16:31:38 -0800 (PST)
Received: from [192.168.15.2] (cpe-76-184-230-185.tx.res.rr.com. [76.184.230.185]) by mx.google.com with ESMTPS id f14sm19862905ani.8.2011.12.01.16.31.36 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 16:31:36 -0800 (PST)
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Thu, 01 Dec 2011 18:31:34 -0600
From: Henry Sinnreich <henry.sinnreich@gmail.com>
To: Aron Rosenberg <arosenberg@logitech.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, Randell Jesup <randell-ietf@jesup.org>, Justin Uberti <juberti@google.com>
Message-ID: <CAFD7886.20DF3%henry.sinnreich@gmail.com>
Thread-Topic: [rtcweb] Screen sharing
Thread-Index: Acywib6AsZdA6AbgVkeZyFaqklgtPA==
In-Reply-To: <CAB+e8F5ZJQJ--BstDfSzR1WyqgG=kxWLNe3vbFqjfXBXECHAqQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3405609096_928161"
Subject: Re: [rtcweb] Screen sharing
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 02 Dec 2011 00:31:39 -0000

Can remote meeting attendees read the print on say a legal document under
discussion?

If yes for commercial grade quality (I still have doubts), how is the codec
tweaking enabled via the API?

Thanks, Henry


On 12/1/11 5:05 PM, "Aron Rosenberg" <arosenberg@logitech.com> wrote:

> Screen sharing works great over H.264 or VP8 for us. You have to tweak the
> codec encoding parameters and FPS a bit, but you get great quality even on
> text.
> 
> Aron Rosenberg
> LifeSize, a division of Logitech
> 
> 
> 
> On Thu, Dec 1, 2011 at 11:18 AM, Henry Sinnreich <henry.sinnreich@gmail.com>
> wrote:
>> Hi Stefan,
>> 
>> Video sucks for screen sharing, displaying documents or even plain bullet
>> slides.
>> Displaying the screen and documents is in a completely other league IMO.
>> 
>> Thanks, Henry
>> 
>> 
>> On 12/1/11 9:19 AM, "Stefan Håkansson LK" <stefan.lk.hakansson@ericsson.com>
>> wrote:
>> 
>>> > Related to use-case 4.2.7 "Simple Video Communication Service with
>>> > sharing"
>>> > 
>>> 
(<http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requiremen>>>
ts
>>> > /?include_text=1>)
>>> > we had a student experimenting a bit.
>>> >
>>> > Essentially, the screen was treated as another video source (just as a
>>> > camera), and was transmitted to the other end as a MediaStream over a
>>> > PeerConnection.
>>> >
>>> > The implementation of getUserMedia allowed the screen to be selected as
>>> > a video source.
>>> >
>>> > Perhaps this could be a way forward for meeting this use-case? And
>>> > perhaps "screen" should be defined as a valid options argument to
>>> > getUserMedia?
>>> >
>>> > (there is some more info about what the student did at
>>> > <https://labs.ericsson.com/developer-community/blog/screen-sharing>)
>>> >
>>> > Stefan
>>> > _______________________________________________
>>> > 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
> 
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email